SAM Asset Manager - Push Notifications

[mara_sol]

Hi SAM experts!

We have followed the complete configuration guides for the activation of PUSH Notification from ERP to SAM.

When we test the push notifications from MOBILE SERVICES, using the "Send Notifications" option:

Messages are not received in the mobile device, and we can see in the Push statistics that the messages are being SENT, but not RECEIVED.

Any clue on what could be missing.

Attached some additional images on configuration done.

We are using a CUSTOM app.

0-firebase-cloud-messaging.jpg

0-firebase-general.jpg

1-mobile-services.jpg

2-mobile-services-push-notification.jpg

authorization-notification-user.jpg

google-services-json.jpg

sdk-configuration.jpg

trust-identity-provider.jpg

[mara_sol]

We finally were able to get the push notifications!

We had some trouble with the user identification, since we are using SSO, and in some places SSO user must be indicated, but in the RFS S* user is required.

Also, something to be aware, when you Send a push notification here:

In the pop-up, only using the Advanced tab works OK. If sent via General tab, it did not work for us!

Regards

Maria

[former_member135739]

Dear María,

S user required in RFC on this tab?

Thanks

[muhammad_rafay]

Hi María,

Few things you can do to debug this.

• Are you seeing any push registration for the device after the app initialization is complete? Push registration is triggered after the initial sync is completed and you should see a pop-up message where the app asks for permission for Push (at least in iOS) so please let me know if you are seeing that? If you are, check-in the mobile service under User registration that the corresponding user has the UUID populated. Usually, that's the first thing we would want to debug since without successful registration the device wouldn't know where to push?
• Did you try putting a breakpoint on the metadata to check if the device is actually getting any push and how the payload look like? If you are using out of the box client then can you please confirm what is the payload look like?
• Can you see the Logs in the Mobile Service (filtered by Push notification) and check if you see any useful error message? When you send the push using the "Send Notification" button, it won't throw any configuration errors so you might have to check on that.
• If the device is registered and the payload is correct, then you will need to create a branded client to debug this issue further.

[mara_sol]

Thanks Muhammad! Really appreciate your help 😀

We were able to activate an extended log for push notifications, and we have a clue now!

screenshot-20211201-093124.png

We"ll try to solve this error!! And post back the solution in case somebody else has the same problem.

Regards

Maria