Status Update
No update yet.
Comments
ra...@google.com
ia...@gmail.com
Hello everyone. Is this bug going to be fixed? I have to install 3rd party app to emulate the location. I really need this feature. Please, fix it.
su...@google.com
to...@googlemail.com
su...@google.com
Also keeps loading when uploading saved route.
SDK does not change anything, I'll try changing API 33 to another one maybe that's the issue.
Ubuntu 22.04
to...@googlemail.com
I tried several API emulators (23 to 33).
Also tried deleting and creating emulators again.
Also tried rolling back the emulator version a couple of versions prior.
Calling the emulator in the command line instead of in the IDE, does not solve it either.
Nothing worked and I have both problems: map does not appear and when clicking the routes, it gets stuck on Loading.
su...@google.com
For now as a workaround you can you the flatpak version as suggested by @Torben
su...@google.com
Same problem on Ubuntu 22.04. It's been broken for 3 months, is there any way to get someone at Google to take notice of this problem? Android Studio cannot be used for location based development on Linux.
Note that the Flatpak version is not an official distribution. Page says "NOTE: This wrapper is not verified by, affiliated with, or supported by Google."
Emulator is https://dl.google.com/android/repository/emulator-linux_x64-8420304.zip
to...@googlemail.com
Same problem on the latest Fedora 36 with kernel 5.18! I have to install 2 or more Android Studio on my PC to debug the app with Location. There isn't flatpak of Canary build :(
su...@google.com
Has anyone checked with KDE DE? Maybe Flatpak version is using KDE Framework Flatpak Dependency and it is working?
to...@googlemail.com
to...@googlemail.com
ap...@google.com
su...@google.com
Any progress on the issue? It been present for more than 4 months, I would really love to just be able to run my emulator through terminal and not have to worry about this issue.
Description
Version used: 1.0.0-alpha09
When using ProGuard, the Worker(Context context, WorkerParameters) constructor isn't kept, leading to Workers being unable to be created:
DefaultWorkerFactory: Could not instantiate com.google.android.apps.muzei.sync.ProviderChangedWorker
DefaultWorkerFactory: java.lang.NoSuchMethodException: <init> []
DefaultWorkerFactory: at java.lang.Class.getConstructor0(Class.java:2327)
DefaultWorkerFactory: at java.lang.Class.getDeclaredConstructor(Class.java:2166)
DefaultWorkerFactory: at androidx.work.DefaultWorkerFactory.createWorker(DefaultWorkerFactory.java:58)
DefaultWorkerFactory: at androidx.work.impl.WorkerWrapper.runWorker(WorkerWrapper.java:180)
DefaultWorkerFactory: at androidx.work.impl.WorkerWrapper.run(WorkerWrapper.java:117)
DefaultWorkerFactory: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
DefaultWorkerFactory: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
DefaultWorkerFactory: at java.lang.Thread.run(Thread.java:764)
WorkerWrapper: Could for create Worker com.google.android.apps.muzei.sync.ProviderChangedWorker
I had to manually add the ProGuard rule:
-keepclassmembers class * extends androidx.work.Worker {
public <init>(android.content.Context,androidx.work.WorkerParameters);
}