08-30 12:19:58.982 3778 3778 E AndroidRuntime: FATAL EXCEPTION: main08-30 12:19:58.982 3778 3778 E AndroidRuntime: Process: org.torproject.torbrowser_nightly, PID: 377808-30 12:19:58.982 3778 3778 E AndroidRuntime: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException08-30 12:19:58.982 3778 3778 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:558)08-30 12:19:58.982 3778 3778 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:936)08-30 12:19:58.982 3778 3778 E AndroidRuntime: Caused by: java.lang.reflect.InvocationTargetException08-30 12:19:58.982 3778 3778 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)08-30 12:19:58.982 3778 3778 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)08-30 12:19:58.982 3778 3778 E AndroidRuntime: ... 1 more08-30 12:19:58.982 3778 3778 E AndroidRuntime: Caused by: org.mozilla.experiments.nimbus.internal.NimbusFeatureException: Nimbus hasn't been initialized yet.08-30 12:19:58.982 3778 3778 E AndroidRuntime: 08-30 12:19:58.982 3778 3778 E AndroidRuntime: Calling NullVariables.instance.setContext(context) earlier in the app startup will08-30 12:19:58.982 3778 3778 E AndroidRuntime: cause this error to go away, but won't fix the problem.
08-19 07:32:27.076 26158 26158 E AndroidRuntime: FATAL EXCEPTION: main08-19 07:32:27.076 26158 26158 E AndroidRuntime: Process: com.youneedabudget.evergreen.app, PID: 2615808-19 07:32:27.076 26158 26158 E AndroidRuntime: com.google.android.play.core.internal.zzat: Failed to bind to the service.08-19 07:32:27.076 26158 26158 E AndroidRuntime: at w7.r.n(com.google.android.play:core@@1.10.3:76)...08-19 10:22:20.320 8909 8909 E AndroidRuntime: FATAL EXCEPTION: main08-19 10:22:20.320 8909 8909 E AndroidRuntime: Process: com.cliambrown.easynoise, PID: 890908-19 10:22:20.320 8909 8909 E AndroidRuntime: java.lang.RuntimeException: Unable to start receiver com.cliambrown.easynoise.OutsidePauseReceiver: android.app.ForegroundServiceStartNotAllowedException: startForegroundService() not allowed due to mAllowStartForeground false: service com.cliambrown.easynoise/.PlayerService08-19 10:22:20.320 8909 8909 E AndroidRuntime: at android.app.ActivityThread.handleReceiver(ActivityThread.java:4316)...08-19 10:22:20.320 8909 8909 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)08-19 10:22:20.320 8909 8909 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:936)08-19 10:22:20.320 8909 8909 E AndroidRuntime: Caused by: android.app.ForegroundServiceStartNotAllowedException: startForegroundService() not allowed due to mAllowStartForeground false: service com.cliambrown.easynoise/.PlayerService...8-19 10:22:28.983 9017 9017 E AndroidRuntime: FATAL EXCEPTION: main08-19 10:22:28.983 9017 9017 E AndroidRuntime: Process: com.cliambrown.easynoise, PID: 901708-19 10:22:28.983 9017 9017 E AndroidRuntime: java.lang.RuntimeException: Unable to start receiver com.cliambrown.easynoise.OutsidePauseReceiver: android.app.ForegroundServiceStartNotAllowedException: startForegroundService() not allowed due to mAllowStartForeground false: service com.cliambrown.easynoise/.PlayerService...08-19 10:22:28.983 9017 9017 E AndroidRuntime: Caused by: android.app.ForegroundServiceStartNotAllowedException: startForegroundService() not allowed due to mAllowStartForeground false: service com.cliambrown.easynoise/.PlayerService....08-20 22:04:35.299 30573 30573 E AndroidRuntime: FATAL EXCEPTION: main08-20 22:04:35.299 30573 30573 E AndroidRuntime: Process: com.youneedabudget.evergreen.app, PID: 3057308-20 22:04:35.299 30573 30573 E AndroidRuntime: com.google.android.play.core.internal.zzat: Failed to bind to the service.
it looks like for some reason the nightly wasn't able to get any permissions or work with the play store so immediately failed to launch cus it couldn't lauch required forground services
alpha builds are reported to have worked for user so unsure what the difference between nightly build and alpha build is, cus I dont think in this case there was a code diff?
unsure what the difference between nightly build and alpha build is, cus I dont think in this case there was a code diff?
Mozilla gates some features on the channel.
For the record, Alpha is a custom channel we use, but as a matter of fact when it comes to Android, we build alpha on Moz's beta channel.
Usually, nightly gets a lot of stuff that is still under development.
I don't like what we do: we differentiate channels to apply the different branding, but as a result we also enable the experimental features.
We want our builds to be the same as the release, actually, so we should find a way to swap colors while staying on release.
@richard ah, it looks like the latest nightly is launching, but it has trouble accessing / creating a control port. It seems to crash Orbot completely too that I need to restart the phone it seems.
adb says:
09-19 08:29:07.286 7450 8653 W OnionProxyManager: Control port file not created09-19 08:29:07.286 7450 8653 I FileUtilities: /data/user/0/org.torproject.torbrowser_nightly/app_torservice/lib/tor/control.txt
I uninstalled Orbot and tried the latest nightly (2023.09.28). Weirdly, I'm still getting the same error of "Orbot is starting ..." and throwing the same IOException error.