What a friggin’ day!!! What a friggin’ day!

I wanted to continue implementing MS 0.8.3 because I really want to get to 0.9.0 asap.

But then, there was a major issue at my other client with PDF-Annotations not really working across Web and Mobile app (Annotations that the users themselves do privately). Somehow, a weird combination of use would delete all of them.

It took make quite some time and some really awful experimenting to figure out:
- WebApp had a #PSPDFKit-Version from May 2022
- iOS had a Version from Nov 2022
- Android had a Version from Aug 2022

iOS-Version was way ahead of all of them, bot because of its date but because the people at PSPDFKit work more on the iOS-Version (and better) than on Android.

So, iOS supports “Annotations V2” and create only V2-Annotations.

Web did NOT support V2, this they were ignored when they were created in iOS.

And Android? Well, Android can only handle V1-Annotations (even the latest version of PSPDFKit, which seems to be a bug).

Result:
- Upgrade Web to the newest PSPDFKit
- Upgrade iOS to the newest
- Upgrade Android to the newest BUT switch off Annotations because since it doesn’t support 2.0 (which now Web and iOS) do, it just deletes them and we can’t have that.

I was completely furious because it was a weird combination on when exactly Annotations were “deleted”. And my testers didn’t really help with comments like “I just tested and it still doesn’t work” (What exactly did you test, which version of App + Web on which server “testing, dev, integration, staging”???) ARGHHHHH!!!

Now it is done. I am waiting for Apple to review the app so I can release it and on Tuesday we will release the Web-Version.

Android is already live and doesn’t delete Annotations anymore.

#Android #iOS #WorkTopics #Flutter

The only problem with #TailwindCSS is that when you need to drop back to vanilla CSS (in this case for #PSPDFKit) then you feel like an incompetent klutz again.