re-notif | Redux & React based Notifications center | Notification library

First note that:

• By default Laravel Notification's migration file doesn't have a deleted_at.
• You are calling Illuminate\\Notifications\\Notification which doesn't extend Model class so there is no withTrashed() method.

Solution:

What we are going to do is a workaround. You need to create a Notification model (in your app directory or app/Models if you are using Laravel 8) which extends Model then you will use SoftDeletes trait.

I used a real device to debug the application and I got an error message: "Java.Lang.RuntimeException: 'Unable to instantiate receiver com.google.firebase.iid.FirebaseInstanceIdReceiver: java.lang.InstantiationException: java.lang.Class cannot be instantiated'"

This was due to my code shrinker (ProGuard/R8) missing some configurations. Following this article I created a proguard.cfg file and added this:

Is it necessary to use one of those methods if my app registered with the notification-hub using the NotificationHub.Start() method?

When you invoke NotificationHub.start(Application, ...), the Android SDK will listen for changes like added tags, new FirebaseMessagingService tokens, etc. Anytime it detects a change, it will invoke an InstallationAdapter to inform a backend of the new details.

The default InstallationAdapter will send an PUT request to the Azure Notification Hubs backend as documented here. This is what is created by NotificationHub.start(Application, string, string); for people who are not hosting their own backend, this is a sensible default.

If you have your own backend where you track devices, or you're just looking to keep your credentials server-side, you can swap out the InstallationAdapter to be a class that invokes your API. All you need to do is implement the InstallationAdapter interface and initialize the SDK by calling NotificationHub.start(Application, InstallationAdapter).

If you use the NotificationHub.start(...) methods as indicated above, there is no further registration action required.

With that in mind is it possible to use the NotificationHub.InstallationId to use as a tag (eg: "handle:") to send device-specific notifications?

Yes! This documentation walks you through how to use the special tag format $InstallationId:{YOUR_TAG_ID} to target a specific device.

When you've used NotificationHub.start(), if you do not specify an InstallationId, it will generate one for you.

Finally it has been brought to conclusion. If anyone's interested:

1. Hub Registrations must be called in main thread. Otherwise Xamarin.Azure.NotificationHubs.iOS wouldn't even give a hint that something went wrong.

2. New approach with MSNotificationHub has a bug in getting UserInfo with casting it to NSDictionary when actual type is NSDictionary. It is issued in GitHub for a while now, but still without any response from team, so if you pass any data besides message through push notification, sorry, it's no go.

3. Old approach using SBNotificationHub has strict Template format. First of all, you shoud use RegisterTemplate method that outs error, not one that do callback, as the former one is the only that gives error description for some reason. Secondly, you can't define template using {$(field)} constructon, you need to specify insertion format for properties, like: "alert":"$(messageParam)","badge":"#(badge)","content-available":"#(contentAvailable)" etc. Also you need to modify dispatcher so it would always send unquoted parameters.

IOS implementation is extremely raw, half-done and forgotten. I understand that interacting with Apple is utter hell and pain in the rear, but still...

Hope it saves someone lots and lots of time.

You won't see this package when implementing it from gradle. Because this package is an EAP ("early access program"). So you can copy this library and paste it to your application from the following link: https://github.com/google/exposure-notifications-android/tree/master/app/libs

Also, have a look at this issue for more information: https://github.com/google/exposure-notifications-android/issues/23

Guava 21 is Java 8 only.

Update your gradle to Guava version 27.0.1-android, which is compatible with Android:

Gradle 4.6+:

If you want to use your Notification as part of a foreground service, rather than manipulate flags directly, use startForeground() and stopForeground() on your Service.

While creating registrationId , you dont have to pass any id. **createRegistrationId(callback)** takes callback as a parameter which creates a registration identifier.

As per the overall implemetation:

Assuming you have the APNS Auth Key correctly configured in the firebase console, and considering your appDelegate implementation you have provided, the only piece of code i see missing is the FIRInstanceId creation.

According to Firebase documentation here :

Instance ID provides a unique identifier for each app instance and a mechanism >to authenticate and authorize actions (for example, sending an FCM message).

Once an InstanceID is generated, the library periodically sends information >about the application and the device where it’s running to the Firebase >backend.

And here

To send or receive messages, the app must get a registration token from >FIRInstanceID. This token authorizes an app server to send messages to an app >instance.

Just before where you register for remote notification in your application didFinishLaunching..., add this before the application.registerForRemoteNotifications()