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
Created firebase project to get google-services.json,sender id and legacy server key.
Installed push plugin ionic3
Installed cordova-plugin-ms-azure-mobile-apps
To send device token to server,referred method initPushNotification from https://medium.com/@ankushaggarwal/push-notifications-in-ionic-2-658461108c59 this document .
On Azure portal,created new mobile app.Reffered https://docs.microsoft.com/en-us/azure/app-service-mobile/app-service-mobile-cordova-get-started. skipped 1 and 2 step under quick start.
followed steps for creating notification hub:-> Configure a notification hub steps from
: https://docs.microsoft.com/en-us/azure/notification-hubs/notification-hubs-android-push-notification-google-fcm-get-started
ionic cordova build android
Installed application on a device.
Got registeration Id (handler from FCM) success message of registered (‘gcm’,registration id).
While sending Test send push notification from Azure portal,could not match found.(sent notification successfully 0:passed,0:failed)
Push notification could not received on a device.
Please help me out.
The text was updated successfully, but these errors were encountered:
Alessar
transferred this issue from Azure/azure-notificationhubs
Mar 5, 2019
@abhishek3999 Are you still facing this issue with our SDK? If so, can you please provide us some more information on how you are using this SDK with ionic3?
Hi,
I have follwed following steps:
https://medium.com/@ankushaggarwal/push-notifications-in-ionic-2-658461108c59
this document .https://docs.microsoft.com/en-us/azure/app-service-mobile/app-service-mobile-cordova-get-started
. skipped 1 and 2 step under quick start.:
https://docs.microsoft.com/en-us/azure/notification-hubs/notification-hubs-android-push-notification-google-fcm-get-started
Please help me out.
The text was updated successfully, but these errors were encountered: