Page 1 of 1

[closed] Another nullPointerException error on launch

Posted: Tue Sep 28, 2010 2:20 pm
by ovd
Since the update to 1.07 (full version) I get the following error on launch:

java.lang.nullPointerException (fireTypeChanged)

You cannot click on the message and clicking back exits the app. Give the error time to disappear and the app works as normal. After the update to 1.08 I still get the error on every launch

Re: Another java.lang.nullPointerException error on launch

Posted: Tue Sep 28, 2010 2:59 pm
by Psyberia-Support
Hi,
Thanks for your report.
Did you un-install version 1.0.7 before installing version 1.0.8 ?
Regards

Re: Another java.lang.nullPointerException error on launch

Posted: Tue Sep 28, 2010 4:23 pm
by ovd
No I did not. I'll uninstall and reinstall 1.08 and let you know how that goes.

Re: Another java.lang.nullPointerException error on launch

Posted: Tue Sep 28, 2010 6:07 pm
by ovd
OK. Did a reinstall and the error no longer shows. Thanks for that.

ovd

Re: [closed] Another nullPointerException error on launch

Posted: Mon Nov 01, 2010 7:23 am
by Bridevalley
When I launch the app (version 1.0.8); I also see a message that appears briefly on the screen saying:
"An error occured...
It is recommended to restart the application
Message: java.lang.NullPointerException:
null (fireTypeChanged)"

As others report, the app seems to work perfectly well after the message disappears.

Re: [closed] Another nullPointerException error on launch

Posted: Tue Nov 02, 2010 2:56 pm
by Psyberia-Support
Hi,
Thanks for reporting this bug on our forum.
Did you made an update of the application or a brand new install ?
Some users reported this error after an update, and de-installing the application and then re-installing it solved the problem (that's why we suggested that in the release note here).

Any way this error happens when restoring the compass settings and have no impact on the run (but I understand this is very boring to see that at startup).

I'll make the necessary to clean saved preferences after an update to avoid these boring errors.
Thanks.