Hey all
I’m seeing that system.cancelNotification with a handle will consistently segfault the app in versions 840 onward(although I haven’t tested previous to this). I’ve logged a bug but I find it odd that I’m the only one to have this issue - I can’t find reference to anyone else having the problem. Either I’m doing something very wrong or no one uses this API. I can understand why this might be the case - it’s not particularly useful given that the schedule method returns user data that cant be persisted between launches - perhaps everyone’s just gone the route of cancel all and reschedule all on any change required (as I’m about to do. Sigh.)
Is anyone else experiencing this? The following code will do it for me :
[lua]display.setStatusBar( display.HiddenStatusBar )
io.output():setvbuf(‘line’)
local textLine = “I am the very model of a modern major general…”
local textDisplay = display.newEmbossedText(“Scheduling…”, display.screenOriginX,0, native.systemFont, 10);
local notification = system.scheduleNotification(1000, {
alert=“You are about to forfeit your match”
}),
print(“notification”, notification)
timer.performWithDelay(1000, function()
system.cancelNotification(notification)
end)[/lua] [import]uid: 117383 topic_id: 29282 reply_id: 329282[/import]