Closed DhruvaSambrani closed 1 month ago
I think the error is because the FoxyDroid version is 1.8.0/72, but the IOS store version is older. Is it possible to update the IOS app? You may also want to use TestFlight incase the IOS store has some update rate limiting
@DhruvaSambrani i got a bug report from your iOS side. It is weird it feels like your database is in a wrong state. Can you try to clear data on iOS ? (might have to uninstall then install again) And then try again. It could work, though it wont explain what happened. Did you do anything specific before on the iOS app? So you understand the sync service see a document which needs to be downloaded but the id of the document is already existing in your database (though no local file). It could be a bug where you deleted the local document but the it was not correctly removed from database
Reinstalled and tried to set up the webdav.
This time, the first error is table Page has no column named brightness
, and then when I try it again, it gives me the unique constraint failure.
The failed import on the first sync leaves the db in a bad state, it seems.
@DhruvaSambrani i see what s happening now. And you were right it could be due to the incompatible versions. The android version does support that new brightness column while the ios version does not. Hopefully new iOS version coming real soon. Sorry about the trouble
Still an issue though that such an error table Page has no column named brightness
should not put your db in a bad state. Will look at it
Also, it might be useful to add some checks so that backward compatibility is somewhat maintained.
@DhruvaSambrani it is all implemented and new iOS version is waiting for review
Version
1.5.0
What platform are you using?
iOS
OS Version
Latest
What happened?
Title.
Exact error: Unique constraint failed document.Id
Relevant log output
No response
Code of Conduct