Sunik Kupfer

I also created a new clean **A13** emulator just to verify, but it does **_not_** happen here at all (same steps). It all just works as it should.

Also just found: https://github.com/UweTrottmann/SeriesGuide/issues/953 The sync framework really is a mess to deal with. Makes me think, maybe it's soon time for: https://github.com/bitfireAT/davx5/issues/247

Also interesting: https://issuetracker.google.com/issues?q=isSyncPending TL;DR: - It might just happen on the emulators - Calling: `ContentResolver.cancelSync(account, null)` after finishing a sync (i.e. when sync adapter stops waiting) could update the cached...

Calling `ContentResolver.cancelSync(account, null)` when a sync is requested by the sync adapter framework kind of works. The pending sync will not be cleared immediately, but a few seconds after the...

That's right. I would be surprised if calling `cancelSync` for the sync framework, after enqueuing our worker sync, could have any dire consequences for us. I would take the risk....

Ok, I don't think ~`cancelSync(null,null)` or~ `cancelSync(account, authority)` would be dangerous for us, but we could still go with a much safer version. The method doc for `cancelSync(SyncRequest request)` says...

I checked the verbose logs. Regarding the changes google made to `isSyncPending`, these lines do not appear in Android 13, but only Android 15 (some, of them show in Android...

Correct. Unfortunately we are on the final release of ical4j and won't be able to update to 4.x.x without a lot of work - not to mention DAVx5 would have...

> We can try on 4.0.4 using the test I made for https://github.com/ical4j/ical4j/issues/651, I think it shouldn't be too much. Your test does not fail anymore. Not sure why, but...

Will probably not be able to solve this within the next version.