tedit development and design discussion
-
@domubpkm confirmed on oneplus 5, focal, rc
-
@ma I can NOT confirm on my OP5T.
I open the app, press power button to lock. Then either press power button again or double tap to wake and unlock. Tedit is still open and doesn't close.
You don't press accidentally the new "exit" button in the top right corner maybe? Not sure where your power button is located. Just to rule that out.
-
@danfro hmm, I CAN confirm it on my Xperia X. But so far no idea why that happens. At least I have a device to test it.
-
@danfro Can't use screen recorder to show the bug because screen recorder crashes on start currently on volla
-
@domubpkm same on opo5
-
@danfro Strange thing, the problem is no longer there now. I cleared the cache of all apps, which I do regularly, then turned the smartphone off and on again. Something must have had an effect somewhere.
-
@domubpkm I did the same - clearing all caches and turning off and on - but the issue still remains.
-
This thing is a mystery. I can't reproduce it on my Xperia X anymore, didn't had it on my OP5T at all. Maybe it matters if other apps are open? Then which apps? Does tedit need to be in foregroud or does it crash in background too?
A tough riddle...
-
@danfro That makes sense, I get it
Thanks for the app! -
This effect even exists when I quickly switch between two apps (fast slide from the ride edge).
-
This post is deleted! -
@danfro No, it doesn't matter what other app is open. If I quickly switch between two apps (quick swipe from the right side), the app crashes when I try to bring it to the foreground. If I send it to the background, it doesn't crash. I use an OP5T.
-
@ma same behaviour on opo 5, focal, rc.
-
When I lock and then unlock the device, the app only crashes when it is in the foreground.
-
Could you please do a reboot and see if the problem persists? I currently can't reproduce it anymore on my two devices.
But might have to do with the app either being in foreground or being brought to foreground.
-
@danfro The problem persists even after a restart.
It gets even crazier. If I quickly scroll through a long note, the app also crashes.
-
@ma very strange. I am scrolling through a full log of Teleports (that IS long
), but all working fine. I am so sorry this is happening. But I have no idea why that happens. I assume this wasn't the case with the last version, right? -
No, I would have definitely noticed.
-
@ma As a shot in the dark, I created a branch without the exit button. If you have time, could you please test the build from the latest pipeline and see if this does solve the problem?
Maybe, just to make sure we hit the right thing, reinstall the app with the current OpenStore version and then install this test build.
-
I'm sorry, but I don't know how to install it.
OP5T = build-arm64?