Sebastián Katzer
Sebastián Katzer
@stinaa I adapter your code to point to a minute ahead from now but cannot reproduce any issue. The correct date is calculated and the notification is triggered as expected.
You need to use 0.9-beta.3 or at least [these](eb41d94f626402718d4c5eaa35ebca1045856709) commit.
`foreground` requires v0.9-beta. v0.8.x doesn't fully support iOS10+
I havent used the other plugin by myself. Since the code works outside of the callback, you could try to wrap the code inside the callback with `setTimeout`. Maybe that...
By myself I have no trouble using latest versions. I have all latest versions installed and running. It might be possible that the FCMPlugin still uses the deprecated API instead...
@soimthe1 There's a system limit already before iOS 11. If there's a logic/interval behind each notification its wise to schedule repeating notifications instead of hundreds with a fixed date.
```js // With cordova-plugin-local-notification v0.9-beta var plugin = cordova.plugins.notification.local, details = plugin.launchDetails; if (details) { alert('Launched by notification with ID ' + details.id); } plugin.on('trigger', function(toast, e) { console.log(toast); });...
BTW please note that `launchDetails` is broken on iOS with beta.2
> `_launchDetails` is only set if the action/event is equal to `click` Thats probably a bug and will be fixed.
@alesgenova Please make sure again that you're running beta.3 and provide a working sample. In case of date issues its important to know how the start date and the trigger...