Community Forum login fails on iPhone with OIDC authorization error

Forum feedback
1

I’m getting a persistent OIDC authorization error when trying to log in to the OpenAI Community Forum on iPhone. I logged out on Tuesday, April 7 and haven’t been able to login since then.

What works:

  • Forum login on desktop

  • OpenAI API login on iPhone

  • ChatGPT app on iPhone

  • ChatGPT in iPhone browser

  • help.openai.com in iPhone browser

What does not work:

  • Community Forum login on iPhone browser

The error is always:
“Sorry, there was an error while trying to authorize your account with oidc. Please try again.”

I’ve already been in contact with OpenAI Support and tested multiple troubleshooting steps, including:

  • Safari and Chrome on iPhone

  • normal browser session and private/incognito

  • clearing cookies / website data

  • logging out of browser sessions

  • restarting phone

  • changing DNS

  • different network

  • another iPhone

Same result every time: desktop works, ChatGPT/help/API in browser or app work, but Community Forum login on iPhone fails with the same OIDC error.

One suggestion I got was that this might be an expired client key / stale auth state between Discourse and OpenAI auth that is not renewing properly on mobile, but clearing the related browser data did not fix it.

Has anyone seen this before or know what specifically could cause forum login to fail on iPhone while desktop login and other OpenAI logins still work?

I would love to be able to login with my phone again.

2

Similar topic is here:

3

Thanks @EricGT for raising this with Discourse.

I hope you all will be unblocked ASAP.

4

in general this discourse has been throwing emails late recently as well…

i wonder if the issues are related.

5

You mean the email notifications are arriving late to your inbox?

6

yup exactly that

sometimes hours late

7

image_2026-04-10_184113841
image_2026-04-10_184113841626×311 14.6 KB

8

Let’s hope this gets sorted out soon, now that the issue has been raised in several places and seems to be affecting many users. I’m glad that i raised it here too, not just for myself, but also for those who currently can’t log in at all.

@vb I need to add something else. For about 1.5 weeks, I have been getting notifications when different topics are marked solved, or maybe that’s a new normal and no, it doesn’t bother, just something that I noticed is a new occurrence.

9

Update: I’m logged in with my phone. The issue seems to be solved.

Can anyone else, please confirm that it’s solved now?

10

Thanks for raising this issue with the log-in.
Thanks for sharing that you are unblocked now.

Another user has already raised the issue with the notification spam. It appears this is not affecting all users in the same way but I surely would be annoyed to receive irrelevant notifications.

11

Can’t access the link, since it seems to be private​:thinking:

12

Sorry, my fault. I have removed the link in the post above to avoid further confusion.

13

Also thank you @vb @polepole and @windysoliloquy for confirming that this issue was broader, than just my iPhone. Fingers crossed this is now solved for everyone affected​:folded_hands:

14

It is due to a newly introduced feature in preferences > notifications:
image

15

Perfect! Thanks a lot @aprendendo.next !

There is also a setting when a topic is tracked automatically the account settings under preferences/tracking

This can then be adjusted to personal preferences.

16

Since I read everything (that’s not hidden/private), does that mean I’m automatically tracking everything? Or am I misunderstanding now this “automatically tracking topics”:sweat_smile:

17

Log in is working for me now using the same means that resulted in the earlier error message.

Thanks for all that helped, including those behind the scene that implemented the fix.

18

Thanks probably to you too, with you firm and polite way of swiping down the first reply to your thread over at discourse…

They did not see interested in investigating it at all at first.

Proper social engineering there, indeed.

19

Here now thanks to you starting this thread and @windysoliloquy for passing along my DM and for everyone else involved in getting this resolved.