Status Update
Comments
ru...@gmail.com <ru...@gmail.com> #2
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 <su...@google.com> #3
ru...@gmail.com <ru...@gmail.com> #4
ra...@google.com <ra...@google.com> #5
ra...@google.com <ra...@google.com> #6
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...@gmail.com <to...@gmail.com> #7
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.
ru...@gmail.com <ru...@gmail.com> #8
For now as a workaround you can you the flatpak version as suggested by @Torben
ru...@gmail.com <ru...@gmail.com> #9
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
ed...@gmail.com <ed...@gmail.com> #10
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 :(
da...@gmail.com <da...@gmail.com> #11
Has anyone checked with KDE DE? Maybe Flatpak version is using KDE Framework Flatpak Dependency and it is working?
Description
Version used: implementation 'android.arch.work:work-runtime:1.0.0-alpha12'
Devices/Android versions reproduced on: Moto e3 Power / Andorid 6.0 Marshmallow
Sometimes Periodic workManager gets called two times.
This is my built.gradle file:-
compileSdkVersion 28
minSdkVersion 22
targetSdkVersion 28
versionCode 1
versionName "1.0"
multiDexEnabled true
testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
Here is this code:-
//---------------------------------------------------------Class Login---------------------------------------------------------------------------------------//
SaveData("Frist");
PeriodicWorkRequest periodicWorkRequest = new PeriodicWorkRequest.Builder(DailyLogoutTask.class,
1, TimeUnit.DAYS)
.build();
WorkManager.getInstance().enqueueUniquePeriodicWork("DailyTaskRestaurantLite"
, ExistingPeriodicWorkPolicy.KEEP
, periodicWorkRequest);
private void SaveData(String str) {
SharedPreferences.Editor preferencesEditor = mPreferences.edit();
preferencesEditor.putString("Status1", str);
preferencesEditor.apply();
}
//------------------------------------------------------Class DailyLogoutTask-----------------------------------------------------------------------//
import android.content.Context;
import android.content.SharedPreferences;
import androidx.annotation.NonNull;
import android.util.Log;
import com.domo.ClsGlobal;
import com.demo.classes.ClsUserInfo;
import androidx.work.Result;
import androidx.work.WorkManager;
import androidx.work.Worker;
import androidx.work.WorkerParameters;
import static android.content.Context.MODE_PRIVATE;
public class DailyLogoutTask extends Worker {
private SharedPreferences mPreferences;
private static final String mPreferncesName = "MyPerfernces";
Context context;
public DailyLogoutTask(@NonNull Context context, @NonNull WorkerParameters workerParams) {
super(context, workerParams);
this.context = context;
mPreferences = context.getSharedPreferences(mPreferncesName, MODE_PRIVATE);
Log.e("DailyLogoutTask", "DailyLogoutTask call");
}
@NonNull
@Override
public Result doWork() {
String getstatus = mPreferences.getString("Status1", "No Task Perform");
Log.d("---getstatus---", "----getstatus---" + getstatus);
Log.e("doWork", "doWork call");
if (!getstatus.equalsIgnoreCase("Frist")) {
ClsUserInfo userInfo = new ClsUserInfo();
ClsUserInfo userLoginStatus = ClsGlobal.getUserInfo(context);
if (!userLoginStatus.getLoginStatus().equalsIgnoreCase("DEACTIVE")){
Log.e("chack", "Logout");
userInfo.setLoginStatus("DEACTIVE");
ClsGlobal.setUserInfo(userInfo, context);
// ClsGlobal.sendNotification("IF", "IF background Logout".concat(ClsGlobal.getEntryDate()),context);
WorkManager.getInstance().cancelUniqueWork("DailyTaskRestaurantLite");
Log.d("getFirstDateOfMonth", "----UserInfo---" + userLoginStatus.getLoginStatus());
}
} else {
Log.e("chack", "Not Frist");
// ClsGlobal.sendNotification("ELSE", "ELSE background Logout".concat(ClsGlobal.getEntryDate()),context);
SaveData("Second");
}
return Result.success();
}
private void SaveData(String str) {
Log.e("SaveData", str);
SharedPreferences.Editor preferencesEditor = mPreferences.edit();
preferencesEditor.putString("Status1", str);
preferencesEditor.apply();
}
If this is a bug in the library, we would appreciate if you could attach:
- Sample project to trigger the issue.
- A screenrecord or screenshots showing the issue (if UI related).