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

SatisMeter is already shown #17

Open
pykaso opened this issue Jan 9, 2019 · 5 comments
Open

SatisMeter is already shown #17

pykaso opened this issue Jan 9, 2019 · 5 comments

Comments

@pykaso
Copy link

pykaso commented Jan 9, 2019

Hi, I'm getting "SatisMeter is already shown" from our app when I trying to force show a Survey after a user closed it sometime in the past.

I can't find any SatisMeter related views in views hierarchy. So I assume it's really closed.

Of course, this happens only when application stays in memory. After the new app start it's ok.

@jsedlacek
Copy link
Contributor

@pykaso thanks for the bug report. Let us have a look why this happens.

Just for the context: What are you trying to achieve with the forceSurvey flag? Is that for testing purposes, or are you trying to implement the survey in certain scenarios?

@pykaso
Copy link
Author

pykaso commented Jan 10, 2019

Yes, now it's for testing purposes during integrating SatisMeter into our app. I want to be sure, that this issue doesn't prevent opening Satismeter in production.

@jsedlacek
Copy link
Contributor

@pykaso Thanks. It should not matter in production, as it's unlikely that you'd like to show the survey multiple times within one application session.

We will address this in future releases.

@pykaso pykaso closed this as completed Jan 14, 2019
@pykaso pykaso reopened this Jan 14, 2019
@pykaso
Copy link
Author

pykaso commented Jan 14, 2019

The same issue also occurs without a forceSurvey tag. When the user of the application (same device) has changed. It means calling the identifyUser with another userID value.

@jsedlacek
Copy link
Contributor

Thanks for an update on this. This is obviously a bug, although very rare case.

I will keep the issue open until we get to resolve it.

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

2 participants