Bliss Launcher Crash Loop related to WeatherUpdateService
- /e/ version: 1.11
- Device model(s): Redmi Note 8T (ginkgo)
Summary
Without any clear cause (no settings changes, updates, new apps or similar that I'm aware of), Bliss Launcher went into a crash loop today.
The phone is utterly unusable in this state.
I noticed in the brief moments the launcher was usable that the weather widget had turned blank.
- Clearing Bliss Launcher cache does not resolve the issue
- Clearing Bliss Launcher data does not reslove the issue (resets all icon positions)
- Rebooting the phone does not solve the issue
- Shutting down and booting up again did not resolve the issue
- Removing the weather widget did not resolve the issue
- Switching off location spoofing in the Advanced Privacy widget did not resolve the issue
Technical informations
Stack trace obtained via the Scoop app:
FATAL EXCEPTION: main
Process: foundation.e.blisslauncher, PID: 6149
java.lang.RuntimeException: Unable to start service foundation.e.blisslauncher.features.weather.WeatherUpdateService@19dbbc2 with Intent { act=org.indin.blisslauncher.action.FORCE_WEATHER_UPDATE cmp=foundation.e.blisslauncher/.features.weather.WeatherUpdateService }: java.lang.IllegalArgumentException: provider doesn't exist: network
at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:4338)
at android.app.ActivityThread.access$1800(ActivityThread.java:237)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1951)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:223)
at android.app.ActivityThread.main(ActivityThread.java:7664)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
Caused by: java.lang.IllegalArgumentException: provider doesn't exist: network
at android.os.Parcel.createExceptionOrNull(Parcel.java:2378)
at android.os.Parcel.createException(Parcel.java:2358)
at android.os.Parcel.readException(Parcel.java:2341)
at android.os.Parcel.readException(Parcel.java:2283)
at android.location.ILocationManager$Stub$Proxy.getCurrentLocation(ILocationManager.java:1259)
at android.location.LocationManager.getCurrentLocation(LocationManager.java:730)
at android.location.LocationManager.getCurrentLocation(LocationManager.java:688)
at androidx.core.location.LocationManagerCompat$Api30Impl.getCurrentLocation(LocationManagerCompat.java:976)
at androidx.core.location.LocationManagerCompat.getCurrentLocation(LocationManagerCompat.java:186)
at foundation.e.blisslauncher.features.weather.location.NetworkGpsLocationFetcher.fetchLocation(NetworkGpsLocationFetcher.java:36)
at foundation.e.blisslauncher.features.weather.WeatherUpdater.fetchNewLocation(WeatherUpdater.java:128)
at foundation.e.blisslauncher.features.weather.WeatherUpdater.updateWeather(WeatherUpdater.java:105)
at foundation.e.blisslauncher.features.weather.WeatherUpdater.forceWeatherRequest(WeatherUpdater.java:79)
at foundation.e.blisslauncher.features.weather.WeatherUpdateService.onStartCommand(WeatherUpdateService.java:45)
at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:4320)
... 8 more
Caused by: android.os.RemoteException: Remote stack trace:
at com.android.server.location.LocationManagerService.requestLocationUpdatesLocked(LocationManagerService.java:1964)
at com.android.server.location.LocationManagerService.requestLocationUpdates(LocationManagerService.java:1947)
at com.android.server.location.LocationManagerService.getCurrentLocation(LocationManagerService.java:2114)
at android.location.ILocationManager$Stub.onTransact(ILocationManager.java:510)
at android.os.Binder.execTransactInternal(Binder.java:1159)
Solutions
Workaround
I am not aware of any workarounds, installing a different launcher might work but I haven't tried. Device seems to be unusable until this is resolved.
Edited by Nanabanaman