-
-
Notifications
You must be signed in to change notification settings - Fork 95
repeated crash log, while opening the app #41
Comments
Unfortunately emailing it or creating an issue is the easiest way to send crash logs at the moment, though I am planning to work on Crasher/#3 in the future which would make it a bit easier. |
@machiav3lli if you're up for testing, you can find the APK for the last commit here - hopefully it should fix some of these issues (or at least give me a better idea of what's going on): https://dl.bintray.com/18jafenn90/builds/013ae313620f660784b8285ce2df90899e678dbe/app-oss-debug.apk |
it doesn't install over the old version, so I had to uninstall the old one and then install the new one, maybe you should use a higher Version for the later test builds. I'll be reporting as soon as I get a crash or in three days if I don't. maybe you can implement the clock shortcut we talked about here [https://github.com//issues/34] in the next test build. |
@machiav3lli sorry about that, it's a debug build so it will have a different signature from the release APKs. I will not be making a Telegram group, there is a Discord server here for that purpose. |
One suggestion about the UI, maybe it's better keeping the red switches even in the AMOLED theme. |
@machiav3lli The continuous notification is necessary to keep the application from being automatically killed by the system when the user leaves the page (reference: services overview). If you do not want a notification, you can cancel the timer before leaving the app. If you have other suggestions, please open them in a separate issue to avoid digressing too far from the original topic. |
I think that the permission ignore battery-optimisations is enough to keep the app from being killed and it did at least work for me (doing timers mostly 20-50 minutes). and sorry for mixing things up |
happy to report that I didn't have any crash since I started using the debug version you sent before. thanks |
this error happens mostly two or three times a day(I open the app mostly 6-8 times a day), I ignored it for sometime, but now I think there's maybe a real problem.
is there a more convenient way to send the logs without emailing it.
maybe instead of share, a linking to upload it to a server or something like that.
thanks.
The text was updated successfully, but these errors were encountered: