@MrGutsy It should be possible to set up the account with the working connection (4G) and then sync over WiFi, too.
Sync fails with KotlinNullPointerException if a particular event is present
-
For the past few days, whenever DAVx⁵ syncs, the sync fails with KotlinNullPointerException, which is displayed in a notification banner. Looking at the debug log and removing the offending event from my Fastmail calendar allows sync to succeed again. Re-adding the offending event causes it to fail.
The event is one my partner invited me to. It is rather personal so I have redacted my partner’s email address, the event title, the Google Meet URL, and all UUIDs in the debug info, replacing them with
x
orX
to the appropriate length. Everything else in this debug log is left alone:https://willthompson.co.uk/misc/davx5-info.txt
With this event removed, sync succeeds, including new events I create or delete on my phone or on the server.
-
Some further research:
- I edited the
.ics
from the invitation to remove theATTENDEE
andORGANIZER
fields and imported it back into my Fastmail calendar; sync succeeded. - I imported the unedited file, without accepting, maybe-ing or declining the event; sync succeeded.
- I accepted the event; now DAVx⁵ crashes again in the same way.
I don’t speak Kotlin, but I would guess it’s the
!!
operator here:date.timeZone = DateUtils.ical4jTimeZone(zone.id)!!
- I edited the
-
Guess so too. Ill try to fix it and release the next hotfix if I can.
-
-
Will do!
-
Should be fixed with 3.2.1.1, which will be released now
-
I have sent an email with the APK. Can you please check whether it now works for you?
-
It works. Thanks for such a quick fix!
-
Will 3.2.1.1 be released on F-Droid? I’ve started experiencing this same exception yesterday with a FastMail calendar on 3.2.1. (Wouldn’t surprise me if it also had to do with a Google Meet event, since I have a couple of those.)
-
@myersjustinc said in Sync fails with KotlinNullPointerException if a particular event is present:
Will 3.2.1.1 be released on F-Droid? I’ve started experiencing this same exception yesterday with a FastMail calendar on 3.2.1. (Wouldn’t surprise me if it also had to do with a Google Meet event, since I have a couple of those.)
Seems like they have published it 53 minutes ago.