Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OneSignal - How to avoid hardcoded APP_ID ? #9

Open
flaviocordova opened this issue Jan 28, 2019 · 2 comments
Open

OneSignal - How to avoid hardcoded APP_ID ? #9

flaviocordova opened this issue Jan 28, 2019 · 2 comments

Comments

@flaviocordova
Copy link

Hi...

I'm trying to use OneSignal module but I can't figure out how to avoid hardcoding APP_ID... the documentation shows this example:

oneSignal: {
    init: {
      appId: 'APP_ID',
      allowLocalhostAsSecureOrigin: true,
      welcomeNotification: {
          disable: true
      }
    }
  }

But I need APP_ID to be wired dynamically on runtime (using a promise, maybe) after getting this information from the server (in a spa-mode app).

Is there any way to get it ?

This question is available on Nuxt community (#c91)
@ghost ghost closed this as completed Jan 28, 2019
@ghost
Copy link

ghost commented Jan 28, 2019

This issue as been imported as question since it does not respect pwa-module issue template. Only bug reports and feature requests stays open to reduce maintainers workload.
If your issue is not a question, please mention the repo admin or moderator to change its type and it will be re-opened automatically.
Your question is available at https://cmty.app/nuxt/pwa-module/issues/c91.

@arielkuzminski
Copy link

@flaviocordova did you work it out?

@pi0 pi0 reopened this Apr 16, 2020
@pi0 pi0 transferred this issue from nuxt-community/pwa-module Apr 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants