This was detected in other AI2 distros and it was the main reason I switched to Niotron. Unfortunately, after the New Update 2.7.0, this horrible bug also came to Niotron builder.
This was previously reported on the beta server, but still not fixed before the update.
There is nothing in blocks, nor decompiling the apk, that is possible as a quick or permanent fix to it. I’ve already tried several ways (maybe I lack knowledge), but nothing has been able to prevent, even provisionally, this event.
Before Update
After Update
Please, kindly take a look at this issue and be the first among others to solve it.
@Fabio We sincerely apologize for any inconvenience this may have caused you. Please let me know if you used any screen-changing animations or changed the orientation from portrait.
In this project, yes, but the issue occurs in a simple, white page, project. I just forgot to mention that the screen is set to portrait and the device has to be (a bit) in landscape position.
If you are talking about phone position, yes. But if you’re talking about configuration, no. The screen orientation is set to portrait and the phone screen orientation is locked, even so the bug happens.
I understand your point, and it’s kind of sad that this is only happening to me, some community users (in all AI2 distros) or those who have tested for me.
MotoG20 Android 11
Galaxy A10 Android 11
Zen Phone Android 8.1
Moto G5 Play Android 7
Redmi 7 Android 10
Nox Player (Emulator) Androids 7 and 9
There’s no specific APK, because even a blank project, as your test one, shows this behavior.
I use a procedure to make screen responsive for all devices and that makes the bug even more visible. However, if it’s a simple project without this procedure, the behavior is still shown.
And this is very occurred. For user who use app