AnastasiiaR

@rlepinski yes, the is no notificationId with a content-available push in the background as well as in the foreground. That would be of great value, as our feature implementation depends...

@rlepinski thank you for your suggestion! We found out that in `onPushReceived` the notifications do have notificationId's if they are accessed through `await Airship.push.activeNotifications`. We took it as a workaround...