You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 10, 2023. It is now read-only.
A few users reporting this. I see it on chrome in one machine but not chrome on another, so it's intermittent. Unfortunately can't reproduce it in dev right now.
The react debugger suggests that currentIssueId is somehow being set to another issue id in only certain places. So the CallPage is getting the correct issue id and displaying the right contacts / script / etc but when it goes to increment the contactIndices, it sets them to someIncorrectIssueID: 1 which then increases whenever you click a result button - but since it's not the right issue id, it just shows the same first contact over and over.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
A few users reporting this. I see it on chrome in one machine but not chrome on another, so it's intermittent. Unfortunately can't reproduce it in dev right now.
The react debugger suggests that
currentIssueId
is somehow being set to another issue id in only certain places. So theCallPage
is getting the correct issue id and displaying the right contacts / script / etc but when it goes to increment thecontactIndices
, it sets them tosomeIncorrectIssueID: 1
which then increases whenever you click a result button - but since it's not the right issue id, it just shows the same first contact over and over.The text was updated successfully, but these errors were encountered: