Infinite reload loop after allowing notifications

[IHIutch]

    "@nuxtjs/onesignal": "^3.0.0-beta.16",
    "@nuxtjs/pwa": "^3.0.2",
    "nuxt": "^2.14.6"

Whether I have notifyButton set in my nuxt.config.js or I use this.$OneSignal.showSlidedownPrompt(), after I select "Allow" in the native prompt, the browser infinitely reloads. If I reset the "Notifications" setting back to "Ask", the issue goes away. Happening in both Chrome and Firefox

[oatkung]

I have the same problem.

[TonyDeplanque]

I have the same problem...

[tjaydk]

Same issue here with both Chrome and Firefox

[Cuke7]

Same here, any news ? Can you actually use this module ?

[ikoshele]

Probably you're trying to debug on dev mode. I had the same issue. If start the app in prod mode, everything works as expected.

[DiegoPerea]

Same issue here. Did you work it out?

[iohansson]

@DiegoPerea I've created a pull request, the solution works for me.
Check it out #36

[z0lo13]

@iohansson do you have a comiled sdk file?

[nt-manlai]

Downgrade your nuxtjs/pwa to same as current nuxtjs/onesignal version like --> "@nuxtjs/pwa": "^3.0.0-beta.16". This worked for me.

[palatok]

@nt-manlai , unfortunately it didn't solve the problem. I am still getting infinite reload loop after downgrading to "@nuxtjs/pwa": "^3.0.0-beta.16" . I am using Chrome 99 on MacOs.

[dennisbusk]

I have the same problem.
It just keeps looping.
Making the whole site unusable

[CHOMNANP]

Anyone manage to get the notification working?
I have the same issue.

[NCLlamas]

I'm currently dealing with this issue as well...surprised there hasn't been any movement or even hint at a solution. This is a pretty big dealbreaker for this module!

[twilliams0001]

Same issue here... Looks like I'll be removing this module!