enteredRegion event not fired.

[morefun0302]

I am using the below code as stated in your example:

TiBeacons.startMonitoringForRegion({
uuid : "E2C56DB5-DFFB-48D2-B060-D0F5A71096E0",
major : 1,
minor : 4,
identifier : "Shop A"
});

but the enteredRegion event is not fired, however, determinedRegionState can be fired.

Please help, thanks

[jbeuckm]

Are you leaving the region to start your app? If your app starts within the region, you will not receive enteredRegion.

[davemuir]

I have found this to be an issue as well. It seems to be a little random. Sometimes the beacon is OUTSIDE and other times it's INSIDE upon monitoring beacons. If it starts inside, I don't see event happening unless the beacon is powered off/on or ranged out. Are you planning on fixing this issue in a later release, work arounds?

Thanks

[avines002]

I'm seeing this happen as well. I'm thinking monitoring for determinedRegionState==inside might be a good work around?

[h3r2on]

since you can get the regionState it's trivial to add code similar to this

var beaconsInRange = [];  //array to hold deacons currently being monitored
var beacons = [] //array of beacons info

function regionState(e) {
  Ti.API.info(e);
  if(e.regionState == "inside") {
    if(!_.contains(beaconsInRange, e.identifier)) {
      var beacon = _.findWhere(beacons, {identifier: e.identifier});
      beaconsInRange.push(e.identifier);
      TiBeacons.startRangingForBeacons(beacon);
    }
  }
}

[achimhoth]

In my setup not even determinedRegionState is firing reliably. Seems to only fire once. I do get traces from the module though telling whether I enter or exit a region. Maybe the events are not bubbling up to the Titanium level?