[SDK 41] Standalone app crashes on ios when built with EAS while using AsyncStorage

Summary

When using AsyncStorage from the package recommended by the SDK 41 upgrade, it breaks the standalone ios app when the app is built using “eas build”. It works fine on standalone android.

The way to reproduce this is call AsyncStorage.getItem(‘key’) in app.js and build it with eas build -p ios and submit that version to the store. It will crash the app right away.

To fix this issue, you’ll have to build the app using expo build.

It has something to do with what native code is used when building the ios standalone app.

Check this issue for more information: https://github.com/expo/expo/issues/13391

Is there a way we could use EAS build using the native code expo build uses as well?

This is such a major issue and nearly impossible to debug without knowing what caused the error initially as it’ll simply crash.

Managed or bare workflow? If you have ios/ or android/ directories in your project, the answer is bare!

managed

What platform(s) does this occur on?

iOS

SDK Version (managed workflow only)

41

Environment

Expo CLI 4.7.1 environment info: System: OS: Windows 10 10.0.19042 Binaries: Node: 12.18.3 - C:\Program Files\nodejs\node.EXE npm: 6.14.6 - C:\Program Files\nodejs\npm.CMD npmPackages: expo: ^41.0.0 => 41.0.1 react: 16.13.1 => 16.13.1 react-dom: 16.13.1 => 16.13.1 react-native: https://github.com/expo/react-native/archive/refs/tags/sdk-42.0.0.tar.gz => 0.63.2 react-native-web: ~0.13.12 => 0.13.18 react-navigation: ^4.4.4 => 4.4.4 Expo Workflow: managed

Reproducible demo or steps to reproduce from a blank project

The way to reproduce this is call AsyncStorage.getItem(‘key’) in app.js and build it with eas build -p ios and submit that version to the store. It will crash the app right away.

To fix this issue, you’ll have to build the app using expo build.

[cauldyclark15]

No, I still run into the issue. I just use expo build instead of eas build because that’s what breaks your app in production. I haven’t had any issues since I switched to expo build. I’d recommend that over eas build.

same here, i am using SDK 43 and it looks like react-native-async-storage/asyncStorage is broken in EAS build

[stderr] FAILURE: Build failed with an exception.
[stderr] * What went wrong:
[stderr] Execution failed for task ':react-native-async-storage_async-storage:generateReleaseRFile'.
[stderr] > Could not resolve all files for configuration ':react-native-async-storage_async-storage:releaseCompileClasspath'.
[stderr]    > Could not resolve com.facebook.yoga:proguard-annotations:1.14.1.
[stderr]      Required by:
[stderr]          project :react-native-async-storage_async-storage > com.facebook.react:react-native:0.64.2
[stderr]       > Could not resolve com.facebook.yoga:proguard-annotations:1.14.1.
[stderr]          > Could not get resource 'https://jcenter.bintray.com/com/facebook/yoga/proguard-annotations/1.14.1/proguard-annotations-1.14.1.pom'.
[stderr]             > Could not GET 'https://jcenter.bintray.com/com/facebook/yoga/proguard-annotations/1.14.1/proguard-annotations-1.14.1.pom'.
[stderr]                > The server may not support the client's requested TLS protocol versions: (TLSv1.2, TLSv1.3). You may need to configure the client to allow other protocols to be used. See: https://docs.gradle.org/6.9/userguide/build_environment.html#gradle_system_properties
[stderr]                   > PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
[stderr]       > Could not resolve com.facebook.yoga:proguard-annotations:1.14.1.
[stderr]          > Could not get resource 'https://jcenter.bintray.com/com/facebook/yoga/proguard-annotations/1.14.1/proguard-annotations-1.14.1.pom'.
[stderr]             > Could not GET 'https://jcenter.bintray.com/com/facebook/yoga/proguard-annotations/1.14.1/proguard-annotations-1.14.1.pom'.

[cmaycumber]

This makes a lot of sense. Let me try a few things first then.

Thanks for the feedback.