If you used to monitor your sport sessions with OpenRunner, you may have observed that OpenRunner no longer works with recent /e/OS versions: at launch, after the initial logo fadeout, the app sticks on a white screen and nothing else happens.
Clearing the cache, resetting authorizations, removing and reinstalling the app from the App Lounge, and disabling tracker blocking… none of these helped.
I have asked several people to check: apparently OpenRunner is broken on /e/OS-3.2-a15 and /e/OS-3.2-a14 but works well on former OS bases like 3.2-s
Are there people here with an understanding about the app dev framework, that could intuit the possibles causes of the white screen after an app logo fadeout?
In a too brief search I cannot tell if the app has been updated for a14 and a15 ?? This would be one possibility (easily checked from devs app@openrunner.zendesk.com) from log
I AppLocaleUtil: Can display preference - [com.openrunner.android] : isDisallowedPackage
My negatives earlier were to do with the “frozen start” did not allow permissions to be given. Allow permissions from Settings allows the app to behave differently but it fails to resolve Location with
11-11 14:24:12.195 15494 15494 W LocationManager: Exception while processing for WorkSource{10232 com.openrunner.android}: Lack of permission
The app is quite intrusive; I noticed that if App Trackers are allowed the error stall “moves on” to
11-11 14:35:20.838 15494 15510 D NetworkLocation: Start network scan for WorkSource{1000 android, 10232 com.openrunner.android}
I am the author of the reply that mentions the problem with Openrunner and UAPP. The latest update to UAPP seems to solve the problem… But Openrunner still doesn’t work…
the method got added to androidx.credentials v1.20 in Nov 2023, the stub got introduced to microg in Aug 2023 and never revisited - it just wasn’t known by then.
Imo one could ask OpenRunner to handle the credential manager exception more gracefully.