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.
Expo notifications inconsistency between EAS and Classic build.
See original GitHub issueSummary
I have Ios and Android app deployed with Classic build on stores. When switched on EAS build services expo notifications are complaining about missing experience id.
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?
Android, iOS
SDK Version (managed workflow only)
41
Environment
Expo CLI 4.4.1 environment info: System: OS: Windows 10 10.0.19041 Binaries: Node: 12.18.3 - C:\Program Files\nodejs\node.EXE Yarn: 1.22.4 - C:\Users\Jurica\AppData\Roaming\npm\yarn.CMD npm: 6.14.6 - C:\Program Files\nodejs\npm.CMD IDEs: Android Studio: Version 4.1.0.0 AI-201.8743.12.41.6953283 npmPackages: expo: ^41.0.0 => 41.0.0 react: 16.13.1 => 16.13.1 react-dom: 16.13.1 => 16.13.1 react-native: https://github.com/expo/react-native/archive/sdk-41.0.0.tar.gz => 0.63.2 react-native-web: ~0.13.12 => 0.13.18 Expo Workflow: managed
Reproducible demo or steps to reproduce from a blank project
const token = await Notifications.getExpoPushTokenAsync();
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Deleting yarn.lock, node modules then upgrading to 0.11.6 solves issues on both platforms! Tnx anyway!
BTW EAS build is awesome!! From 71 mb to 9 mb on IOS and 17 to 10 mb on android!
Keep up with good work!
~0.11.5 resolves to 0.11.6 - https://stackabuse.com/caret-vs-tilde-in-package-json/