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
Issue: intermittent problems signing in to codebuddies.org #1109
Comments
Windows 7 Chrome + Firefox issues reported by @h2c on Slack: |
The error is happening on line 18 of Full code:
|
I initially thought this was a Windows-only error, but I just now had an issue logging in using Slack. I didn't get the first error message in h2c's screenshot. I did get the second error message:
After a couple of tries, I was able to log in. This is on macOS High Sierra + Firefox 65.0 |
@wuworkshop Thank you! Maybe that other issue has higher weight too; will look into it. :) |
@tgrrr also reports problems logging in from Chrome mobile. |
Definitely something weird going on - I've signed on once, then refreshed about two or three times (without signing on again) and the session finally started. |
I looked into this a little and was not able to recreate the login issue. I did experience the one @angelocordon referenced. My guess is that it is a server-side syncing issue. The client code looks good and once the server is "warm" the problem does not happen again. |
Encountered by @cbelsole: I have no idea what the string of characters at the top is (starting from |
That's weird... kind of looks like an SVG data being set as a background property for an icon |
Im having trouble signing in via git hub. I have an email co firming that code buddies has been allocated its github permissions, and I can click the link and see it. But if I click applications from git hub neither type of application shows codebuddies. When I log into codebuddies via github, I get redirected to codebuddies page without completing sign in.. Not sure if anyone has experienced this? |
Thanks to Annie and Bill for reporting.
Should look in console to see if there are any errors.
The text was updated successfully, but these errors were encountered: