v1.0.8 progress (and what can I do to help?)

[eurobob]

Version

1.0.8

Platform

iOS

OS version

iOS 10

I've been experiencing difficulty with ranging beacons. Currently this is what happens when i build my app (only testing on iOS atm):

1. App loads
2. User grants location permission
3. Call Beacon listeners
4. No beacons detected
5. Have to close and reopen app
6. Still no beacons detected
7. Exit beacon radius and finally get an exit event
8. Beacon monitoring and ranging works fine after this

Bascially, i'm about to launch a project that depends on beacons for the revenue. So two questions:

1. Are the changes coming in v1.0.8 going to enable ranging of beacons when the app is loaded while in range of one?

2. What can I do to help get this version out asap? I don't know much about the native side of things, but I can put my full attention on this immediately. Is there a task list anywhere?

[MacKentoch]

Limitations in ranging come from iOS native:

If you are in range when launching the application it won't trigger enter event. This is really frustrating I agree with you...

Now I don't see any solution apart from a trick to counter that. I'm opened to suggestion to fix that.

Until I have a beautiful solution, I would go for a trick with some mix of monitoring and ranging.

[eurobob]

I'm not sure I follow with the idea of tricking the system? I've been looking into the "requestStateForRegion" documentation, but it seems that we can't use our own defined regions with that.

How would we use monitoring and ranging to detect that we're already in a region?

The only thing I can think of right now is maybe storing the return value of the "didDetermineState" listener in the state, and running the desired code if beacons are ranged but the state is either undefined or "outside"