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

is there a way to have access to getInAppShowingWaitTimeInterval value? #533

Closed
elanovasconcelos opened this issue Feb 22, 2022 · 4 comments

Comments

@elanovasconcelos
Copy link

is there a way to have access to getInAppShowingWaitTimeInterval value? I need this value, but I couldn't find a way to get it

@tapashmajumder
Copy link
Contributor

Sorry this is a private value. Can you please explain why you need access to this?

@elanovasconcelos
Copy link
Author

There are some moments that I start or stop showing messages, but I need a way to know if it's ok to show again messages respecting the retryInterval.

another question: is there a way to dismiss the current message (IterableInAppHTMLViewController) by code?

@tapashmajumder
Copy link
Contributor

Hi @elanovasconcelos It will be unidiomatic for us to provide access to this value. This is used internally to schedule next in-app message. If you want to show an in-app manually then you can just show it anytime and don't need to worry about the retry interval.

No, currently there is no way to dismiss the current message by code? Are you thinking about a message that stays on the screen for sometime and then disappears after that? Maybe that is something we can look at in the future.

@roninopf
Copy link
Contributor

roninopf commented Sep 6, 2022

Closing due to age, if you feel that this is a relevant issue, I actually suggest letting your CSM know that this in particular is a feature request. Thanks!

@roninopf roninopf closed this as completed Sep 6, 2022
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