{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
originally posted in:BungieNetPlatform
2/4/2017 7:56:48 PM
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.
English
-
Are you folks still seeing this today?
-
Even with my preflight workaround in place, about 16% of my users are still seeing this error message. Of which the only thing I can do is log them out and have them log back in.
-
The issue behind this error was patched yesterday around 2PM Pacific time. Have you seen any improvement since then?
-
Edited by larsacus: 2/7/2017 8:32:12 PMI'm still uncertain if I'm just using the wrong documentation, or if this is changing, but it actually looks like the token refresh error code has now changed to code 2111. This is unfortunate, because that now means I need another code change to handle this new error code when it comes back. Previously the access token expired code was 22 (the one that I have in code that was working before last week). { ErrorCode = 2111; ErrorStatus = AccessTokenHasExpired; Message = "Access token has expired."; MessageData = { }; ThrottleSeconds = 0; } Is there a place where all of the error codes are documented? Particularly related to this new auth scheme?
-
Unfortunately, 22 was "unhandled exception" which could be anything and is likely a server side bug (which it was in this case). Now that we fixed that bug, you are seeing the correct error code of 2111. Error code 2111 is the right one to look for to determine if you need to get a new code. Additionally, it is a good idea to keep track of the expiration time of the access token and get a fresh one preemptively.
-
My workaround currently is a preflight check on the expiration time. But based on my analytics, this is not 100% effective. Is there a location where error messages are documented officially somewhere?
-
We have very little official documentation with the exception of this [url=https://www.bungie.net/en/Help/Article/45481]article[/url], and even it does not mention the specific error codes.
-
Is this something we should expect in the coming future? Especially given all of the issues above we have seen regarding error handling and the expected error states of the token handling specifically? Without any documentation, my options are to either revert back to the old cookie-based method (which honestly is sounding like a better experience for my users given the feedback), or patch my code when I see new bungie-domain errors in my analytics and slowly generate my own documentation. With documentation, those of us on the outside likely would have seen many weeks ago that the API was returning the wrong error code for token-refresh scenarios, but it seems we all thought was expected behavior. 🍻
-
I cannot promise what the future holds. We really appreciate you giving this new authentication method a chance. It is an important step in the right direction and we are committed to supporting your efforts. The cookie based method violates our terms of service and so is not recommended. Regardless of the authentication method used, you are bound to get various errors calling our APIs, so merely changing your authentication mechanism won't solve that problem. We are very small team at Bungie providing support for the Bungie.net APIs. Much of what is possible with our APIs would not be understood if were not for the contributions of the developer community and unofficial documentation. There are several resources linked in this group, and many people willing to help including, me, @VThornheart and lots of community members. I understand your frustration, but please keep moving forward.
-
I cannot understate the appreciation I have for the service you are providing to the community with these APIs. The new authentication scheme is definitely the future and is a better overall experience of trust and privacy for the users that they should expect from other developers in the future. I think I and others are simply looking for clarity since we're moving from under-the-table API hacker-esque usage to official-business. The errors we've gotten in the past from the API have largely just been reportive errors that we just parrot back to the user and they try again or resolve it on their characters in-game. I think these new errors have posed a problem simply because the user doesn't really care about them/need to know about them and they're more traffic-control for developers that we need to execute explicit logic whenever they come up. Again, just trying to clarify this for all of us developers so we can move to the official authentication sooner rather than later, and not spook everyone into not wanting to use it. This is why I was so excited about it and why I appear to be one of the first to be using it in something live. 🍻
