-
Notifications
You must be signed in to change notification settings - Fork 26
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
[Bug]: Adding promptOptions to init shows a premature prompt #128
Comments
I add the same issue, and I just had my Init parameters in the wrong format. Try with something like that : |
Does it work?
But it still shows the slidedown |
It takes time for the "Auto Prompt" changes to reflect in my website. Sorry for the false alarm. 🙏 |
What happened?
Using 3.0.1.
When filling promptOptions, a prompt shows on page load (with my updated text), however, since it is only an init method, it should not do that. My config to reproduce (uncomment promptOptions).
I tried adding the promptOptions in the
OneSignal.Slidedown.promptPush
method but it does not accept such options. Which would be a better place to add them, by the way.What browsers are you seeing the problem on?
Chrome (Chromium)
What operating system are you running?
Latest iOS in Mac M1 but it is likely just a library issue
Steps to reproduce?
What did you expect to happen?
A prompt should not show on page load simply because of adding promptOptions in the init method.
Relevant log output
No response
The text was updated successfully, but these errors were encountered: