App broken on Android 10 about mobile

[veloce]

Wait for the version 0.8.15 that should fix it (still in review).

[NewSupKaizo55]

Android 11 is also affected, nothing works as stated in the bug report.

[veloce]

I don't think it's related to an android version, because I also have android 10 and I don't reproduce this issue.

[BennieD]

Anything else I can do to test?
Info I can collect?
Could it be device specific? @NewSupKaizo55 what device do use?
Could it be memory availability?
My device storage: 13Gb/16GB
memory: 711MB/1GB
It seems to mean used / total available.
Lichess Beta usage: storage: 94.45MB
memory: 2.5MB on average in last 3 hours
Permissions: No permissions required (no change from previous version)
Attempt to sign in: no data used
Attempt puzzles: no datat used
Attempt game: no data used
Analysis board usage (Works fine): no data used
Attempt watch: no data used
Donate link (works fine): No data used by Lichess Beta, Data used by Chrome
About Lichess link (works fine): Ditto
All external links works fine.
Lichess Beta start-up screen is Home, but the options to sign in, etc (I cannot remember the other 2 options) expected does not show.
I am testing my wife's Samsung Galaxy A03 core with Android 13 now, will let you know.

*edit:
The start up options that does not show up is: Sign in, Donate, About lichess...
Lichess Beta works correct on Samsung Galaxy A03 Core with Android 13.

*Edit:
Testing airplane mode:
Expected "!Network connectivity unavailable", and watch "Not available in offline mode"
Experienced: no change in app, external links still tries to access lichess.org but report no internet on Chrome
no additional err messages.
App does not seem to realise it has gone off-line.
All this experiences feels like the app does not get connectivity, but does not realise it.

[NewSupKaizo55]

The affected device is a ZTE Blade A31 / Android 11, 2GB RAM, Octa-Core 4x1.6 GHz + 4x1.2 GHz. It is my friend's phone who reported to me that the app was working perfectly before the new update without any problems and now all aspects of the app became unusable as in the bug report.

My phone that I currently use is a Xiaomi Redmi Note 10 5G / Android 13 (MIUI 14), 4GB RAM, Octa-Core 2.2 GHz. There are no problems with the app on my phone at all.

Between the two mentioned devices there is a difference in the Android version, the available RAM and the processors. I don't think the RAM or the processors are the cause because the app was working perfectly before the new update on the weaker device too.

Tell me if I can help another way or if I can provide any more information!

[NewSupKaizo55]

I got some screenshots now:

[veloce]

Considering the number of new crash reports I can tell this bug is due to the cronet http client not found which is very weird because no change to that regard has been made between 0.8.10 and 0.8.12.

[BennieD]

I'm afraid the problem still persists in v0.8.14
Unfortunately I cannot confirm which version still worked, as I don't know if I missed updates in between.
I learn something from this: as beta tester check the current working v nr before update!
(sorry, I'm inexperienced)
@NewSupKaizo55: can you confirm which version still worked for your friend, and did the 0.8.14 update fix the issue?
I cleared cache and data, and restarted the device - still not working.