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
getTimeZone() causes NPE #229
Comments
Same as #219 |
I have opened it again because the other issue is about returning |
Same thing happening here, with 2.0.0. What's the status of this? Any ideas? workarounds? |
@noloman Does it happen in Android 8.0.0 only or on other platforms? Meanwhile I assume this is some kind of firmware bug, especially because the NPE happens in |
@rfc2822 it only happens (for now on Android 8.0.0) but it only happens when using the library for parsing a DateTime. Is there any known workaround, even if it's modifying the backend? Thanks for the good work guys! |
BTW this is also happening on other versions of Android, not only 8. Could it maybe not be an Android bug? |
@noloman On which other version have you seen that? We have only seen it with Android 8.0, although we have many users with various versions. Uninstalling the app and installing it again sometime fixes the problem magically, which is very strange… For reference, this is our thread: https://forums.bitfire.at/post/9654 |
well unfortunately, telling our customers to remove and install the app is really not a suitable solution, as you will understand. |
@noloman Same here (not reproducible). At the moment, I think it may be somehow related to an Android cache… And we tell our customers to re-install, too… just because there's no better solution at the moment. This is why I have mentioned it. |
If you have suggestions on how to work around the issue let me know (eg extra error handling) |
well I can give you guys several datetime strings in the ICS that can't be parsed (20180714T193000 for example). If you try to debug with that String -I haven't personally tried THAT string, but I have tried with others- you can dive into the debug until you reach the NPE |
Hi, BTW in which versions, if any, can you guys NOT reproduce this? I was using 2.2.0 and I have upgraded now to 3.0.1, so hopefully this crash won't happen again? |
Unfortunately, upgrading to 3.x is not an option for me, because we have to support Android <7, too (and ical4j 3.x requires JDK 8 libraries, which are only available on Android 7+). |
What do you mean?
I have upgraded and built gradle plus executed the app in an emulator
(Oreo) but I didn't have any issue. Is it supposed to crash if it's run in
< Oreo?
Op di 4 sep. 2018 17:38 schreef rfc2822 <notifications@github.com>:
… Unfortunately, upgrading to 3.x is not an option for me, because we have
to support Android <7, too (and ical4j 3.x requires JDK 8 libraries, which
are only available on Android 7+).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#229 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AALL4GQ2Kys9tEOoldubUbSk4qBQmeo8ks5uXp6OgaJpZM4TZtST>
.
|
Yes, or does it work for you in <Oreo emulator? There are many operations which rely on the Java 8 API, which requires Android >= 7. Java 8 bytecode wouldn't be the problem, but the API… |
Indeed @rfc2822 I understood it completely wrong: it is crashing on devices with Android < Nougat, but working on the newer versions |
Theoretically, it should be possible to make a class loader which dynamically injects the required classes for Android < 7… |
Hello 👋 |
ical4j 2.2.20, Android
When calling
getTimeZone()
on a registry created byTimeZoneRegistryFactory.getInstance().createRegistry()
, it sometimes generates aNullPointerException
:I don't know which time zone causes the problems yet, but I think
getTimeZone()
should not throw an unchecked exception in any case.The text was updated successfully, but these errors were encountered: