[Bug-12703]Unable to open converted global template due to NPE

I just updated to b2019021002 and tried opening my screens again. But I still get deserialisation errors one the same templates as mentioned.

Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
	at com.inductiveautomation.ignition.client.tags.impl.GatewayTagInterface.get(GatewayTagInterface.java:136)
	at com.inductiveautomation.ignition.client.tags.impl.ClientTagManagerImpl.getClientTagProvider(ClientTagManagerImpl.java:99)
	at com.inductiveautomation.ignition.client.tags.impl.ClientTagManagerImpl.lambda$subscribeAsync$9(ClientTagManagerImpl.java:198)
	at com.inductiveautomation.ignition.gateway.util.GroupMapCollate.lambda$groupMapIndexed$10(GroupMapCollate.java:79)
	at java.base/java.util.stream.ReferencePipeline$3$1.accept(Unknown Source)
	at java.base/java.util.HashMap$EntrySpliterator.forEachRemaining(Unknown Source)
	at java.base/java.util.stream.AbstractPipeline.copyInto(Unknown Source)
	at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(Unknown Source)
	at java.base/java.util.stream.AbstractPipeline.evaluate(Unknown Source)
	at java.base/java.util.stream.AbstractPipeline.evaluateToArrayNode(Unknown Source)
	at java.base/java.util.stream.ReferencePipeline.toArray(Unknown Source)
	at com.inductiveautomation.ignition.gateway.util.GroupMapCollate.groupMapIndexed(GroupMapCollate.java:92)
	at com.inductiveautomation.ignition.client.tags.impl.ClientTagManagerImpl.subscribeAsync(ClientTagManagerImpl.java:197)
	at com.inductiveautomation.ignition.common.tags.model.TagManager.subscribeAsync(TagManager.java:67)
	at com.inductiveautomation.factorypmi.application.binding.SimpleBoundTagAdapter.startup(SimpleBoundTagAdapter.java:145)
	at com.inductiveautomation.factorypmi.application.binding.DefaultInteractionController.startupBindings(DefaultInteractionController.java:355)
	at com.inductiveautomation.factorypmi.application.binding.DefaultInteractionController.startupAdapters(DefaultInteractionController.java:360)
	at com.inductiveautomation.factorypmi.application.components.template.VisionTemplate.startup(VisionTemplate.java:178)
	at com.inductiveautomation.factorypmi.designer.workspace.WindowWorkspace.openTemplate(WindowWorkspace.java:1877)
	at com.inductiveautomation.factorypmi.designer.model.navtree.TemplateNode.open(TemplateNode.java:126)
	at com.inductiveautomation.ignition.designer.navtree.model.AbstractResourceNavTreeNode.onDoubleClick(AbstractResourceNavTreeNode.java:179)
	at com.inductiveautomation.ignition.designer.navtree.NavTreePanel$MouseListener.lambda$mousePressed$0(NavTreePanel.java:655)
	at java.desktop/java.awt.event.InvocationEvent.dispatch(Unknown Source)
	at java.desktop/java.awt.EventQueue.dispatchEventImpl(Unknown Source)
	at java.desktop/java.awt.EventQueue$4.run(Unknown Source)
	at java.desktop/java.awt.EventQueue$4.run(Unknown Source)
	at java.base/java.security.AccessController.doPrivileged(Native Method)
	at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
	at java.desktop/java.awt.EventQueue.dispatchEvent(Unknown Source)
	at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
	at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
	at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
	at java.desktop/java.awt.EventDispatchThread.pumpEvents(Unknown Source)
	at java.desktop/java.awt.EventDispatchThread.pumpEvents(Unknown Source)
	at java.desktop/java.awt.EventDispatchThread.run(Unknown Source)

I moved this post to a new topic, since it’s caused by a differently underlying issue. Will keep you posted on the status - thanks for reporting these issues.

1 Like

Do you have any update on this?

I would like to continue testing next week.

There’s a fix for it up, but it hasn’t been verified/merged in yet. Quite possibly today, in which case it would go into the next nightly build.

1 Like

This issue was fixed in the build that was uploaded today (2/27)
Please let us know if you continue to see this behavior after upgrading.

I was able to test a new nightly today. The bugs described here are indeed solved. Thank you for that, but I ran into some other issues.

1 Like