DHL / Post App (Germany) - login impossible

The recent update of the app has made changes on the login.
Now I’m being redirected and have to login using the browser, however after it complains that the browser (the one e/os shipped with) isn’t supported.

Anyone figured out a way around this, other than installing some other browser?

Install Fennec e.g. as your standard browser. Then you can login into the DHL app. After that you can delete Fennec.

I think the only other way to use the DHL app is to install an older version (like 291001270, that’s ver 8.4.0) via Aurora .

I use Firefox Klar as my standard browser, it’s Chromium based. To my knowledge you need a chromium based launcher for the log-in @DHL app.

wasn’t Klar initially based on chromium but then introduced Gecko again?

Anyway, have Fenix set as browser, can authenticate, enter 2fa, app will crash.

But on subsequent App start works.

Looking at the trace it happens in firebase messaging. Could be due to e/OS + AP blocking some telemetry or this is already the crash reporting being barred, don’t know…

Timeout exceeded while awaiting app exception callback from Analytics listener

crash stacktrace
D GmsHttpFormClient: -- Response --
D GmsHttpFormClient: token=hunter2
E ResolverController: No valid NAT64 prefix (173, <unspecified>/0)
D libcrashlytics: Initializing libcrashlytics version 3.2.0
D libcrashlytics: Initializing native crash handling successful.
W FirebaseCrashlytics: Timeout exceeded while awaiting app exception callback from Analytics listener.
E AndroidRuntime: FATAL EXCEPTION: main
E AndroidRuntime: Process: de.dhl.paket, PID: 14733
E AndroidRuntime: java.util.concurrent.ExecutionException: java.io.IOException: SERVICE_NOT_AVAILABLE
E AndroidRuntime: 	at com.google.android.gms.tasks.g.h(com.google.android.gms:play-services-tasks@@18.0.2:32)
E AndroidRuntime: 	at com.google.android.gms.tasks.g.a(com.google.android.gms:play-services-tasks@@18.0.2:40)
E AndroidRuntime: 	at com.google.firebase.messaging.q.run(R8$$SyntheticClass:43)
E AndroidRuntime: 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
E AndroidRuntime: 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
E AndroidRuntime: 	at o6.c.run(com.google.android.gms:play-services-basement@@18.1.0:7)
E AndroidRuntime: 	at java.lang.Thread.run(Thread.java:919)
E AndroidRuntime: 	Suppressed: oj.i0: [w1{Cancelling}@360068d, Dispatchers.Main.immediate]
E AndroidRuntime: Caused by: java.io.IOException: SERVICE_NOT_AVAILABLE
E AndroidRuntime: 	at com.google.firebase.messaging.u.then(R8$$SyntheticClass:56)
E AndroidRuntime: 	at com.google.android.gms.tasks.k.run(com.google.android.gms:play-services-tasks@@18.0.2:23)
E AndroidRuntime: 	at c2.d.execute(Unknown Source:0)
E AndroidRuntime: 	at com.google.android.gms.tasks.l.zzd(com.google.android.gms:play-services-tasks@@18.0.2:8)
E AndroidRuntime: 	at com.google.android.gms.tasks.y.b(com.google.android.gms:play-services-tasks@@18.0.2:36)
E AndroidRuntime: 	at com.google.android.gms.tasks.c0.u(com.google.android.gms:play-services-tasks@@18.0.2:15)
E AndroidRuntime: 	at com.google.android.gms.tasks.k.run(com.google.android.gms:play-services-tasks@@18.0.2:31)
E AndroidRuntime: 	at com.google.android.gms.cloudmessaging.a0.execute(Unknown Source:0)
E AndroidRuntime: 	at com.google.android.gms.tasks.l.zzd(com.google.android.gms:play-services-tasks@@18.0.2:8)
E AndroidRuntime: 	at com.google.android.gms.tasks.y.b(com.google.android.gms:play-services-tasks@@18.0.2:36)
E AndroidRuntime: 	at com.google.android.gms.tasks.c0.u(com.google.android.gms:play-services-tasks@@18.0.2:15)
E AndroidRuntime: 	at com.google.android.gms.tasks.e.b(com.google.android.gms:play-services-tasks@@18.0.2:3)
E AndroidRuntime: 	at com.google.android.gms.cloudmessaging.q.d(com.google.android.gms:play-services-cloud-messaging@@17.0.0:59)
E AndroidRuntime: 	at com.google.android.gms.cloudmessaging.s.a(com.google.android.gms:play-services-cloud-messaging@@17.0.0:11)
E AndroidRuntime: 	at com.google.android.gms.cloudmessaging.h.handleMessage(com.google.android.gms:play-services-cloud-messaging@@17.0.0:109)
E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:103)
E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:214)
E AndroidRuntime: 	at android.app.ActivityThread.main(ActivityThread.java:7356)
E AndroidRuntime: 	at java.lang.reflect.Method.invoke(Native Method)
E AndroidRuntime: 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:491)
E AndroidRuntime: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:940)
W ActivityTaskManager:   Force finishing activity de.dhl.paket/de.its_berlin.dhlpaket.base.main.MainActivity
I DropBoxManagerService: add tag=data_app_crash isTagEnabled=true flags=0x2
I Process : Sending signal. PID: 14733 SIG: 9
D ConnectivityService: ConnectivityService NetworkRequestInfo binderDied(NetworkRequest [ LISTEN id=1000, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&FOREGROUND Uid: 10144] ], android.os.BinderProxy@fbc1b72)
D ConnectivityService: ConnectivityService NetworkRequestInfo binderDied(NetworkRequest [ TRACK_DEFAULT id=999, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10144] ], android.os.BinderProxy@fa09bc3)
I WindowManager: WIN DEATH: Window{d44dda8 u0 de.dhl.paket/de.its_berlin.dhlpaket.base.main.MainActivity}

Edit: version: 9.0.4.12 in /e/-1.8.1-Q … SERVICE_NOT_AVAILABLE (now on every start) must be related with the device not registering for some GCM facility imo - something changing at the play services end / in gcm registration

Can’t confirm on /e/OS 1.7-s-20230111250406-dev-FP3 with Post & DHL (de.dhl.paket) Version 9.0.4.12-(e0421304ba) according to Settings - Apps - Post & DHL (bottom of the page).

The App informed me about the need of a Chrome or Firefox based browser, then redirected to the login page (my default browser is Fennec), login worked, the App works as usual for me so far.

Version?

The same, which is the most recent as of now.

as the crash is within GCM… if I disable/disallow the push messages registration the App seems to continue to run, login works. Haven’t checked package retrieval (the function that probably needs push, but then… a refresh probably just makes some requests)