Cannot sync... 500 error #654
-
Ever since the update, I can't sync anymore. I get a 500 error. I can take the URL I'm using and put it in a browser and download the ICS just fine. So I know the link works. I also haven't changed the link in years. It does the same thing on mine and my wife's phones. HTTP 500 java.io.IOException: HTTP 500 |
Beta Was this translation helpful? Give feedback.
Replies: 9 comments 24 replies
-
I get this one with Office365 ics files since yesterday too. Other ics are perfectly fine. It seems that Microsoft is doing something weird with UserAgent:
In the KO case, Office365 issues a redirect to a 500 error page:
So either it’s a definitive change, and this should be sorted out (fake user agent?), either Microsoft has released some bogus change that will be fixed, and… just wait? |
Beta Was this translation helpful? Give feedback.
-
Microsoft doing Microsoft things it sounds like then. |
Beta Was this translation helpful? Give feedback.
-
I don't know enough about coding to figure out what even to request as a change. But is that something the developer could work on if it is a 365 URL? |
Beta Was this translation helpful? Give feedback.
-
I'm encountering the same issue, so I did a bit of testing and they seem to check on a few very specific things. The current UA for me: Working UA: The differences are:
From the linked discussion, I understand that there's some worry about lying in the UA string. I think these changes are fair: each of them is true and has a precedent in the UA strings of major browsers. Chrome's UA for example mentions that it's "(KHTML, like Gecko)". Edge and Opera just put Chrome/xxx strings in there. See https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/User-Agent for examples. Changing the UA string like this might be an easy solution to fix the big Outlook/Exchange ecosystem, without building full UA customization. |
Beta Was this translation helpful? Give feedback.
-
Same here, so ended up here. since a day of 5 indeed. |
Beta Was this translation helpful? Give feedback.
-
Suddenly today it started working? I'm guessing a fix was not made on this side, right? Maybe Microsoft fixed their end? |
Beta Was this translation helpful? Give feedback.
-
We are still going to support custom agents, followup in #663. But it looks like that as of 2025/08/22, Microsoft has reverted some changes, and this is working fine. |
Beta Was this translation helpful? Give feedback.
-
This has started happening to me this morning, from testing anything but a browser user-agent now redirects the request to /owa/auth/errorfe.aspx?httpCode=500&msg=3673577647&owaError=Microsoft.Exchange.Clients.Owa2.Server.Core.OwaBasicUnsupportedException |
Beta Was this translation helpful? Give feedback.
-
So does the new update work for you guys? Since the initial change, I can't get my Office ics calendar to work. If I don't use a custom user agent, I get a HTTP 500 error, when I use a custom one I get "Couldn't parse iCalendar". |
Beta Was this translation helpful? Give feedback.
We are still going to support custom agents, followup in #663. But it looks like that as of 2025/08/22, Microsoft has reverted some changes, and this is working fine.