Error on startup: Native module cannot be null about playlist-example HOT 5 CLOSED

Try updating the 'app.json' file line 7 - "sdkVersion": "30.0.0".
They updated it in 'package.json', but probably forgot that one.
Had the same issue until I found a thread with someone with a similar issue who just updated to v 30.0.0 and was advised to check that file.

from playlist-example.

same here. can't figure out what to do 🤔

from playlist-example.

Thank you @a3l5o7n9, helped me a lot. I still had to tweak some minor things to get it running. You can find my code (if anybody is interested) here: https://github.com/natterstefan/playlist-example/tree/feature/expo-sdk-31. I have not created a PR yet, because one feature is not working anymore and I am still investigating why.

from playlist-example.

For anyone else having this issue: we solved it because after upgrading to v31, even though the npm install created the split up of the expo modules, it didn't add them to the Podfile and header paths for the Xcode project.

Adding:
pod 'EXLocation', :path => "../node_modules/expo-location/ios"
To your pod file and "${PODS_ROOT}/Headers/Public/EXLocation" to the Header Search Paths on your Xcode project target should sort out this error.

Keep in mind it may not be the last of the errors that you'll see. If you create a fresh expo project and do an eject, have a look at the generated Podfile and Header Search Paths that are created. They'll probably have a lot more entries than your current config.

from playlist-example.

Closing this as we've updated to SDK 34 and I wasn't able to repro this. If you run into any issues using the Audio API, please open any further issues at the main Expo repo

from playlist-example.