Bungie-net / api

Resources for the Bungie.net API
Other
1.22k stars 92 forks source link

SearchDestinyPlayer: UserCannotResolveCentralAccount #1516

Open rentalhost opened 3 years ago

rentalhost commented 3 years ago

Hello!

I am using the SearchDestinyPlayer endpoint, but I cannot search the player SearchDestinyPlayer. It just returns that:

{
    "ErrorCode": 217,
    "ThrottleSeconds": 0,
    "ErrorStatus": "UserCannotResolveCentralAccount",
    "Message": "We couldn't find the account you're looking for. The account may not exist, or we may be experiencing technical difficulties.",
    "MessageData": {}
}

Even for raid.report, for instance, it does not works:

image

The user itself does exists: https://www.bungie.net/7/pt-br/User/Profile/254/23186503/NimbleGuts

image

I can found this same user via GetBungieNetUserById endpoint:

{
    "Response": {
        "membershipId": "23186503",
        "uniqueName": "NimbleGuts#9149",
        "displayName": "NimbleGuts",
        "profilePicture": 0,
        "profileTheme": 0,
        "userTitle": 0,
        "successMessageFlags": "0",
        "isDeleted": false,
        "about": "",
        "firstAccess": "2019-10-15T01:32:01.811Z",
        "lastUpdate": "2019-11-28T21:10:27.673Z",
        "showActivity": true,
        "locale": "en",
        "localeInheritDefault": false,
        "showGroupMessaging": true,
        "profilePicturePath": "/img/profile/avatars/default_avatar.gif",
        "profileThemeName": "d2cover",
        "userTitleDisplay": "Newbie",
        "statusText": "",
        "statusDate": "0001-01-01T00:00:00Z",
        "blizzardDisplayName": "AzulaBoy",
        "steamDisplayName": "NimbleGuts",
        "cachedBungieGlobalDisplayName": "NimbleGuts",
        "cachedBungieGlobalDisplayNameCode": 9149
    },
    "ErrorCode": 1,
    "ThrottleSeconds": 0,
    "ErrorStatus": "Success",
    "Message": "Ok",
    "MessageData": {}
}

But it doesn't returns the membershipId.

rentalhost commented 3 years ago

Via GroupV2/4038658/Members I could found the membershipId, but is too hacky and depends of the member have a clan.

           {
                "memberType": 2,
                "isOnline": false,
                "lastOnlineStatusChange": "1630608126",
                "groupId": "4038658",
                "destinyUserInfo": {
                    "LastSeenDisplayName": "NimbleGuts",
                    "LastSeenDisplayNameType": 3,
                    "iconPath": "/img/theme/bungienet/icons/steamLogo.png",
                    "crossSaveOverride": 0,
                    "applicableMembershipTypes": [
                        3
                    ],
                    "isPublic": false,
                    "membershipType": 3,
                    "membershipId": "4611686018482920661",
                    "displayName": "NimbleGuts",
                    "bungieGlobalDisplayName": "NimbleGuts",
                    "bungieGlobalDisplayNameCode": 9149
                },
                "bungieNetUserInfo": {
                    "supplementalDisplayName": "NimbleGuts#9149",
                    "iconPath": "/img/profile/avatars/default_avatar.gif",
                    "crossSaveOverride": 0,
                    "isPublic": false,
                    "membershipType": 254,
                    "membershipId": "23186503",
                    "displayName": "NimbleGuts",
                    "bungieGlobalDisplayName": "NimbleGuts",
                    "bungieGlobalDisplayNameCode": 9149
                },
                "joinDate": "2021-08-30T22:36:23Z"
            }
floatingatoll commented 3 years ago

What key arguments are you passing to each of these endpoints? Like, what exact string are you searching for "by name", etc.

rentalhost commented 3 years ago

@floatingatoll

https://www.bungie.net/Platform/Destiny2/SearchDestinyPlayer/All/NimbleGuts%239149

My account works normally:

https://www.bungie.net/Platform/Destiny2/SearchDestinyPlayer/All/David%20Rodrigues%230854

ChaseMalik commented 3 years ago

There are many accounts that have this issue (returning ErrorCode 217 on SearchDestinyPlayer call with their Bungie Name):

Here's a sample:

https://www.bungie.net/Platform/Destiny2/SearchDestinyPlayer/-1/Taako%234051/ https://www.bungie.net/Platform/Destiny2/SearchDestinyPlayer/-1/Marvel%232488/ https://www.bungie.net/Platform/Destiny2/SearchDestinyPlayer/-1/Dewski%230261/

Also, note that none of these accounts are returned by the newer User Search api when you remove their Bungie Name Code: https://www.bungie.net/Platform/User/Search/Prefix/Taako/0/ https://www.bungie.net/Platform/User/Search/Prefix/Marvel/0/ https://www.bungie.net/Platform/User/Search/Prefix/Dewski/0/

Cytraen commented 2 years ago

I wonder - could these be because they're Steam accounts with cross-save off? Searching for a friend of mine results in the same issue. Could also be that they were Blizzard/Battle.net accounts, that migrated to Steam, and have cross-save off, as is the case with said friend of mine.

Friend is prism#9661, BNet member ID 17829352

Cytraen commented 2 years ago

Adding an Xbox account and enabling cross-save fixed the issue, for my friend's account at least.

landervervaeke commented 2 years ago

Any update on this issue? I'm getting a lot of questions about users that can't find their Guardian due to this issue. Thanks!