Closed kueda closed 4 years ago
We can transmit this data in other ways (it's another method of transferring results from the INatService class - we've implemented before for other APIs). Will fix
FWIW, this seems like it's still happening, only on Google devices and only in Android 9: https://fabric.io/inaturalist/android/apps/org.inaturalist.android/issues/5c1430b6f8b88c2963db7913?time=last-thirty-days. Not sure if it's really impacting users.
Definitely not fixed as it's still happening in 335 and 337. The question is, can it be fixed or is this just due to giant JSON responses from the API?
FWIW, this is still happening in build 370, but it remains unclear whether this is fixable. Smaller API responses are something we're working on in the next version of the API.
I think an observation's JSON is too large the app will crash when loading comments and IDs. This was happening when you try to view https://www.inaturalist.org/observations/5407184.json in the app (it's not now b/c I removed a lot of the photos). You could definitely argue that this response is absurd with a ton of duplicate taxon and photos records, and you would be right, but regardless, the app should not choke on JSON just b/c it's too big unless it's absurdly big, like 5+ MB or something. Or maybe I'm mis-diagnosing this, but I'm definitely getting a crash on my 5X, build 199. I do not get that crash with build 203 after having removed the photos. Yes I should have tested the most recent version before removing the photos. I am a bad bug filer.
The user who reported this is the one who owns this observation, and they also say that when they try to view it in the app, the app hangs and posts an older version of their ID (you can see the sequence of replaced IDs on their observation). I'm not entirely sure that's related, but maybe.
Anyway, if there is some kind of cap on the size of JSON we can load, can we remove it?
Log data: