iOS — Exception 'Invalid parameter not satisfying: region != nil' was thrown while invoking startRangingBeaconsInRegion on target RNiBeacon with params ...

[didacus]

Version

11.2.6

Platform

iOS

OS version

iOS 11

Expected behaviour

Should start monitoring region for Eddystone beacons.

Actual behaviour

Throws back the following error:

Exception 'Invalid parameter not satisfying: region != nil' was thrown while invoking startRangingBeaconsInRegion on target RNiBeacon with params 
(
    {
        identifier = "EDDY_STONE_REGION_ID";
        uid = 953E1199A959B67221BD;
    }
)
callstack: (
	0   CoreFoundation                      0x00000001867cb17c <redacted> + 148
	1   libobjc.A.dylib                     0x0000000185a14528 objc_exception_throw + 56
	2   CoreFoundation                      0x00000001867cb038 <redacted> + 0
	3   Foundation                          0x00000001871657f4 <redacted> + 112
	4   CoreLocation                        0x000000018cdc43e0 CLClientRetrieveData + 55944
	5   eddystonePrototype                  0x00000001009c1844 -[RNiBeacon startRangingBeaconsInRegion:] + 148
	6   CoreFoundation                      0x00000001867d2ad0 <redacted> + 144
	7   CoreFoundation                      0x00000001866b136c <redacted> + 292
	8   CoreFoundation                      0x00000001866b5e1c <redacted> + 60
	9   eddystonePrototype                  0x00000001007d3774 -[RCTModuleMethod invokeWithBridge:module:arguments:] + 2064
	10  eddystonePrototype                  0x000000010087c44c _ZN8facebook5reactL11invokeInnerEP9RCTBridgeP13RCTModuleDatajRKN5folly7dynamicE + 664
	11  eddystonePrototype                  0x000000010087bfdc _ZZN8facebook5react15RCTNativeModule6invokeEjON5folly7dynamicEiENK3$_0clEv + 132
	12  eddystonePrototype                  0x000000010087bf4c ___ZN8facebook5react15RCTNativeModule6invokeEjON5folly7dynamicEi_block_invoke + 28
	13  libdispatch.dylib                   0x00000001011212cc _dispatch_call_block_and_release + 24
	14  libdispatch.dylib                   0x000000010112128c _dispatch_client_callout + 16
	15  libdispatch.dylib                   0x000000010112ff80 _dispatch_queue_serial_drain + 696
	16  libdispatch.dylib                   0x00000001011247ec _dispatch_queue_invoke + 332
	17  libdispatch.dylib                   0x0000000101130f6c _dispatch_root_queue_drain_deferred_wlh + 428
	18  libdispatch.dylib                   0x0000000101138020 _dispatch_workloop_worker_thread + 652
	19  libsystem_pthread.dylib             0x00000001863f2f1c _pthread_wqthread + 932
	20  libsystem_pthread.dylib             0x00000001863f2b6c start_wqthread + 4

Notes

@dukhanov can you spot an error in the way the region is defined? Maybe the UID format? Has anyone encountered this issue? (Estimotes beacons works fine.)

[dukhanov]

Are you sure that you use the latest version? Show me your JS code?

I see uid but should be uuid it might be the case

[axlalvaro]

Hi! I have the same issue. I see uuid in the Xcode log (not uid)

[didacus]

@dukhanov Back to this issue, I changed UID to UUID but I am getting the same error. Would be possible to post your app working with Eddystones beacons? @axlalvaro did you manage to solve this issue?

[didacus]

Any developments on this issue?

[dukhanov]

Do not have time so far, will check this week

[axlalvaro]

@dukhanov I didn't solve it. I noticed that if I set the uuid to all ceros like this: 00000000-0000-0000-0000-000000000000 It did scan my Eddystone custom beacon. But what is the point if cannot differentiate mine from the rest, right?

[didacus]

@axlalvaro how did you manage to scan an Eddystone plotting a UUID from an iBeacon!? Puzzled.

[axlalvaro]

@didacus Apparently the 'all ceros uuid' catches everything, like a wildcard. Also, I think eddystone is just a format (eddystone-uid) and this library claimed to support eddystone..

[RM-Eric]

I'm getting this as well; has anyone figured it out?

Im using git://github.com/MacKentoch/react-native-beacons-manager.git#53c1bda , for what its worth