-
Notifications
You must be signed in to change notification settings - Fork 919
Session #106
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
Comments
try this one |
I've made some changes to address this issue on lasts commits. Can you please, test and report back here? Thanks. |
this issue still happen
|
yes I got same issue.
2021-01-15 12:30 GMT+07.00, Ahmad Gika <[email protected]>:
… https://media2.giphy.com/media/0eMMUFAINUPMlfHUuD/giphy.gif
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#106 (comment)
|
I've followed your steps but I could not reproduce it here. Did you cleaned up your browser cache? |
I did not clear cache browser yet sir
2021-01-15 17:16 GMT+07.00, Cassio Santos <[email protected]>:
…> this issue still happen
>
> * login normaly and you redirect to ticket page
> * go back until see the dashboard page
> * go to ticket page again, you will get blank screen
> * then go back to [main](https://whaticket.economicros.com.br/)
> you will see the ticket page again
I've followed your steps but I could not reproduce it here. Did you cleaned
up your browser cache?
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#106 (comment)
|
This should be fixed now. Could you guys please clear you browser cache and give it a try? |
1.I entered the program login
2.Copy link https://whaticket.economicros.com.br/tickets
3.Logout program
4.I'm pasting the address again to browser https://whaticket.economicros.com.br/tickets
It was supposed to lead to the login screen.
it was redirect to home screen
The session doesn't work
I'm looking Chrome dev console, it gives this error
"error":"Token was not provided."}
The text was updated successfully, but these errors were encountered: