Magic Earth crashes and closes after upgrade to 1.8.1-20230205257804-beryllium

Using /e/OS Applications
1

Hello,
@Manoj
I use Magic Earth daily since moving to e a few years ago.
Since upgrade to 1.8.1-20230205257804-beryllium, Magic Earth now crashes and closes ~1-2 minutes or so after starting.
I use ME for navigation, driver assist and dashcam.
Cleared cache and storage, but same issue.
My thanks,
NickP

Regain your privacy! Adopt /e/ the unGoogled mobile OS and online servicesphone

2

if you’re unable to debug this (via adb logcat) - have a look at the workaround to update magic earth through Aurora to have working Navigation until your issue is understood

3

Thank you Tcecyk.

I have checked but there’s no update to Magic Earth available in Aurora/Play Store at the moment.

How can I best provide logs etc?

My thanks,

NickP

4

you’d enable the developer mode and usb debugging, that from a pc look at “adb logcat” while interacting and waiting for the exception to happen - it will very likely show a stack trace leading up to the lines “FATAL EXCEPTION”. It’s visual distinctive as the trace itself is indented by one space to the left:

E AndroidRuntime: FATAL EXCEPTION: Thread-2
E AndroidRuntime: Process: com.generalmagic.magicearth, PID: 9390
E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.endsWith(java.lang.String)' on a null object reference
E AndroidRuntime:  at com.generalmagic.magicearth.intotheerrorbasement..
E AndroidRuntime:  at com.generalmagic.magicearth.fallingthroughmorelibraries..
E AndroidRuntime:  at com.generalmagic.magicearth.theroomitallstarted..

the last report on your error category was magic earth crashes as of /e/os 1.5 (#6293) · Issues · e / Backlog · GitLab - but no log, so hard to say if related

5

Thank you; I’ve tried this but because the Magic Earth app requires you to be driving to fully launch, and I’m running adb logcat on a desktop (I don’t have a win laptop that I can take driving), the app isn’t crashing.
Is it possible to save a log file to the device, when it’s actually in use, so that I can drive and record it crashing?
Thanks!

6

a logcat dump will record prior exceptions/crashes. You won’t have the benefit of having this “interact to pinpoint the error” benefit, but if the crash is recorded it can be found in a dump. So if you come home after driving and didn’t reboot, the logcat will contain the crash

7

tcecyk,

Thanks for the explanation, appreciated.

I did what you suggested but found only the following fatal exception:-

03-04 16:50:57.837 3566 15173 E AndroidRuntime: FATAL EXCEPTION: Thread-2
03-04 16:50:57.837 3566 15173 E AndroidRuntime: Process: foundation.e.drive, PID: 3566
03-04 16:50:57.837 3566 15173 E AndroidRuntime: java.lang.NullPointerException: Attempt to get length of null array
03-04 16:50:57.837 3566 15173 E AndroidRuntime: at foundation.e.drive.operations.ListFileRemoteOperation.onHttp404Received(ListFileRemoteOperation.java:148)
03-04 16:50:57.837 3566 15173 E AndroidRuntime: at foundation.e.drive.operations.ListFileRemoteOperation.run(ListFileRemoteOperation.java:91)
03-04 16:50:57.837 3566 15173 E AndroidRuntime: at com.owncloud.android.lib.common.operations.RemoteOperation.run(RemoteOperation.java:399)
03-04 16:50:57.837 3566 15173 E AndroidRuntime: at java.lang.Thread.run(Thread.java:923)
03-04 16:50:57.868 1403 15419 I DropBoxManagerService: add tag=system_app_crash isTagEnabled=true flags=0x2
03-04 16:50:57.869 1403 1534 I PackageWatchdog: Updated health check state for package foundation.e.drive: INACTIVE → INACTIVE
03-04 16:50:57.914 1403 7214 D ConnectivityService: ConnectivityService

Does that help?

Thank you,
NickP

8

it’s an app crash, but the wrong one (that you probably don’t care about) - it isn’t related to your magic earth woes (but funny it’s also a NullPointerException as in my example)