-
-
Notifications
You must be signed in to change notification settings - Fork 74
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
Getting: EXCEPTION java.lang.NoClassDefFoundError: at.bitfire.vcard4android.property.CustomScribes #511
Comments
Same here, this update somehow broke contacts sync with nextcloud. Calendar sync is working fine. |
Same here |
+1 can't sync with NextCloud when a contact is updated at server side or can't add a new account |
Same. I added a new contact and when syncing, it gave me this error. After I removed the new contact, the sync goes fine. |
+1 Also it only syncs a small part of my nextcloud contacts. Posted the exception below. If detailed logs are needed I can strip the personal info and add it. But had the feeling that this might suffice. EXCEPTION
|
Procedure to test:
Tested with:
I've not been able to reproduce on new devices, however, my tablet is throwing a similar error, but with Some debug information: debug-info.zip I can also confirm that the error is not temporal. It happens all the time when trying to synchronize after having modified a contact. More logs: logcat.txt |
Reinstalling the app fixes the issue for some reason, at least for me, though it's not ideal. Edit: it did not fix it. Which fixed the issue is installing the master branch compiled directly. |
For me the error is java.lang.NoSuchFieldError: No field emptyString of type Ljava/lang/String |
@MichaelZ4714 thanks for the logs. I can confirm the stacktrace of the error is the same for everybody. See the comment by @elea11 above |
For me, it didn't, unfortunately. Even removed my nextcloud account completely and started from scratch. |
Okay, that's good, at least we have some consistency. |
vcard4android was updated on a27a4fc, which I believe was released on v4.3.11-alpha.2, but I will futher dig into it. |
Reinstalling the app doesn't solves the issue for me |
The issue is with NextCloud accounts.
|
The only thing modified on vcard4android since the last update was something about timezones (changes). Shouldn't be related, but I will do some tests now to see if this has something to do. |
Maybe it's an issue on newer Android versions? I'm on A14 and getting exactly the same error like @robertoprubio with the emptystring. |
For me it's only happening on Android 10 on my tablet. My Pixel 6a running A14 works perfectly, so I think it's not related to the version of Android |
Okay, I have managed to reproduce the error. Looks like it's a problem with the compiled APK, there's no code issue. Maybe some corruption happened in the compilation process. I think the fix is simple, recompile and release this version again @rfc2822. To reproduce (just for internal reference), I have taken the compiled AAB, extracted everything with bundletool: bundletool build-apks --bundle=file.aab --output=release.apks Then uninstalled the current version: adb uninstall at.bitfire.davdroid And installed the new one: bundletool install-apks --apks=release.apks After doing that, add the Nextcloud account, and synchronize, the exception occurs. Update: The same can be reproduced with the public APK. Steps:
Note The error is not thrown if the app is installed directly after compiling, instead of taking the built version, and the error shows that there's a class missing. That's why I think the APK is corrupt, or maybe proguard removed some files accidentally. What still bothers me is that I'm not having this issue on my phone, only on my tablet, and they are running the same DAVx5 compilation. |
Happens for -ose and -gplay, reproducible on all our devices. So extremly urgent
Seems to work without |
Happens here too with a mailbox.org account qith the version from gplay:
|
@ All: Can you please verify that 4.3.12.1 is working again? |
Tried in a Redmi Note 9S (A12) and in a Pixel 7 Pro (A14, GrapheneOS) and working perfectly in both devices. Thanks! |
Works here again now. A14 QPR Beta. Pixel 7. |
Now we will have to find out why the problems occur with AGP 8.2.0 but not with AGP 8.1.4 … |
Hotfix contained in 4.3.12.1 has been released in all stores now. It usually takes a while until the store owners approve it and until f-droid builds the hotfixed version. |
It works for me again with the hotfix on A14 crDroid 10 and A13 crDroid 9.11. Have many thanks! It was not that urgent for me personally because I used the quick fix go back to 4.3.11. |
Same problem since today, have did all I can. Uninstall the beta, clean my Pixel7 and install the latest stable from Playstore and set up my account fresh. Nothing changed. Pixel7 |
This version works for me too. Thank you for the quick fix as on Christmas, the is not usual! Thank you really much and enjoy Christmas now. 😊 |
Like everyone, I can confirm that the hotfix is working fine. Thanks for the quick fix @everyone involved. |
Yes the update worked all OK thanks for the quick community support |
Update works for me also. Thanks for the quick fix! |
As I was also affected by this issue I can confirm the update's working fine, until now, thank you for that ! Edit: I'm using a Baikal Server. |
Fix did not work when syncing with posteo.de . Log below |
You're still using 4.3.12. The problem is fixed in 4.3.12.1 |
I agree with many others here, the 4.3.12.1-ose version is fixed on A14 for both Nextcloud and mailbox.org. No more problems, cheers! |
I just updated to 4.3.12.1-ose via F-Droid and it worked fine even with posteo.de. |
…eAT/davx5#512) * Update to AGP 8.2.1 * Add keep rule for javax.xml.namespace.QName See #511 Closes bitfireAT/davx5#499
Discussed in #508
Originally posted by wksantiago December 24, 2023
Getting EXCEPTION
java.lang.NoClassDefFoundError: at.bitfire.vcard4android.property.CustomScribes
when syncing from Nextcloud to android and getting no contacts over
This happened after the upgrade
The text was updated successfully, but these errors were encountered: