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
{{ message }}
This repository has been archived by the owner on Feb 7, 2019. It is now read-only.
The certificates, the provisioning profile, and the p12 files were generated on the same machine (iMac).
The correct certificate and provisioning profile are set up in Sidekick. We are testing it via pushtry.com as well as locally via our API.
I am using a Mac and I followed the instruction from this article to the letter.
The token is generated properly in the correct format and I can verify that the plugin successfully completes the call to registerUserNotificationSettings.
The notifications are enabled on the device and in XCode as well as in the app profile in developer.apple.com.
I am really running out of places to look at. Any suggestion would be greatly appreciated.
Hi @dpdragnev
If you are not using interactive push notifications in your project, you may try implementing the push functionality with the {N} Firebase plugin - not only because we are going to deprecate the push-plugin in the future, but also because the Firebase plugin promotes another way of sending/testing your push notifications (through the Firebase console for both Android and iOS). This may make difference in your setup and work with no errors.
Let us know if you try this way and what is the outcome.
We are experiencing an issue with sending notifications to our test iOS device. Everything works well on Android. Here is our environment:
nodejs: 8.9.4
npm: 5.8.0
tns-ios: 4.1.0
push-plugin: 1.0.4
tns: 4.1.2
The certificates, the provisioning profile, and the p12 files were generated on the same machine (iMac).
The correct certificate and provisioning profile are set up in Sidekick. We are testing it via pushtry.com as well as locally via our API.
Here is how we generate the token:
The text was updated successfully, but these errors were encountered: