Hi Guys, I made a post a few days ago about Push notification with Parse stopping my app from launching when offline. I just wanted to make an update as Parse came back to me with something that David might be interested in. First, I used Parse for push with v2.1.8 without problem, this is the first time I use it with v2.1.9. According to Parse: "You're using a few synchronous, blocking method calls in your app. For example, "save" instead of "saveInBackground". This is not advised, as your main thread will get blocked until the network responds with data, and iOS might kill your app for becoming unresponsive on launch. You should have seen some warnings in the console about this." I didn't get warnings. I don't understand much about this but it looks like it has to do with the BT source code(?) Maybe this can be considered for v3 core? Thanks, Farcat

If you don't mind, may I ask for clarification? You're saying push (with Parse.com) worked ok with BT v2.1.8 but it is not working with BT v2.1.9? And those reasons the folks from parse.com seem to be part of the issue? Cheers! -- Smug

Hi Smug, Thanks for the quick reply. Yes, I had no problem with BT v2.1.8, I followed the same install and BT v2.1.9 seems to cause issues. Just to clarify, the push notification is working, I can push a message and I receive it so the integration of Parse code is OK. Also there is no warning or error message showing on Xcode. It just seems to be an issue when opening the app when offline (it aborts after 15 seconds). I sent the parse folks my debug output and my appDelegate file and they came back with this answer. I have Googled this issue till blue in the face and I couldn't find any related solution. I took the liberty of emailing you my debug output and my appDelegate, just in case you have a few minutes to glance over it. I can remove Parse from my app for now and introduce it later but IF it is BT code related I just wanted to highlight it. Cheers, Farcat