You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are trying to send a push notification on android device using GCM/FCM with the latest Notification-Hubs-java-sdk version (1.0.4).
We wrote the same code in dotnet and we can successully send a notification. Using the java sdk we see that the notification are received on notification hub but they never pass to successfull status on dashboard.
Watching the situation on firebase with the java code none of the notification are delivered to the account. Instead, the same hub, used by dotnet delivered notification successfully.
Even I am facing the same issue. I am using fcmV1 whose support was recently built in this sdk. However facing the same problem. Can see that incoming notification count is increasing on azure hub, however not of them actually reach the device.
Also tried using the test send option from portal, it works and notificaitions also work
Also facing the same issue, any solutions? "Test Send" works but not via SDK. notificationId is null but trackingId exists in the outcome
edit: Notification.createFcmV1Notification("{ \"message\": { \"notification\": { \"body\" : \"hello\"} } }") worked. The issue seems to be with my template
Uh oh!
There was an error while loading. Please reload this page.
We are trying to send a push notification on android device using GCM/FCM with the latest Notification-Hubs-java-sdk version (1.0.4).
We wrote the same code in dotnet and we can successully send a notification. Using the java sdk we see that the notification are received on notification hub but they never pass to successfull status on dashboard.
Watching the situation on firebase with the java code none of the notification are delivered to the account. Instead, the same hub, used by dotnet delivered notification successfully.
Working Dotnet code
NOT Working Java code
The text was updated successfully, but these errors were encountered: