Api: NOTICE: DestinyUnexpectedErrors being intermittently returned since DLC2 launch

Created on 8 May 2018  路  8Comments  路  Source: Bungie-net/api

We are experiencing some technical difficulties at the moment: there appears to be some issues related to the launch that are causing intermittent unexpected errors from the game servers. We're looking into it, but be advised that 3rd party apps and the Companion may not behave as expected until this is resolved.

bug ready for release

Most helpful comment

After much ado (and some issues involving the lingering old Destiny deployment causing outages in API data), this bug has been resolved. You should be able to consistently contact the API for any user again!

All 8 comments

Just as a heads up, a workaround if you're experiencing this issue is to log into the game with each of your characters - this appears to be resolving the issue for folks who do it.

We believe that we've found a fix - it's being verified as we speak, but we'll need to find an appropriate release window where we can deploy the fix safely. Hang tight in the meantime, and feel free to distribute knowledge of this workaround to others. Note that apps like DIM that load all characters across all linked accounts may not function unless you log in with all characters on all of your linked BNet accounts.

Thanks. Hoping you guys can push something soon.

I very much hope so as well! We'll keep you posted.

Since you mentioned you found a fix, just a heads up that i'm still getting ErrorCode 1618 when I try and hit the "Account/{membershipId}/Character/{characterId}/Stats" endpoint in my Android app i'm working on, but only for Xbox players..? PSN accounts work fine, and it also seems to work fine in my API testing client.

@vthornheart-bng I'm now getting these on PGCR endpoint too - would your fix fix those also?

Yes, those should be resolved as well.

We're targeting a fix for tuesday. I'll let you all know once it's live!

After much ado (and some issues involving the lingering old Destiny deployment causing outages in API data), this bug has been resolved. You should be able to consistently contact the API for any user again!

Was this page helpful?
0 / 5 - 0 ratings