I've seen more than ten of these topics floating around. This topic aims to organize and list them so we don't have so many duplicates.
Here's the issue–
- User clicks on Messages to view new notifications.
- User clicks notification that says someone has replied on a profile or in a studio (1).
- The profile page or studio linked to (with the url pointing to a specific comment, e.g., https://scratch.mit.edu/users/Leafsparkle/#comments-314159265) displays “Comments loading…” for as long as the tab is open (2).
- Upon refreshing the page, the user is now signed out in that tab and everywhere else (3). They will have to log back in.
- Even after multiple logouts and logins, clicking the link in Messages will log the user out, and the user profile or the studio will not show the comment.
(If I didn't describe it well, scroll down to “Other descriptions” for different explanations.)
1. I'm only aware of this happening with profiles and studios. Projects seem to be unaffected. Comment below if you've got more information.
2. I've kept the same tab open, without refreshing it, for probably a day. It stayed at “Comments loading…” for the whole time.
3. I haven't tested how this works with multiple devices.
List of topics (non-exhaustive, organized by date of OP, let me know if I've missed a major one)–
- 12349999eeeeeee9S99, 02 July 2019, about signing out
- TheBrozBlamII, 22 August 2019, about signing out
- 1HappyFroYo1, 23 August 2019, about the whole issue, particularly the signing out part (closed)
- Project_1001, 25 August 2019, about signing out
- 100daysummer, 04 September 2019, about signing out, perhaps unrelated
- cs458468, 04 September 2019, about the whole issue, describes the message issue in more detail (OP and here)
- Fireguy27, 05 September 2019, describes the whole issue well
- -MarvelComics-, 07 September 2019, describes whole issue well
- k3e1c4k, 07 September 2019, about whole issue
- CantDoStuff, 07 September 2019, describes whole issue well
- TabsMod, 11 September 2019
- PowerPooka35, 13 September 2019, possibly unrelated
- miriyanguyen, 13 September 2019, possibly unrelated
- randomguyboi, 14 September 2019
- scratchmaster678, 16 September 2019
- XxItsMehPotato, 20 September 2019, maybe related
- Broadway_Geek, 21 September 2019
- itzfandomlife, 26 September 2019
- DARKwordwolf, 27 September 2019
Sometimes when I go to a comment opened from my messages (epecially one that leads to a studio) the comments will load for a long time before I reload and get looged out. (…)
Sometimes, I will be on someone's profile, and the comments won't load. So I reload the page, and I am suddenly signed out.
I have this bug issue as well, and frequently.
When you receive a notification that there is a comment, but it hasn't shown up on the actual page yet, the comments will get stuck “Loading”, and refreshing logs you out. Why the comment doesn't appear in the first place, I don't know, but that appears to be the underlying problem. (…)
I don't know why, but I went to check one of my messages to see one of my profile comments, and the profile comments wouldn't load. So I went to refresh the page, and as soon as I did, not only did the comments still have that issue, but I noticed I wasn't logged in. (…)
(…) Sometimes when I get messages and I click the link that leads me to them, It does bring me to the page where the comments are but the comments won't load. When I try and refresh the page or click anything else, I get automatically signed out of my account (…)
(…) I found that when I clicked my message link to go reply that the comments wouldn't load. If I went into the studio without going through the messages, it would load the comments, but it would not load the person's reply. And often times when switching from different screens and refreshing my browser, it would log me out. (…)
(I think the comment(s) appearing after a bit is probably because these users left comments on the profile(s)/studio(s) in question, thus clearing up the bug as seen in the Scratch Wiki entry and my description in this section – rather than because the page cleared itself up with no user intervention, intentional or otherwise. I've also put my thoughts on this in a separate post. –Leafsparkle)Wait a bit and the comments will appear.
If you look in the “Possible Solutions” section on this wiki article, there are two solutions to this problem. Hope I helped! :D
Sometimes, if a user comments on one's profile later, the comment that previously would not show may appear. Then, the user can view, reply, delete, or report the comment. This works with most users, but is only temporary. This will need to be done again when another comment will not show.
Clearing the browser's cache may help fix this problem. If one uses Google Chrome, they can go to “Clear Browser Data” in Settings, click “Advanced,” then select the following:
Cookies and other site data
Cached images and files
To clear the entire cache, one can select “All time.” Then, they can click “Clear Data.”
Note Warning: Clearing one's cache may sign the user out of some websites, requiring the person to login again. Also, it may take longer to open some websites because images and other graphics will need to be reloaded.
Go to the main profile or studio page (rather than the direct link to the comment). Leave another comment on the page. Then, look for the original comment. It should now appear, and clicking the direct link to it should not sign you out.
I hope this post helped you, and let's hope we can solve the issue! In the meantime, try the above fixes.
Comment below if you have additional fixes, other threads to add, hypotheses, or anything else!
You have no idea how much time I spent compiling this.
My browser / operating system: Linux, Chrome 74.0.3729.131, No Flash version detected
Edited for typo, content misrepresentation.
Edited again to add some more topics about the issue. There are so many of them…
Edited yet again. The reports keep coming in. Also, fixed the opaque Scratch Wiki wording.
Edited again right after edit no. 3 to note an observation about the “wait and the comments will load” possible fix.
Edited again right after edit no. 4 to link to further thoughts about this observation, which you can find through the link in this post and in the comments below.
Edited again to add another topic and note the possible unrelatedness of a previously added topic.
Edited again because I made a small and execrable formatting error.
Edited to add two new topics about the issue (sigh) and because I realized I've been doing lists wrong this whole time.
Edited to add another topic.
Edited to add another topic.