1.7-Android crashes on start and periodically in Background
See original GitHub issueAvoid duplicates
- Bug is not mentioned in the FAQ
- Bug is specific for Android only, for general issues / questions that apply to iOS and Android please raise them in the documentation repository
- Bug is not already reported in another issue
Describe the bug
A friend’s Samsung Galaxy A3 Mini updated CWA to 1.7 11 hours ago. Ever since the app crashes on open and every few seconds when in background.
11-26 10:02:20.493 5987 6021 E AndroidRuntime: FATAL EXCEPTION: pool-2-thread-3
11-26 10:02:20.493 5987 6021 E AndroidRuntime: Process: de.rki.coronawarnapp, PID: 5987
11-26 10:02:20.493 5987 6021 E AndroidRuntime: java.lang.IllegalArgumentException: Unknown worker: androidx.work.impl.workers.ConstraintTrackingWorker
11-26 10:02:20.493 5987 6021 E AndroidRuntime: at de.rki.coronawarnapp.util.worker.CWAWorkerFactory.createWorker(CWAWorkerFactory.kt:7)
11-26 10:02:20.493 5987 6021 E AndroidRuntime: at androidx.work.WorkerFactory.createWorkerWithDefaultFallback(WorkerFactory.java:1)
11-26 10:02:20.493 5987 6021 E AndroidRuntime: at androidx.work.impl.WorkerWrapper.run(WorkerWrapper.java:70)
11-26 10:02:20.493 5987 6021 E AndroidRuntime: at androidx.work.impl.utils.SerialExecutor$Task.run(SerialExecutor.java:1)
11-26 10:02:20.493 5987 6021 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
11-26 10:02:20.493 5987 6021 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
11-26 10:02:20.493 5987 6021 E AndroidRuntime: at java.lang.Thread.run(Thread.java:762)
Technical details
- Mobile device: Samsung Galaxy A3 Mini (2016), SM-A310F
- Android version: 7.0
Possible Fix
Additional context
Internal Tracking ID: EXPOSUREAPP-3987
Issue Analytics
- State:
- Created 3 years ago
- Comments:20 (14 by maintainers)
Top Results From Across the Web
Information regarding the Android version - Blockheads Forums
Regarding the current version of the game: Both the Google Play version and the Noodlecake updated version suffer from the white startup screen ......
Read more >Core - Android Developers
This first alpha version contains all the new APIs backported down to API 23, with the exception of the icon background. See the...
Read more >HUGE MEMORY HOG. Phone itself using 1.6GIGS RAM (of 1.7).
I have a HTC ONE and I've got a problem that has STUMPED WIRELESSWAVE, and BELL. After 2 HOURS on BELL customer service,...
Read more >Advanced Usage for Android - Sentry Documentation
The application package is automatically marked as inApp. ... libraries for detecting when the Application is either in the background or in the...
Read more >BombSquad - froemling.net
There's currently an issue with Retina macbook pros where the game will crash if you launch it while at the highest resolution setting...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@d4rken Yes, I guess I can confirm that. In order to get rid off the cwa crashes I recently hoped that a system update would help. Which obviously did not work out. I used a flashtool from Mediatek for that. The device was recognized as MT6580. More specifically the path to one of the files was named “X511_CQ_7081C_CUBOT_N_V.0.2.0.1.S00708\MT6580”. Thanks for looking into this. Let me know if I could provide anything else useful. BTW: When I use the function “send feedback” when the app crashes. Will that end up in the Nirvana of Google or is it something that you developers have access to ?
I was affected by this issue as well (Android 7.1, even though I had 4GB of internal memory free) and can confirm that it is fixed for me with the just published update to 1.7.1. Thanks for the quick fix!