-
Notifications
You must be signed in to change notification settings - Fork 24.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dropping Support for iOS 8 #19346
Comments
This comment has been minimized.
This comment has been minimized.
Will you also be able to upgrade the JavaScriptCore shipped with Android to a version aligned with the iOS 9 version of JavaScriptCore? That would allow some of the older polyfills (e.g |
f50df4f updated target deployment for RNTester/React xcode project to 9.0, and also removed RCTFont specific overrides for iOS <8.2. |
@fkgozali You should also update |
@ikesyo good catch - I thought I did, will fix soon |
092103e updates a few .podspec files to iOS 9.0 |
Support for iOS 8 has been dropped. Thanks @fkgozali for working on this. There's a few deprecated methods that are yet to be removed but it's been worked on. This issue can now be closed. |
iOS 8 was released almost 4 years back, an eternity for iOS releases. Thanks in part to the fact that any device that can run iOS 8, can also run iOS 9, it's used by less than 0.5% of devices. Anyone who wants to, can upgrade to iOS 9.
With these facts in mind, we will be dropping official support for iOS 8 starting next week. The core React Native team will no longer run tests on iOS 8 devices and will not maintain any workarounds that may be in place to support iOS 8. Dropping support for iOS 8 will also help React Native achieve consistency with the rest of the codebase at Facebook.
Workarounds
Developers who support iOS 8 in their apps may continue doing so as this is a Xcode-level setting (
IPHONEOS_DEPLOYMENT_TARGET
). Please be aware that any issues you may encounter when your app is running on iOS 8 devices will not be considered a priority.The text was updated successfully, but these errors were encountered: