{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
オリジナルの投稿元:BungieNetPlatform
2/4/2017 7:07:47 PM
1
UnhandledException returned since outage
Since the recent login issues I've noticed if my App mistakenly makes an API call with an expired Access Token I get the following payload back, previously I got a sensible message and a different error code:
ErrorCode = 3;
ErrorStatus = UnhandledException;
Message = "<null>";
MessageData = (
);
Response = "<null>";
ThrottleSeconds = 0;
-
10 通の返信As of a couple days ago, my app is also now in essentially a permanent-dead state as a result of this. Since my code was relying on the refresh token error to come back, this means my iOS app is currently DOA unless users logout then log back in, which I have been unsuccessful in communicating to everyone. I have code in review to mitigate the issue with a preflight check to see if the expiration timestamp is already expired, but this is only a stopgap, as theoretically, taking the request time into account, requests could still make it to the API and be expired even if they weren't expired when they left. I came here to post this issue formally and found this topic, since the number of 1-star reviews on my app is steadily rising the longer this issue is present. @vthornheart also told me to create a post with this issue to maybe track the issue better. I'm just glad my app isn't the only one experiencing the issue.
