Open achou11 opened 2 months ago
I got the same error but without starting to create an observation... And I didn't close the app, just put it in the background
Update on my progress. The issue is happening very indeterminately. I have not figured out how to recreate the error consistently.
When the error does happen, it is consistently the error that andrew has logged above.
Im going to try building an apk next to see if it has anything to do with expo, and expo rebundling
I have determined what is causing the bug (but don't fully understand the underlying architecture). But its related to our hot-reload not properly working.
So the bug happens in the dev
environments when android is rebundled. With hot-reload, it shouldn't rebundle, but our hot reloading isnt consistently working. When we open and close the app, sometime (but not all time), the app rebundles, and that causes the tracks to crash.
To confirm, i built an apk, and I have not been able to reproduce this bug in production.
Because it is not happening in production, I am going to de-priortize this bug. And I think that the fix for this bug is actually going to be a fix for hot-reload
Describe the bug
In development, I'm getting this error when running the reproduction steps listed below:
When re-opening the app, I get an app error that says the following (and the app doesn't actually load):
Seems like the only way to recover is to clear the app storage (not even just the cache)...
To Reproduce
Under the assumption that you have tracks feature enabled...
Seems like the issue doesn't occur if 2 is omitted.