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.
Missing deviceId from the new version of Expo client
See original GitHub issuedeviceId became to undefined because deviceId: ExponentConstants ? ExponentConstants.installationId : undefined overrider that value. My App is used SDKv28, so the native code was not up-to-date with JS changed.
Issue Analytics
- State:
- Created 5 years ago
- Comments:12 (8 by maintainers)
Top Results From Across the Web
Device - Expo Documentation
DISPLAY (not Build.ID ) and currently is a string as described here. On iOS, this corresponds to kern.osversion and is the detailed OS...
Read more >how to get deviceId, deviceToken, deviceType in react-native ...
1.GET DEVICE ID: To get the device information in React Native will use the react-native-device-info library. getDeviceId() is method for ...
Read more >Approov Reference Guide | Approov Docs latest
This documentation provides a detailed reference manual for using Approov. If you are new to Approov then you will find it much easier...
Read more >How to use the expo-constants.default function in expo ... - Snyk
To help you get started, we've selected a few expo-constants.default ... in // the Expo client, or a standalone app (we also assume...
Read more >react-native-device-info with Expo : r/reactnative - Reddit
Thanks :) I need the unique device ID of the phone which unfortunately ... otherwise it will just work in any Custom Dev...
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
We’ve published new versions of the
expopackage with a fix for this that works with the latest client as well as older ones. After installing the new package you shouldn’t have to make any changes to your code. These are the versions on npm:SDK 28: 28.0.1 SDK 27: 27.1.1 SDK 26: 26.1.1 SDK 25: 25.1.2 SDK 24: 24.1.1 SDK 23: 23.1.1 SDK 22 was dropped with the latest Expo client and therefore is unaffected by the breaking change in this issue.
Please give these packages a try and if they address this issue we’ll close it out.
@ide: I confirmed this fix is worked. Tks. Look like the root-cause is missing publish JS version for the old SDK. 😃