60 seconds was just for the example. Typically it sends at calculated times of the day, but for testing I wanted to make it easier. Regardless, it still doesn’t solve the problem of the app not launching from the notification with either time method used. Even with the launch arguments it still has the same response.
As a reminder, the notifications work perfectly fine and open the application if it’s already running. It’s only when the app is completely closed and a notification is hit that the app crashes, which leads me to believe it has nothing to do with the time setting.
Hi @hello40,
At this point, I think we’re going to need a bug report filed on this so engineering can inspect it and see what the issue may be. Can you please file one and include the most basic project you have?
http://developer.coronalabs.com/content/bug-submission
Thanks,
Brent
Was this ever fixed? I’m still getting this problem
Hi @zv713,
I’m not sure if the previous poster ever filed a bug report. Can you do so please?
https://developer.coronalabs.com/content/bug-submission
Thanks,
Brent
I just tested the LocalNotifications sample app that shipped with Corona and I don’t see any app crash when restarting the app after the app is completely closed and a location notification occurs. Can you try the sample to see if you get the same results?
If the sample doesn’t fail you should check what your code is doing differently that may cause it to crash.
Ok I dissected the problem. The options table for the scheduleNotification table needed all 4 variables (alert, badge, sound and custom), even though the docs have each of them as optional. This was a bit misleading, but it’s working correctly now.