We have a BB10 Cascades app with push support. We are seeing the following problem.
The app has set registerToLaunch to true. When the app is closed and a push comes in, the app is started in the background and receives the push InvokeRequest.
The app needs a couple of seconds to do some network communication and depending on the results will trigger a Notification.
The problem is that while the push is being handled in the app, the user cannot launch the app from homescreen. Clicking the icon simply does nothing.
As soon as the app exits using Application::quit() everything is back to normal and clicking the icon will open the app.
Unfortunately the time of the notification is usually exactly the time the user wants to open the app by either opening the notification from the hub or from the homescreen.
I am not seeing any other InvokeRequest or anything coming in when the icon is clicked.
A few questions to hopefully better understand your issue:
1. You mentioned that the results will trigger a "Notification". Are you referring to a notificaiton entry in the BlackBerry Hub? Are you creating this notification as part of your processing of the push? Typically, creating the notification itself should be one of the last things you do when processing the push. Heavy processing should also be avoided while processing a push if possible.
2. Which verison of the Dev Alpha device are you testing with? There are some lags and delays you might see in these devices that you would not typically see in production grade BlackBerry 10 devices. I mention this, because in our Push Collector sample app, the processing of the push seems to be really quick. The app is open, processes the push, and exits in a matter of milliseconds.
3. Have you tried the Push Collector sample app on your device? Are you seeing the problem with the sample as well or is it unique to your app?
4. What version of the OS version do you have loaded on your device?