10-24-2009 10:39 PM
I am currently experiencing a strange issue with my app that only occurs on the device and not on the simulator. I have just finished adding a custom fadein/fadeout animated transition in my app's screens. Basically when a screen is pushed, another screen, MangoAnimationScreen, is pushed on top of it and draws the animation. Then when the animation is completed, MangoAnimationScreen is popped to reveal the new screen below it.
This works fine on the simulator, however when I tested the app on the BlackBerry it does not work. Right after the fade animation completes, the app closes and I get a dialog box stating:
[code]Uncaught Exception popScreen: UiEngine is null !: net.rim.device.api.ui.
10-25-2009 07:04 AM
Don't think I can help, but it would be useful to know the JDE/Component pack and Device OS Levels involved here, also the Device. Can you post these?
10-25-2009 11:06 AM
Building against JDE 4.7 component pack, simulator is running os 184.108.40.206 or something like that, and the device I'm testing on is Verizon 9530 running OS 220.127.116.11. If there were a way to "update" the simulator that might be useful in testing?
10-25-2009 11:44 AM
try attaching your device in the debugger and see where it gets "null".
you can also download verizon simulator here:
10-25-2009 11:15 PM
Well that's the thing: it never happens in the simulator. Maybe that's because of the differing OS versions... I'll try the verizon simulator now.
10-26-2009 07:23 AM
I tried using the Verizon simulator running OS 18.104.22.168 (the same OS running on the device) and got nothing. The simulator still chugs along happily where the device throws an error every time. :/
12-27-2009 07:33 PM
I get the same exception for 4.5.
The exception occurs after a soft reset or battery pull.
The reference for the UiEngine object points to the same address,
so I don't understand whey the exception says UiEngine is null != ...UiEngine.
UiEngine eng = Ui.getUiEngine();
Can someone tell if this is bug on Rim's side?
12-28-2009 07:48 AM
As a guess, and only a guess, I'd suggest your problem might be related to running things at startup before the UI is really available. Try delaying if