Incompatibility with Expo SDK 44 + EAS Updates
See original GitHub issueDescribe the bug
TypeError: null is not an object (evaluating 'Constants.manifest.logUrl')
Steps to reproduce
Use EAS updates instead of legacy updates and Constants.manifest will be null, and Constants.manifest2 will instead be defined
Environment
-
Bugsnag version: “@bugsnag/expo”: “7.16.0”,
"expo": "44.0.3", "expo-application": "4.0.1", "expo-constants": "13.0.1", "expo-device": "4.1.0", "expo-updates": "0.11.5",
Issue Analytics
- State:
- Created 2 years ago
- Comments:13 (7 by maintainers)
Top Results From Across the Web
Expo SDK 44. Today we're announcing the release of…
They were initially supported only in bare workflow or standalone apps built with EAS Build, but with the release of SDK 44 are...
Read more >Upgrade Expo SDK
Expo maintains ~6 months of backward compatibility. Once an SDK version has been deprecated, you will no longer be able to use the...
Read more >Limitations - Expo Documentation
EAS Build is compatible with bare workflow projects if you check in the native directories, but no longer runs prebuild, as that could...
Read more >Updates - Expo Documentation
The expo-updates library allows you to programmatically control and respond to new updates made available to your app. Platform Compatibility. Android Device ...
Read more >Migrating from "expo build" - Expo Documentation
You must upgrade your project to migrate to EAS Build. ... careful when publishing updates in order to avoid publishing an incompatible JavaScript...
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 FreeTop 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
Top GitHub Comments
@kennethlynne - thanks for the quick reply and sharing your dependencies. Lemme give this one more try.
Some of the relevant usages that needs to be patched:
We patched all usages using patch-package like so as a temporary workaround: