FIRST-Tech-Challenge / scorekeeper

FIRST Tech Challenge Live Scorekeeper Software
89 stars 21 forks source link

Cannot logout on Silk #693

Closed timtim17 closed 6 months ago

timtim17 commented 10 months ago

Describe the bug Was at an event with Kindle Fire tablets using the Silk browser. Inspectors had logged in and successfully used the tablets. When we tried to logout, the tablet would return to the home page still logged into the inspector account. (cookie not being reset?)

Workarounds that were identified included navigating manually to /login/default to pick a new user to login as, or clearing browser cookies.

To Reproduce Steps to reproduce the behavior:

  1. Login as one user
  2. Click on the username in the top right, and click the red "logout" button.
  3. Observe that, in the top right, the user is still logged in

Expected behavior The user is logged out

Screenshots video: https://i.imgur.com/vYGrCjm.mp4

Device (please complete the following information):

Additional context I heard of another event experienced a similar issue, which I believe was using non-Amazon tablets (Samsung? i.e. using Chrome) [edit: the FTA for this other event reports they actually were Fire tablets, but using Chrome]. Personally, I have only been able to reproduce this on my personal Kindle Fire tablets with Silk. As a test, I installed Chrome onto my same tablet and was not able to reproduce the issue.

maths22 commented 10 months ago

Can you upload server logs where this is happening? Logs can be found in ~/Library/Logs/org.firstinspires.ftclive-2024-default

timtim17 commented 10 months ago

Oddly I can't repro this on my tablets anymore, FireOS appears to have updated overnight.

Here is the log from when I was able to repro it yesterday, the tail end of the log aligns with the video I linked (~16:52)

2024_01_15_04_14_11_PM.log

tweirtx commented 10 months ago

I just tested this locally and cannot reproduce...strange

maths22 commented 6 months ago

This appeared to actually be an issue with logging out after logging in with a QR code. It has been fixed in v5.4.0.