This just started happening a couple days ago. Steps to reproduce (tested in Google Chrome stable):
- Log in successfully.
- Allow the session to expire naturally.
- Return to the frame.work tab
- Attempt to log back in (I use login with Google – did not test any other way)
Expected: login should succeed
Actual: I get the flash error message “Could not authenticate you because Actioncontroller::invalidauthenticitytoken”
Additional: at this point if I load up Chrome developer tools > Application > Storage and ‘Clear Site Data’, then reload the page, I can click Login with Google again and it will work.
1 Like
This morning I opened my laptop and my previously signed-in tab had correctly logged out and redirected to the login page. I clicked the Google login button and got the ‘ActionController…’ error. I clicked the Google login button again and it correctly logged in. That’s… an improvement 
Hey there, are you still experiencing this? We’ve been trying to replicate this issue on our side, but haven’t been able to. If you’re able to replicate, can you walk me through it to share to the team? Thanks!
@catastrophic I can’t reproduce it on-demand, unfortunately. I think this may be a situation where you’ll need to go to backend logs to try and identify instances of this.
Relatedly, another intermittent issue I’ve experienced, which just reproduced again for me this morning:
- Come to website having been previously signed in, with session now timed out.
- Click Sign in in the menu
- Click Continue with Google and complete Oauth sign-in on the Google screen
Expected: redirect completes back to appropriate frame.work webpage
Actual: browser redirects to https://frame.work/flash_messages and will redirect no further. Refreshing the page also does not trigger a redirect. If I manually navigate to frame.work, I do have an active login session now.
in both instances are you trying to log into frame.work or community.frame.work?
I believe this should be fixed now. Please let me know if you are still experiencing issues or others come up. Thanks again for flagging this!
I was able to reproduce this issue just now.
was it the same steps as above?
Yes – I returned to the frame.work tab where a previous login session had timed out and immediately clicked Continue with Google and got that error. Clicked Continue with Google again and was logged in successfully.
Thanks, bringing to the team again to see what’s going on there.
