You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently have code in our engine fork to detect problems during Dart initialization and "mark the patch bad" (e.g. roll it back).
However we don't currently catch other kinds of crashes, but could. e.g. #1826
My understanding of the way Expo does this in their OTA product is by setting a timer for ~5 seconds on launch, if the timer fires it marks the patch as good.
Obviously there would be caveats with potentially needing to catch users killing the app (to not mark the patch bad)?
We also could just more directly catch the crash (like crashlytics or sentry would) and mark the patch bad that way.
The text was updated successfully, but these errors were encountered:
We currently have code in our engine fork to detect problems during Dart initialization and "mark the patch bad" (e.g. roll it back).
However we don't currently catch other kinds of crashes, but could. e.g. #1826
My understanding of the way Expo does this in their OTA product is by setting a timer for ~5 seconds on launch, if the timer fires it marks the patch as good.
Obviously there would be caveats with potentially needing to catch users killing the app (to not mark the patch bad)?
We also could just more directly catch the crash (like crashlytics or sentry would) and mark the patch bad that way.
The text was updated successfully, but these errors were encountered: