-
Notifications
You must be signed in to change notification settings - Fork 386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Etar is crashing. #176
Comments
Which Etar version runs on your phone ? In a few days there will be version 1.0.10. Without a debug log it would be hard to determine why Etar crashes on your phone and I don't have a 7.1.1 device. |
I have etar version 1.0.9 from F-Droid installed. The problem with the log is, that the app crashes before a have any chance to enter it. Is there any other way to enable the log? |
you can use |
The red E is the error, but you need to press it, to toggle the information. Also, if you long press on the error, you can copy it the the clipboard and paste it here. |
There are not more information given by catlog. You can see, i toggled everything by pressing the second button on the top. I tested it again and the same errors appeared, but additionally this error was displayed: 02-22 21:13:16.244 E/InputDispatcher(2514): channel '52df068 ws.xsoh.etar/com.android.calendar.AllInOneActivity (server)' ~ Channel is unrecoverably broken and will be disposed! |
There should be a backtrace in there, maybe catlog can't show it. Do you have access through adb? |
I tried Version 1.0.8 from F-Droid and it´s working. Afterwards i tried to install 1.0.9 again, but it´s crashing again at start up. Ich could try adb tomorow. |
I tried it with the 7.1.1 simulator but there are no crashing after start up. So we need full debug log. |
Got the same problem here. Etar is working fine on version 1.0.8, and don't work on versions 1.0.9 and 1.0.10 on my phone (Android 7.1.1 me too). Here is logcat when I start Etar version 1.0.10 :
Here is logcat of Etar version 1.0.8 which is working :
|
@chteufleur thanks for your report as well! Is one of you able to build Etar from git and do a bisect? Otherwise, please contact me via mail (in my profile) and I will send you debug builds. Thanks! |
you could add a very simple crash capture like i did with Antox: its just 1 small function and a line in the AndroidManifest.xml added to the <application> tag:
it will save the crashlog file to SD card (works without root) |
Interesting, the other option would be https://github.com/ACRA/acra, that's what f-droid is using, for example. |
oh no, please don't use ACRA. |
Any reason why (email is fine, as well)? |
Thanks to @chteufleur for helping with the bisect of this one. Most probably the broken commit is: b79f09d. @Gitsaibot could check if there is something wrong with it or if you find other commits related to it? |
Thanks to the commit message, I check if my Android system allow Etar to acces the stockage. The permission was not allowed. |
@N3dal can you confirm this ? |
Sorry for answering so late and for not helping solving the problem. I was very busy and had no time for this. |
Same probleme here with the last version. |
@N07070 Have you tried the work around? Didn´t that work for you? |
@N3dal indeed, the permission was not put in place. |
The ImportActivity needs READ_EXTERNAL_STORAGE upon start if EXPORT_SDCARD_DIRECTORY (/sdcard/CalendarEvents) exists. As we need write permission for export anyhow, this simply asks for both permissions at startup.
I think I was able to reproduce this. We need storage permission if the directory /sdcard/CalendarEvents exists. This should be fixed by 5a9b46b. @N3dal @chteufleur can you check if you have that directory? |
@jspricke yes, i have this directory. |
Yesterday everything was fine with etar, today it´s crashing instantly. I don´t know what could be the problem, i didn´t changed anything ( major ) on my phone. ( Android 7.1.1 )
I deisntalled the app and installed it again, but the app is crashing instantly, after asking for calender access, with im allowing.
EDIT: Stock calender is still working.
The text was updated successfully, but these errors were encountered: