notifications.scheduleNotification suddenly failing?

Solar2D iOS
#1

We have been successfully using notifications.scheduleNotification to schedule local push notifications on iOS & Android devices, but it appears to have stopped working on iOS recently (can’t pinpoint time).

Our logging on iOS shows us scheduling the notification (in UTC) and returning successfully (“userdata: 0x17444cda8”), but when the time comes, notifications aren’t appearing on the device.

In this particular example the logs at the scheduled time showed something that was unhelpful…

"May  8 17:47:00 Nathans-iPhone-6S CommCenter(libATCommandStudioDynamic.dylib)[81] <Notice>: QMI: Svc=0x22(COEX) Ind MsgId=0x0021 Bin=[<private>]

May  8 17:47:00 Nathans-iPhone-6S CommCenter(libATCommandStudioDynamic.dylib)[81] <Notice>: QMI: Svc=0x22(COEX) Ind MsgId=0x0021 Bin=[<private>]

"

I’m running iOS 10.3.1 and the build was on Corona 3003.

Any help greatly appreciated as it’s an app that’s in production with a lot of users.

#2

That sounds a bit strange.

If you’re using Corona build 3003, there are no recent changes as the binary for iOS for the notifications plugin is from January 2015.

I’m starting to wonder if it may be an issue that started with iOS 10?

#3

Ahh - could be.

#4

If it turns out to be an issue with iOS 10 and the legacy notifications plugin, you can try ‘plugin.notifications.v2’ which was released a few weeks ago. That plugin should be backwards compatible with the legacy plugin with regards to local notifications.

However you would need to use Corona build 3060 or later to use that plugin.

#5

So this turned out to be unrelated to iOS version.

Local notifications were failing due to a race condition that resulted in the notifications being cancelled unexpectedly, and remote was due to an expired certificate.

Sorry for the confusion.

#6

That sounds a bit strange.

If you’re using Corona build 3003, there are no recent changes as the binary for iOS for the notifications plugin is from January 2015.

I’m starting to wonder if it may be an issue that started with iOS 10?

#7

Ahh - could be.

#8

If it turns out to be an issue with iOS 10 and the legacy notifications plugin, you can try ‘plugin.notifications.v2’ which was released a few weeks ago. That plugin should be backwards compatible with the legacy plugin with regards to local notifications.

However you would need to use Corona build 3060 or later to use that plugin.

#9

So this turned out to be unrelated to iOS version.

Local notifications were failing due to a race condition that resulted in the notifications being cancelled unexpectedly, and remote was due to an expired certificate.

Sorry for the confusion.