Skip to content
This repository has been archived by the owner on Jun 13, 2022. It is now read-only.

OneSignal does not seem to work #534

Open
1 task done
tovbinm opened this issue Apr 25, 2020 · 5 comments
Open
1 task done

OneSignal does not seem to work #534

tovbinm opened this issue Apr 25, 2020 · 5 comments
Labels
bug Something isn't working pinned Important Issues
Milestone

Comments

@tovbinm
Copy link

tovbinm commented Apr 25, 2020

  • I confirm that this is a issue rather than a question.

Bug report

Version

0.0.5

Steps to reproduce

  1. Enable neSignal integration by adding app id on path notifications.webpush.onesignal.appId in config.js
  2. Run the website.
  3. Subscribe -> Push -> Enable Notifications - nothing happens, except various exceptions in debugger about it failing to execute a function in OneSignalSDK.js file

(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

  • 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
@welcome
Copy link

welcome bot commented Apr 25, 2020

Thanks for opening this issue, a maintainer will get back to you shortly! Be sure to follow the issue template! 🤓

@juliomrqz juliomrqz added the bug Something isn't working label Apr 27, 2020
@tovbinm
Copy link
Author

tovbinm commented May 1, 2020

@juliomrqz do you have an idea on the fix for this issue?

@tovbinm
Copy link
Author

tovbinm commented May 15, 2020

Hi, folks. Are there any updates on this?

@juliomrqz juliomrqz added this to the 1.0.0 milestone May 20, 2020
@stale
Copy link

stale bot commented Jun 9, 2020

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.

@stale stale bot added the wontfix This will not be worked on label Jun 9, 2020
@juliomrqz
Copy link
Owner

juliomrqz commented Jun 9, 2020

This will be fixed in the next major release. For more information you can review this announcement #551

@stale stale bot removed the wontfix This will not be worked on label Jun 9, 2020
@juliomrqz juliomrqz added the pinned Important Issues label Jun 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working pinned Important Issues
Projects
None yet
Development

No branches or pull requests

3 participants