After update sdk 39, app crashed
See original GitHub issue🐛 Bug Report
Summary of Issue
I update Expo SDK to 39, but the app crashed.
TypeError: undefined is not an object (evaluating ‘self.fetch.bind’)
<unknown> AppEntry.bundle?platform=ios&dev=true&minify=false&hot=false:333588:29 loadModuleImplementation AppEntry.bundle?platform=ios&dev=true&minify=false&hot=false:271:13 <unknown> AppEntry.bundle?platform=ios&dev=true&minify=false&hot=false:331662:13 loadModuleImplementation AppEntry.bundle?platform=ios&dev=true&minify=false&hot=false:271:13 <unknown> AppEntry.bundle?platform=ios&dev=true&minify=false&hot=false:331427:31 loadModuleImplementation AppEntry.bundle?platform=ios&dev=true&minify=false&hot=false:271:13 <unknown> AppEntry.bundle?platform=ios&dev=true&minify=false&hot=false:331343:51 loadModuleImplementation AppEntry.bundle?platform=ios&dev=true&minify=false&hot=false:271:13 <unknown> AppEntry.bundle?platform=ios&dev=true&minify=false&hot=false:286044:29 loadModuleImplementation AppEntry.bundle?platform=ios&dev=true&minify=false&hot=false:271:13 <unknown> AppEntry.bundle?platform=ios&dev=true&minify=false&hot=false:271138:47 loadModuleImplementation AppEntry.bundle?platform=ios&dev=true&minify=false&hot=false:271:13 <unknown> AppEntry.bundle?platform=ios&dev=true&minify=false&hot=false:128282:54 loadModuleImplementation AppEntry.bundle?platform=ios&dev=true&minify=false&hot=false:271:13 <unknown> AppEntry.bundle?platform=ios&dev=true&minify=false&hot=false:1335:47 loadModuleImplementation AppEntry.bundle?platform=ios&dev=true&minify=false&hot=false:271:13 guardedLoadModule AppEntry.bundle?platform=ios&dev=true&minify=false&hot=false:163:46 global code AppEntry.bundle?platform=ios&dev=true&minify=false&hot=false:408363:3Environment - output of expo diagnostics
& the platform(s) you’re targeting
expo: 39.0.0 react-native: https://github.com/expo/react-native/archive/sdk-39.0.0.tar.gz
if I just use sdk 39 and react-native sdk use 38.0.2 , app is ok. I guess it’s the compatibility issues React Native has
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Android app crashes after SDK-tools update version ...
I fixed it by going into Java Build Path > Order and Export tab. Click everything in the list "Android Private Libraries". Then...
Read more >In iOS 15, when the app is restarted, it immediately crashes.
After the iOS 15 update, the following process causes the app to die. Go to the home screen while running the app; Completely...
Read more >Crash affecting iOS 15/15.1 on iPad | Apple Developer Forums
After update 15.1 on my iPhone , nothing works. Several crashes when in use on different apps, rebooting my device and battery life...
Read more >Diagnosing issues using crash reports and device logs
Use crash reports and device logs to debug app issues. ... Update your code to fix the issue. ... These logs can be...
Read more >Crash in ios15 EXC_CRASH (SIGKILL) - Apple Developer
The crash is coming from within the SDK. It seems that the crash start to happen on iOS 15. (We were unable to...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hey!
When it comes to
TypeError: undefined is not an object (evaluating 'self.fetch.bind')
— do you have such code in your application? It doesn’t look like one that comes from us. 🤔When it comes to
39.0.0 is not a valid SDK version
— please ensure your Expo client is updated (latest version is2.17.x
). If you open Expo client and look at the <kbd>Projects</kbd> tab in Expo client, at the bottom there is: <kbd>Client version</kbd> and <kbd>Supported SDKs</kbd>. Latest Expo client on my device shows:Hi guys! Without a repro, we can’t really investigate this issue. It’s most likely that some of your dependencies are referring to a React Native internal that was changed in between
0.62.2
and0.63.3
. If someone can provide a repro, that would be helpful!For now I can only suggest taking a look at either one of these two issues, they seem to be similar
Hope this helps!