Closed gino-m closed 2 weeks ago
@scolsen This is related to the sync status that you had worked on, do you have bandwidth to look into this by Wed?
We should always catch all errors and return Result instead of bare values.
Yes, definitely. I'd go so far as to say exceptions are now a code smell since we have error value types. In general, error value types will be much better for us given that we use functional streams extensively, which do not cohere well with exceptions.
In the meantime, I took a simpler route and just added a catch
call. I'm not sure what the underlying cause is here. I've added some additional debugging to the error message in efforts to help repro—looking at the code, we just copy the previous mutation and only update its state, so it's not obvious to me where/why the Job ID would change if that's actually the cause of the exception here.
https://github.com/google/ground-android/pull/2333 is a workaround for this crash, I'd like to leave this open so that we can get to the root issue (but considered "done" for the 3/13 freeze)
Based on my prev comment, going to pull this into iteration 7
@scolsen I think this has already been fixed, can you kindly confirm?
Closing as inactive.
After disabling Airplane mode:
From Crashlytics:
Note that conversions shouldn't crash app. We should always catch all errors and return
Result
instead of bare values.The data is uploaded, but the status screen then gets stuck with the following:
@scolsen FYI