-
-
Notifications
You must be signed in to change notification settings - Fork 263
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
Errors/exceptions should be propagated to avoid crashes #224
Comments
Hi @Jonge, Do you have any crashes in specific that we should look at? Usually is hard to recover from Core Data failures that's why the default for some cases it has been to just crash, but there's also the chance that the crashes are our fault and would be great to reproduce them to provide a solution. |
I have some crash logs, but I'm pretty sure it is my fault, as I am not yet cancelling Sync operations. So there might be an issue when parsing a JSON with an object that meanwhile gets deleted, but not 100 % sure. Sorry those are a bit mangled, this is how i got it from HockeyApp.
Also, I am getting these crashes in
I might try to do a bit of debugging to make sure that I am doing something wrong. Thank you so far! |
Hi again. The only crash I really care about now is the last one in While I agree that it should not really happen if everything is correctly set up, it can't be guaranteed that the output from JSON is valid. I think in this case, the error could be easily caught (if I'm pretty busy right now, but I can try to find some time for a pull request if needed. |
Thanks @Jonge, That's pretty useful. I'll add an issue on that repo to follow up later. 🙏 |
Most errors should be propagated now, if you have any other suggestions please let me know. |
There are lines like:
and:
(and in some other places) that can (and do) cause crashes. Instead, an error should be caught/produced and propagated all the way through to the
changes
methods inSync
class, so that the developer can handle them instead.By the way, the latest release (1.9.0) is super stable so far. These crashes are VERY rare (less than 0.5% of users). So thanks a lot, you have done a great job! 👍
The text was updated successfully, but these errors were encountered: