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 Jun 13, 2022. It is now read-only.
I confirm that this is a issue rather than a question.
Bug report
Version
0.0.5
Steps to reproduce
Enable neSignal integration by adding app id on path notifications.webpush.onesignal.appId in config.js
Run the website.
Subscribe -> Push -> Enable Notifications - nothing happens, except various exceptions in debugger about it failing to execute a function in OneSignalSDK.js file
Subscribe -> Push -> Enable Notifications - nothing happens, except various exceptions in debugger about it failing to execute a function in OneSignalSDK.js file
Other relevant information
Your OS: Mac OSX 10.15.4
Node.js version: 13.12.0
Browser version: Chrome 81.0.4044, Mozilla 75.0, Brave 1.7.98
Is this a global or local install? Both.
Which package manager did you use for the install? npx and npm
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Bug report
Version
0.0.5
Steps to reproduce
notifications.webpush.onesignal.appId
inconfig.js
(Same happens on the demo site - https://demo.statusfy.co)
What is expected?
One Signal integration notification pop up
What is actually happening?
Subscribe -> Push -> Enable Notifications - nothing happens, except various exceptions in debugger about it failing to execute a function in OneSignalSDK.js file
Other relevant information
The text was updated successfully, but these errors were encountered: