You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running on both simulator and device (with update to RCTDeviceUUID.m), DeviceUUID just hangs and does not log the uuid to the console. Any ideas on how to begin debugging this?
Update
I needed to perform the following steps (adapted from react-native-keyboardevents):
In XCode, in the project navigator, right click Libraries ➜ Add Files to [your project's name] Go to node_modules ➜ react-native-device-uuid and add the .xcodeproj file
In XCode, in the project navigator, select your project. Add the lib*.a from the react-native-device-uuid project to your project's Build Phases ➜ Link Binary With Libraries. Select the .a file. Go to the Build Settings tab. Make sure 'All' is toggled on (instead of 'Basic'). Look for Header Search Paths and make sure it contains both $(SRCROOT)/../react-native/React and $(SRCROOT)/../../React - mark both as recursive.
The text was updated successfully, but these errors were encountered:
Running on both simulator and device (with update to RCTDeviceUUID.m), DeviceUUID just hangs and does not log the uuid to the console. Any ideas on how to begin debugging this?
Update
I needed to perform the following steps (adapted from react-native-keyboardevents):
In XCode, in the project navigator, right click Libraries ➜ Add Files to [your project's name] Go to node_modules ➜ react-native-device-uuid and add the .xcodeproj file
In XCode, in the project navigator, select your project. Add the lib*.a from the react-native-device-uuid project to your project's Build Phases ➜ Link Binary With Libraries. Select the .a file. Go to the Build Settings tab. Make sure 'All' is toggled on (instead of 'Basic'). Look for Header Search Paths and make sure it contains both$(SRCROOT)/../react-native/React and $ (SRCROOT)/../../React - mark both as recursive.
The text was updated successfully, but these errors were encountered: