-
Notifications
You must be signed in to change notification settings - Fork 5
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
adding the "app launched" transition broke the android sync #9 #7
Comments
Added by ecc8b17 |
Obvious fix is to move the try/catch block into I added some code to store them into an error database instead, but before we use it, we need to unify some usercache behavior between iOS and android. In particular, we can store but it turns out that on iOS, if we pass in something that is a string and not a wrapper, the serialization code returns an empty JSON object '{}', so we will never store invalid entries into the database.
We need to think carefully about the error handling here - should we drop entries at storage time, or store them into an error database or ??? If we do store them into an error database, we should have a screen that displays them and allows users to clear them. We don't want to have the data leak of storing entries that there is no way to manipulate later. So for now, we put on storing data into the error cache. We still have the error table, and the functions that will store entries into it, but we just don't populate them, either on iOS or on android. |
Before this, on android, if there was a single ill-formatted message, we used to abort the entire sync. Now, we only skip that message. Currently, all skipped messages are deleted at the end of the sync. We were originally going to store skipped messages in a separate error database. But it turns out that on iOS, we check validity at insert time, and invalid messages are not stored in the usercache at all, which means that they are effectively discarded. We need to decide our error handling policy. Until we do this, we discard on both iOS (at insert time) and on android (at upload time). We have created an error database to store the data, but are not using it pending decision. The issue is being tracked in: e-mission#7
The text was updated successfully, but these errors were encountered: