tedit development and design discussion
-
@domubpkm same on opo5, focal, rc. also swiping leads to a crash as well as switching between applications.
-
@messayisto Same on Redmi Note 9S, but as I don't think I did try this before, I have doubts that it could be related to OTA-7... (?)
-
@stanwood good point, I'm not shure, too...
-
I'm just saying that now (OTA-7), the crash is systematic, whereas before OTA-7, this was not the case, always sometimes.
-
@domubpkm I just tested tedit, had the issue with the crash. Then I tried something and installed a new build, now everything is gone again. Even if there are no changes on code side.
I am quite sure its nothing related to OTA7. But I am afraid I have no idea what exactly is the reason for the crashes. They are gone here now. Please try clearing the apps cache and maybe another reboot. Although I am aware that this is no good solution.
-
Maybe everyone who has that issue, please try to remember what you did before when this happens. Did you import or save a file? Open another file? Is this only with new files or also with existing files? Do you have some content in clipboard...
Just guessing, whatever you do, but maybe you can reproduce it somehow which then would give us a better idea where to start fixing.
-
@danfro hum. The only thing I can say that I created a new file before. Then I tried to copy one word from this file and pressed it. Tedit crashed. I openend it again while another app was running (Morph). I tried to switch from tedit to the other app and it crashed again.
-
@danfro My test was the simplest one: Just open Tedit, type "test" on the field, then press and hold my index finger on the word ‘test’ that I've just written. The app closed immediately.
Now I just tried something even more simple: Open Tedit, press and hold in the empty space (nothing has been written), and the app closed (crashed) as well.
In both cases, no other app was opened nor active.
Hope that it can help...
-
@messayisto and @stanwood When the bug occurs, I can reproduce exactly the issues you descibe. But right now they are all gone here. So something must trigger it.
Could you please try the build from the latest pipeline? When building there was an error with a regex that is used for parsing a file name. Just a shot in the dark. But it can't hurt (hopefully
).Although part of me expects it to fix it, just to come back later.
-
@danfro said in tedit development and design discussion:
Could you please try the build from the latest pipeline?
Ouh... Don't know how to install this, I couldn't find the .click file in the "artifact.zip". But I acknowledge that I'm not skilled at all....
-
@stanwood No worries. First make sure you get the right artifacts file. Most devices are arm64 (64bit), but some older ones are armhf (32bit). Download that file on your device and extract it in file manager. Then hop into that folder and go builds/aarch64-linux-gnu/app. There you should find a .click file. Click on that, you should be asked to open it with another app. Pick OpenStore there to install it.
-
@danfro The difficulty is that now we don't even see the artifacts with morph! Could you link the artifact here please
! arm64 -
-
@danfro Thanks ! No crash (currently) with the artifact. However, with the latest official built, I cleared the cache, and I didn't get any crashes after that too.
-
@domubpkm Thanks for testing. Yes, clearing the cache did help before too. I assume when I build the app with clickable, this clears the cache as well. No idea why something in the cache can make the app crash though...
-
@danfro Installed from artifacts, cleared the cache again, app still crashes.
-
@danfro I don't know anything about it, but couldn't it have something to do with the size of Tedit's cache?
-
@messayisto Same here: Deleting cache + config + data does not help.
Redmi Note 9S Stable
If God has a computer, it must be a GNU/Linux -
@domubpkm App cache is handled automatically. I don't think there is anything I can do about the size, except maybe clear cache every time tedit is closed.
-
@stanwood and @messayisto very strange. Just to be safe, did you also try a reboot?
Could you please check the apps log and see if there is anything in it? All I see is an error about a binding llp in TextInputPopover. But that is also when not crashing, so likely not related.
Hard to track down if not reproducible. But a very annoying bug...
