ios - New Possible iBeacon Monitoring Issue since Xcode 6.3 -

so here's breakdown

all swift language configuration 1: xcode 6.3 version ios 8.1+

configuration 2: xcode 6.2 version ios 8.2 , lower, since xcode 6.3 need build ios 8.3 devices.

iphone 5 / ipod 5th gen in both tests.

during config # 1 in our app monitor main region, (uuid no major/minor). after enter event raised start monitoring sub regions have same uuid, assigned major/minors. after entering "main" region multiple smaller regions, when 1 of removed, function didexitregion of cllocationmanager called called main region , not sub region expected. when exit sub regions (thus exit main region) 2 callbacks, both of main region.

the intended behavior expect when exit sub region, not main region call sub region. , when exiting last of sub regions 2 callbacks, 1 sub region , second main region.
behavior written in apple docs , how worked in our config # 2 aka until xcode version 6.3 (basically how worked until upgrade of xcode.

my real question: else having issue, , know possible work around didexitregion call return correct clregion. i've used 1 of our companies dev support things, hoping apple can answer since seems part of how xcode handling os calls. if hear them post below.
sorry in advance newbness, 2nd or third question, still getting hang of it.
edit: never mind, i'm huge idiot, overwriting variable accidentally copy pasting code fixing different problem...

this thought…

from startmonitoringforregion:

you must call method once each region want monitor. if existing region same identifier being monitored app, old region replaced new one.

try registering smaller regions first. take @ monitoredregions @ runtime , see if contains expect.