Hi All,
Thought I would post an update here. DTS are being rather slow - we've been told its still under 'investigation'. Since this is impacting our business quite seriously we have started playing around with some other ways to communicate with beacons.
We use a range of beacons, primarily from China and what is interesting is that the library they provide (that uses CoreBlutooth, CBManager etc) works without fail as its not using BLE but normal bluetooth (kind of goes against the fundamental's of a beacon I suppose). Although all the manufacturer's we use tell us that we should use their libraries, but it seems that some of them can reproduce the problems we have too! So at the moment whilst Apple seems to brush this aside, it seems the only possible way to work with Beacon's is tell our users to use an old phone or drink more battery using Core Bluetooth.
Is anyone here using Estimote beacons? I saw some problems over on their forums when iOS 10 was released, but things have quietened down now. If they have managed to fix it, it would be interesting to find out how.
Just to give a summary on what we think is causing the problem (if anyone wants to try and reproduce that would be great!) - on devices that don't pickup beacons as ive explained previously, if you do a hard reset on the phone we find that for a short period (varies) after it restarts that Beacon's will work fine. This has pushed us to the conclusion that there is something going wrong in the CLBeacon library - we have relayed this to apple, but heard nothing back.
Jayden