Not authorized to view my own post

I have a post (https://developer.apple.com/forums/thread/825224) from a day or so ago. I got a nice reply asking for some followup information, but I'm not longer authorized to view or reply to the thread.

The weird thing is I often do see the thread for a second or two, then the page gets replaced with "Unauthorized. Access to this place or content is restricted. ..." without me doing anything.

Sometimes I can see the page for longer, but posting a reply usually results in an error (and frustratingly, the contents I write disappears).

Hmm... I have reported the same issue here. But I guess they have decided not to do anything with it although I spent some 15 minutes figuring out the correct thread URL.

@Resonious Thanks for providing this feedback about the forums. A screenshot is always useful. Closing and opening the browser to delete all data should be a good test to see if that's the issue.

@Tomato I can assure you Quinn took notes and filed it internally. Thanks for the report and going over the URL.

Albert
  Worldwide Developer Relations.

We’ve been hunting a number of different issues with symptoms like this:

  • In one, the presence of a URL parameter (that is, stuff after the ? in a URL) causes forums to behave strangely. Which would be fine if forums didn’t generate notifications with those parameters! |-: (r. 172326632)
  • In another, long URLs cause grief for the forums JavaScript code (r. 173685799).

Neither seems to exactly match the symptoms you’ve described, so I have a couple of diagnostic tests I’d like to try.


The first one is simple: Open the thread’s URL, https://developer.apple.com/forums/thread/825224, in a private browsing window. Does that show the content?

In my case it does, so if this fails for you that’d be super interesting.


The second is to repeat your normal test but with JavaScript disabled. If you’re using Safari on the Mac, disable JavaScript using Safari > Settings > Security > Enable JavaScript.

The reason I’m asking about this is that, in my experience, lots of ‘it starts to show correctly but then fails’ are triggered by JavaScript issues.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Not authorized to view my own post
 
 
Q