Should onEnteredRegion be called if the BeaconManager is created while inside the region?


On the latest Android SDK (0.9.7), I find that if I create and connect to a BeaconManager while inside a region, onEnteredRegion is not called. (It’s only called after I go out of range, and come back into range).

Is that expected behaviour? If so, is there any way to check if I am currently in a region, separate from onEnteredRegion?

Actually, after some more testing, the cause here seems to be something in my own code.