expo: SDK 39++ bug fix release

Hi everyone! I am both pleased and relieved to be able to tell you that we have now rolled out the following fixes for SDK 39:

• expo-updates:
  • Standalone apps built for SDK 39 now properly read updates from the release channel they are built against (issue).
  • Standalone apps for iOS will read assets correctly from exported projects (built with expo export), and iOS and Android standalone apps support assetUrlOverride with absolute urls. (issue, issue)
  • Updates.reloadAsync() is supported in development once again. (pr)
• expo-splash-screen:
  • android.splash.hdpi and other *dpi properties are used as expected in Expo client on Android. (issue)
  • iOS and Android splash screen image no longer flickers after completing bundle download within Expo client (issue)
  • Configuration of splash screen in Android standalone apps now works the same as before. (issue)
• react-native:
  • Fixed regression in Blob support. (issue)
  • TouchableOpacity press-in delay removed. (issue)
  • Fix Xiaomi TextInput native crash. (issue)
• Remote JS debugging on Android no longer crashes the Expo client app (issue).
• DocumentPicker on iOS 14 no crashes in Expo client on iOS 14, also fixed issue with being unable to open it more than once on iOS 14. (issue).
• TaskManager no longer crashes on Android in release mode. (issue 1, 2)
• Linking.getInitialUrl() on Android returns the correct deep link URL (issue).
• Published apps that throw exceptions before loading no longer hang on splash screen in Expo client, instead they will show an error screen. In standalone apps, the app will crash rather than hang (as expected). (issue)
• Updated Facebook Audience Network SDK (pr).
• Fix regression in notification icons with expo-notifications. (issue)
• QR code scanner to scan to open apps in Expo client for Android no longer skewed on some devices. (issue)

Next steps

• Download the latest iOS and Android clients from the stores.
• Install the latest iOS and Android clients with expo client:install:ios and expo client:install:android

If you previously upgraded your project to SDK 39

• For managed apps, change your react-native version to https://github.com/expo/react-native/archive/sdk-39.0.3.tar.gz. For bare apps, we recommend using react-native 0.63.3.
• Run yarn upgrade to update to the latest version of packages in your project for their current semantic version range. npm does not have an equivalent command, so you can delete your package-lock.json and node_modules and run npm install again.
• Build your standalone apps again.

Thank you again for your patience and detailed issue reports! We’ll follow up again soon with plans for avoiding shipping significant regressions again in the future.

The estimate is sometime within the next 1-5 days.

guys it works you are awesome!

I also try it with expo client:install:android

expo client:install:android You are currently using SDK 39.0.0. Would you like to install client 2.17.4 released for this SDK?

the expo --version 3.27.13

What did I miss?

@kailo777

2.17.4 is the version of the Expo Client App on the Phone. 3.27.13 is the Expo CLI version you are using in the terminal.

With running expo client:install:android you are installing the latest version of the Expo Client App on a connected Android device or emulator, which needs to be 2.17.4 for the latest Expo SDK 39.

@nightmarelie Did you followed this step to upgrade the mobile client? That helped me.

Install the latest iOS and Android clients with expo client:install:ios and expo client:install:android

Might be a silly question, but how do I do this?:

@ac15aeq - steps:

1. edit package.json and in the “scripts” section set the value of react-native to: "react-native": "https://github.com/expo/react-native/archive/sdk-39.0.3.tar.gz",
2. run npm install (or, alternatively, yarn install)
3. to confirm you now have the correct version installed, you can use npm ls react-native. I believe that it will show: react-native@0.63.2

Should I upgrade the expo package to 39.0.3 too? The instructions above doesn’t mention it and expo upgrade doesn’t upgrade it (I have 39.0.0 installed).

@brentvatne https://github.com/expo/react-native/archive/sdk-39.0.3.tar.gz is installing react-native 0.62.2 for managed workflows, I have tried expo upgrade, yarn upgrade, yarn i after removing node_modules and yarn.lock file even cleared yarn cache with yarn cache clean but it always fetches 0.62.2, shouldn’t it get 0.63.3 for managed workflows?

Thank you so much @brentvatne @ide and all the ones involve on this new release. 👍

@nightmarelie @xnaveira

I also try it with expo client:install:android

expo client:install:android You are currently using SDK 39.0.0. Would you like to install client 2.17.4 released for this SDK?

the expo --version 3.27.13

What did I miss?

I have the following versions: 2.17.4 - client version 3.27.13 - cli and everything works

try to start with -c flag. yarn start -c (Clear the Metro bundler cache)

@calvinkei - yes, please refer to the instructions above:

If you previously upgraded your project to SDK 39

• For managed apps, change your react-native version to https://github.com/expo/react-native/archive/sdk-39.0.3.tar.gz. For bare apps, we recommend using react-native 0.63.3.
• Run yarn upgrade to update to the latest version of packages in your project for their current semantic version range. npm does not have an equivalent command, so you can delete your package-lock.json and node_modules and run npm install again.
• Build your standalone apps again.

in particular, the final point

@ac15aeq - update the version of react-native in package.json to "https://github.com/expo/react-native/archive/sdk-39.0.3.tar.gz" and then run npm install or yarn. the sdk version is still 39.0.0, this is just bumping the react-native version.

Hi,

Might be a silly question, but how do I do this?: For managed apps, change your react-native version to https://github.com/expo/react-native/archive/sdk-39.0.3.tar.gz

I tried doing expo cli upgrade and then expo upgrade but that didn’t seem to get the new version, still says 39.0.0.

Do I need to uninstall current react-native and somehow install this folder?? I’ve only npm installed packages before, I am fairly new to this type of development.

Thanks

I think we should also fix https://github.com/expo/expo/issues/10469.

This problem consists of two minor ones:

• In standalone bundle, the image on the right can not be removed (or changed to something other than notification.icon) when remote notification is displayed. - It was fixed by https://github.com/expo/expo/commit/710776d3e60b3b8554288cd44e81cbc7762701b2
• In standalone bundle, the icon and text coloring is different for local and remote notifications. - maybe fixed by https://github.com/expo/expo/pull/10492