-
Notifications
You must be signed in to change notification settings - Fork 27
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
Crash when importing ics file exported from calendar-import-export #94
Comments
I encounter the same issue after updating to v2.7. The app crashed when opening a file. After uninstalling and reinstalling, the app opened but crashed when charging the ics file. |
Hi, same crash for me with 2.7 - thank you very much, red-black-bonsai for telling us, that version 2.6, manually chosen in f-droid, is working fine, so it does for me. |
Thanks for reporting this. The work-around 58b337c works reproducibly for me so I branded a new release which should be available on F-Droid within a few days. |
There is now a release 2.7.1 available at https://f-droid.org/en/packages/org.sufficientlysecure.ical/ – please check whether this resolves the issue you experience. |
I have tried 2.7.1 version but it didn't change anything. It still crashes when opening a file. I had to return to 2.6.0 |
I'm having crashes on 2.7.2 still with importing calendar files. I open the ICS from my email app and as soon as I press Load in this app it crashes. |
Here's an ICS file that causes a crash. I changed the file extension so GitHub would upload it. |
I confirm @skylarmt comment. It doesn't work either with the 2.7.2 version. This time it crashes when loading the ICS file. I can't downgrade to 2.6.0 anymore because FDroid shows only the last 3 versions :(. Is it possible to to download the apk files through Github? |
I can reproduce the error: it occurs during the static initialization of net.fortuna.ical4j.util.Configurator. Applying the work-arodung suggest in https://stackoverflow.com/questions/60018008/android-apache-logger-crashes-for-no-reason-in-production-release-build helps, see 1b3ab38. A new release is schedule, stay tuned. |
Unfortunately, version 2.7.4 is even worse than 2.7.2. In the last version the app crashed when selecting an ics import file. Now it already crashes when you just click on "import file"... |
Can confirm worse behavior - crash on "import file" with 2.7.4. With clean installed A12L (5.April 22 Patch) Rom. |
Unfortunately, I cannot reproduce the issue, using android emulator with Android 12.0 / API 31 / x86_64. Since the crash is reported to happen when clicking »import file«, the exact content of the file should be irrelevant. There must be subtle differences with the setup. Actually, there have been a lot of participants in this thread. Are there any among you who get along with 2.7.4? This could give important clues what goes wrong here. |
I'm running 2.7.4 from F-Droid. My device is Android 11 (LineageOS 18.1) on ARM64, no GApps. Here's my logcat when I press Import File:
|
I cannot reproduce the behaviour, but the log clearly points to the line changed in a23e732 There are hints that the Android framework uses a fixed version of the Commons Codec library, cf. https://stackoverflow.com/questions/9126567/method-not-found-using-digestutils-in-android/29833101#29833101 Speculatively it is better to avoid to rely on inheritance here, maybe that plain static method call works better. If this doesn't help either, I plan to go with https://github.com/ExCiteS/apache-commons-codec-shaded and include a whole clone of Commons Codec. |
Many thanks. Sry, just had time to test now but it does work with 2.7.5, could import without errors. 😃 |
Well done! Import with 2.7.5 works fine again! Thanks you 👍🏻 |
2.7.5 works for me too. |
2.7.5 works for me too but when I open a file, then load it, I have two instances of the app. |
To migrate the local calendar from phone A to phone B, I created an export with CIE on phone A, copied the ics to phone B and tried importing. CIE, version 2.7, just closes/crashes.
Installing CIE version 2.6 from F-Droid store (after first uninstalling version 2.7) on phone B alleviates the problem. With it, I can import fine (even a file generated by 2.7 on phone A) :)
Potentially relevant log from import on phone B:
If I disable permissive export on phone A, I also get this error in phone A's log:
The text was updated successfully, but these errors were encountered: