Hi Argun, Thank you for the detailed response. Gives us peace of mind that we are on the right track. I completely understand that it is very difficult to guess why things are going wrong without knowing how we implemented it. Is there a way we could use to give you a better idea on our implementation which could help point to what the cause of our problems could be? One follow up item which I completely forgot to mention. We have setup the peripheral to advertise as a iBeacon when the connection is broken. How it is setup is that when the BLE connection is broken the peripheral advertises as a iBeacon for 10 seconds and then switches to normal advertising for 5 minutes and repeats this iBeacon and normal advertising loop until the BLE connection is established again. On the App side we setup Region monitoring so that when the peripheral advertises as a iBeacon the region monitoring starts the Application up. Would this have a negative affect on what you mentioned in point 1 above with trying to connect as soon as possible? Or any other negative side effects we don't know off? Thanks again for you assistance in the matter. Reinhart Fourie

Sorry Argun, I missed one detail around using the iBeacon. We are trying to cover a edge case where the user swipes the application out of history. We use the iBeacon to start the App again due to iOS seeing the user termination as a user event and won't allow the app to run in the background. We are planning to change the advertising of the iBeacon so that it is only advertised before we send the sync notification as highlighted in point one of my original post. Hope it clarifies things a bit. Reinhart Fourie