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
#4755 removes a user-facing workaround we left in our template app. It has a nasty side-effect of causing any apps upgrading to see a crash if they don't remove the workaround.
This is a breaking change that could cause a lot of frustration, as the crash will appear somewhat cryptic. Following up with @vmoroz to understand if there are alternate fixes that could avoid the crash, or if we could convert the crash into a build-time error.
Pending that we have a couple options:
Cherry-pick into 0.62 and try to rip the band-aid off early. This will break people using our preview, which is not ideal.
Delay the change until 0.63, so that we can try to catch people with initial release notes.
Invest in infrastructure like react-native-upgrade to mitigate before making the change (likely not possible)
The text was updated successfully, but these errors were encountered:
ghost
added
the
Needs: Triage 🔍
New issue that needs to be reviewed by the issue management team (label applied by bot)
label
May 2, 2020
#4755 removes a user-facing workaround we left in our template app. It has a nasty side-effect of causing any apps upgrading to see a crash if they don't remove the workaround.
This is a breaking change that could cause a lot of frustration, as the crash will appear somewhat cryptic. Following up with @vmoroz to understand if there are alternate fixes that could avoid the crash, or if we could convert the crash into a build-time error.
Pending that we have a couple options:
react-native-upgrade
to mitigate before making the change (likely not possible)The text was updated successfully, but these errors were encountered: