node-pushnotifications | Push notifications for GCM , APNS , MPNS , AMZ | Notification library

by appfeel JavaScript Version: 3.0.0 License: MIT

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | node-pushnotifications Summary

node-pushnotifications is a JavaScript library typically used in Messaging, Notification, Nodejs applications. node-pushnotifications has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can install using 'npm i node-pushnotifications-http2' or download it from GitHub, npm.

Push notifications for GCM, APNS, MPNS, AMZ (automatic detection from device token)

Support

Quality

Security

License

Reuse

Support

node-pushnotifications has a low active ecosystem.

It has 518 star(s) with 117 fork(s). There are 19 watchers for this library.

There were 3 major release(s) in the last 12 months.

There are 10 open issues and 97 have been closed. On average issues are closed in 52 days. There are 6 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of node-pushnotifications is 3.0.0

Quality

node-pushnotifications has 0 bugs and 0 code smells.

Security

node-pushnotifications has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

node-pushnotifications code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

node-pushnotifications is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

node-pushnotifications releases are available to install and integrate.

Deployable package is available in npm.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi has reviewed node-pushnotifications and discovered the below as its top functions. This is intended to give you an instant insight into node-pushnotifications implemented functionality, and help decide if they suit your requirements.

send a notification to the list of notifications
Process failure .

Get all kandi verified functions for this library.

node-pushnotifications Key Features

No Key Features are available at this moment for node-pushnotifications.

node-pushnotifications Examples and Code Snippets

No Code Snippets are available at this moment for node-pushnotifications.

Community Discussions

Trending Discussions on node-pushnotifications

Failing APNS for Independent WatchOS6 app

imported library not found after npm install

Push Notifications not working in Testflight

QUESTION

Failing APNS for Independent WatchOS6 app

Asked 2019-Oct-05 at 08:47

After setting up a new independent WatchOS6 app, which now supports push notifications, getting the device to request the user for push notifications and capturing the push token. I can’t get my server to send a push notification.

With all the correct credentials and P8 set up on my NodeJS server, I have tried to push messages to the device... This is the error all the time:

Status 400 - DeviceTokenNotForTopic - Which according to Apple’s documentation, means that the Topic (BundleId of the app) is wrong. But in this case it is not.

Tried 2 different NPM packages (for elimination)

https://www.npmjs.com/package/node-pushnotifications

https://www.npmjs.com/package/apn

Both providing me with the same issue.

Has anyone successfully managed to complete a Independent WatchOS app with APNs? What am I missing

———

Update

To test the node service, a further 2 tests have been made:

Created a new app, iOS this time, with the same Bundle Identifier, using the pushToken and sending a message the service was successful
Created a new app, another watchOS, with a different Bundle Identifier, this was again rejected but the APNs for the same DeviceTokenNotForTopic issue.

To test production, the only way current is to submit to the store for App Store review. TestFlight option is currently not available for the Watch and there is no way to install a production ad-hoc .ipa manually. Once it is in the store I will continue with further tests.

...

ANSWER

Answered 2019-Oct-05 at 08:47

Problem has been solved.

Xcode has a couple of issues, if you rely on Xcode to sort out your certificates in the developer portal then please don't.

I have been in touch with support and after a few days back and forth with logs it has been made aware that:

Apple's documentation for Independent WatchOS applications does not state anywhere that the topic (which is the bundle id) should be the one ending in .watchkitapp
Xcode does not allow you to add the Push Notification Capability to the .watchkitapp thus meaning it never creates the AppId in your developer portal.

The solution to the problem, I had, was to manually go to the developer portal and add the .watchkitapp AppId and create the certificates, thus allowing my p8 certificate on the server to allow pushes to that particular application.

Source https://stackoverflow.com/questions/58094221

QUESTION

imported library not found after npm install

Asked 2019-Jun-11 at 09:56

Following steps from : https://github.com/appfeel/node-pushnotifications#installation

I've installed package :

...

ANSWER

Answered 2019-Jun-11 at 09:28

Try :

delete node-pushnotifications from package.json
Install by npm i node-pushnotifications
Else, you can use install ny yarn

Source https://stackoverflow.com/questions/56540152

QUESTION

Push Notifications not working in Testflight

Asked 2017-Jul-20 at 02:21

Similar to this post, push notifications works on development, but does not work through testflight. Here are screenshots of my certs:

Certificate of type iOS Distribution
App ID. Named (not wildcard). Push notifications enabled for both Development and Distribution - green lights - with all SSL certificates genereated and uploaded
iOS Distribution Provisioning Profile, that usese the above mentioned Certificate and App ID as well as lists Push Notifications among enabled services
distribution and adhoc signing

Using Heroku and "node-pushnotifications". It works on development, does not work on testflight. APN_key.p8 and serviceAccountKey.json are in there as well.

I've been working on this all day and been scouring the internet for answers but have yet to find any. Any ideas?

...

ANSWER

Answered 2017-Apr-20 at 15:41

Issue resolved! we didn't properly set up our node environment in the server (needed NODE_ENV=production)

Source https://stackoverflow.com/questions/43509219

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install node-pushnotifications

You can install using 'npm i node-pushnotifications-http2' or download it from GitHub, npm.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: