Mobile Object Spy - using 'Add to Mobile Object Spy' gives NullPointerException

similar issue to this one from 3 years ago - it has no resolution mentioned.

NullPointerException when adding an object to mobile object Spy

I’m running KSE 8.6.8 on Windows 10 machine, using a preinstalled app on Android.
When I add existing objects to the Spy (after first starting it), it creates a NullPointerException and moves focus back to KSE rather than the Spy (with an error dialog as below)
As a workaround, it seems to be possible to ignore the alert and continue using the Spy - as long as the alert is not closed, because if it is, a new one is generated!
If the alert is ignored, multiple lines will keep adding to the dialog, as in the screenshot.
To summarise - it doesn’t look very good and workaround is not intuitive (simply ignoring errors).
Error message is below:

!ENTRY org.eclipse.jface 4 2 2024-02-22 13:14:33.951
!MESSAGE Problems occurred when invoking code from plug-in: “org.eclipse.jface”.

  • at*
  • at*
  • at*
  • at$1.selectionChanged(*
  • at org.eclipse.jface.viewers.Viewer$*
  • at*
  • at*
  • at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(*
  • at org.eclipse.jface.viewers.StructuredViewer.updateSelection(*
  • at org.eclipse.jface.viewers.StructuredViewer.handleSelect(*
  • at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(*
  • at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(*
  • at org.eclipse.jface.util.OpenStrategy.access$4(*
  • at org.eclipse.jface.util.OpenStrategy$1.handleEvent(*
  • at org.eclipse.swt.widgets.EventTable.sendEvent(*
  • at org.eclipse.swt.widgets.Display.sendEvent(*
  • at org.eclipse.swt.widgets.Widget.sendEvent(*
  • at org.eclipse.swt.widgets.Display.runDeferredEvents(*
  • at org.eclipse.swt.widgets.Display.readAndDispatch(*
  • at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$*
  • at org.eclipse.core.databinding.observable.Realm.runWithDefault(*
  • at*
  • at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(*
  • at org.eclipse.ui.internal.Workbench.lambda$3(*
  • at org.eclipse.core.databinding.observable.Realm.runWithDefault(*
  • at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(*
  • at org.eclipse.ui.PlatformUI.createAndRunWorkbench(*
  • at com.kms.katalon.core.application.WorkbenchApplicationStarter.start(*
  • at com.kms.katalon.application.Application.runGUI(*
  • at com.kms.katalon.application.Application.start(*
  • at*
  • at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(*
  • at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(*
  • at*
  • at*
  • at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)*
  • at sun.reflect.NativeMethodAccessorImpl.invoke(*
  • at sun.reflect.DelegatingMethodAccessorImpl.invoke(*
  • at java.lang.reflect.Method.invoke(*
  • at org.eclipse.equinox.launcher.Main.invokeFramework(*
  • at org.eclipse.equinox.launcher.Main.basicRun(*
  • at*
1 Like


My team has been investigating this issue. I will let you know soon if there is any update. Thank you!