Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Web: Upgrading from 44.0.0 to 44.0.1 results in error: export 'getManifest2' was not found in './PlatformUtils'
See original GitHub issueSummary
Upgrading from 44.0.0 to 44.0.1 results in this error when building for web (in development):
./node_modules/expo-asset/build/AssetSources.js:78:20
"export 'getManifest2' was not found in './PlatformUtils'
76 |
77 | // For assets during development using manifest2, we use the development server's URL origin
> 78 | const manifest2 = getManifest2();
| ^
79 |
80 | if (manifest2?.extra?.expoGo?.developer) {
81 | const baseUrl = new URL(`http://${manifest2.extra.expoGo.debuggerHost}`);
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?
Web
SDK Version (managed workflow only)
44
Environment
Expo CLI 5.0.3 environment info:
System:
OS: macOS 12.0.1
Shell: 5.8 - /bin/zsh
Binaries:
Node: 16.0.0 - ~/.nvm/versions/node/v16.0.0/bin/node
Yarn: 1.22.10 - ~/.nvm/versions/node/v16.0.0/bin/yarn
npm: 8.2.0 - ~/.nvm/versions/node/v16.0.0/bin/npm
Watchman: 4.9.0 - /opt/homebrew/bin/watchman
SDKs:
iOS SDK:
Platforms: DriverKit 21.2, iOS 15.2, macOS 12.1, tvOS 15.2, watchOS 8.3
IDEs:
Xcode: 13.2.1/13C100 - /usr/bin/xcodebuild
npmPackages:
@expo/webpack-config: ~0.16.15 => 0.16.15
babel-preset-expo: 9.0.2 => 9.0.2
expo: ^44.0.1 => 44.0.1
react: 17.0.1 => 17.0.1
react-dom: 17.0.1 => 17.0.1
react-native: 0.64.3 => 0.64.3
react-native-web: 0.17.5 => 0.17.5
npmGlobalPackages:
eas-cli: 0.41.1
expo-cli: 5.0.3
Expo Workflow: managed
Reproducible demo
n/a
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Upgrading to expo@44.0.0 breaks iOS build of amazon ...
I tried upgrading to expo@44.0.0, but the iOS build then fails with a lot of errors, e.g: error: duplicate interface definition for class ......
Read more >Incompatible react native SDK with expo SDK - Stack Overflow
You'll need to update your version of the Expo SDK using the "expo upgrade" command. This error is saying that your SDK version...
Read more >I recently updated to expo SDK 44 and now I'm getting below ...
EAS build using eas build -p android fails due to a gradle error and it seems to be related to @react-native-async-storage/async-storage and ...
Read more >expo | Yarn - Package Manager
Changelog. This is the log of notable changes to the Expo client that are developer-facing. Package-specific changes not released in any SDK will...
Read more >Expo app crashes when attempting to write a new record with ...
I get no error messages in console nor in the Realm logs. ... creating a new app in the Realm backend, and furious...
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
This is fixed in expo-asset@8.4.6 (or expo@44.0.5 if you only have expo-asset as a transitive dependency).
Thanks for the quick reply! I don’t have the issue with your new project, but deleting and re-installing everything did solve it!
Should have done that myself first…
Thanks!