Relative Content

Tag Archive for iosreact-native

Disable NSLocationWhenInUseUsageDescription iOS permission in react-native

I’m getting warnings from App Store Connect about a missing purpose string for NSLocationWhenInUseUsageDescription but my react-native app doesn’t use any location services. If I remove the string from my Info.plist file I get a warning about needing it to be set because my app references the location APIs.

React native application not launching

My react native application suddenly stopped working and when I try to run the app and the app builds successfull and even launches but then immediately crashes. What could be the issue? This is the only error log I see and noting appears in the console.

Generating an iOS application from React Native crashes during the load phase on the simulator

2024-07-16 16:45:22.475 [error][tid:com.facebook.react.JavaScript] Invariant Violation: Native module cannot be null.
2024-07-16 16:45:22.478 [error][tid:com.facebook.react.JavaScript] Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication)
2024-07-16 16:45:22.478 [fatal][tid:com.facebook.react.ExceptionsManagerQueue] Unhandled JS Exception: Invariant Violation: Native module cannot be null.
*** Terminating app due to uncaught exception ‘RCTFatalException: Unhandled JS Exception: Invariant Violation: Native module cannot be null.’, reason: ‘Unhandled JS Exception: Invariant Violation: Native module cannot be null., stack:
y@132:461
@1417:218
v@2:1474
@1416:74
v@2:1474
@1415:767
v@2:1474
@1408:426
v@2:1474
@1302:180
v@2:1474
@1186:138
v@2:1474
@396:387
v@2:1474
@395:196
v@2:1474
@6:58
v@2:1474
d@2:876
global code@2151:4

*** First throw call stack:
(
0 CoreFoundation 0x00007ff80049b761 _exceptionPreprocess + 242
1 libobjc.A.dylib 0x00007ff800063904 objc_exception_throw + 48
2 NativebaseKitchenSink 0x000000010484e0c2 RCTGetFatalHandler + 0
3 NativebaseKitchenSink 0x00000001048c4938 -[RCTExceptionsManager reportFatalException:stack:exceptionId:] + 508
4 CoreFoundation 0x00007ff8004a238c invoking
+ 140
5 CoreFoundation 0x00007ff80049f6b3 -[NSInvocation invoke] + 302
6 CoreFoundation 0x00007ff80049f923 -[NSInvocation invokeWithTarget:] + 70
7 NativebaseKitchenSink 0x0000000104881a63 -[RCTModuleMethod invokeWithBridge:module:arguments:] + 583
8 NativebaseKitchenSink 0x0000000104883c72 _ZN8facebook5reactL11invokeInnerEP9RCTBridgeP13RCTModuleDatajRKN5folly7dynamicE + 266
9 NativebaseKitchenSink 0x00000001048839bc ___ZN8facebook5react15RCTNativeModule6invokeEjON5folly7dynamicEi_block_invoke + 82
10 libdispatch.dylib 0x000000010556a747 _dispatch_call_block_and_release + 12
11 libdispatch.dylib 0x000000010556b9f7 _dispatch_client_callout + 8
12 libdispatch.dylib 0x00000001055738c9 _dispatch_lane_serial_drain + 1127
13 libdispatch.dylib 0x0000000105574665 _dispatch_lane_invoke + 441
14 libdispatch.dylib 0x000000010558176e _dispatch_root_queue_drain_deferred_wlh + 318
15 libdispatch.dylib 0x0000000105580b69 _dispatch_workloop_worker_thread + 590
16 libsystem_pthread.dylib 0x0000000104edac55 _pthread_wqthread + 327
17 libsystem_pthread.dylib 0x0000000104ed9bbf start_wqthread + 15
)
libc++abi: terminating due to uncaught exception of type NSException

Application getting crash when upload video size more than 500 mb in iOS

using react-native-background-upload package for chunk upload It is iOS specific issue, in android working fine. video less than 500mb works well for iOS but more than 500mb crashes the app. no specific errors Also it is device specific, tried on various iPhones like iPhone 11 pro, iPhone 13, iPhone 14 ios react-native New contributor Nancy […]

Same identifierForVendor id generated in different devices

We are facing an issue on production where in – same identifierForVendor id (IDFV) is getting generated on two different iOS devices. Owner of both the devices are related to each other. As per our understanding, we came to know that this could be possible in case if both the devices have the same apple id configured and key chain is in sync. But this is ruled out as both devices have different apple id (customer confirmed).