Open xgerhard opened 2 years ago
Another one: aquaCJA#4689
any chance you were able to find a workaround? I have it so that people can input their profile url and get their destiny profiles from the BungieNext ID, but i was hoping for a cleaner solution...
Nope. Not with the API at least. Manual fixes.
Adding to this to hopefully bump it.
Player Kurumi#8423
returns the same error, yet the profile is here: https://www.bungie.net/7/en/User/Profile/3/4611686018482978970
Another account hitting it:
danielej2k#2330
(User has active account, and all other API calls work.
For visibility I created a new issue, it's similar to #1516 however we're using a different endpoint now.
Some players/accounts can't be found when using exact search.
Example
/Platform/Destiny2/searchDestinyPlayerByBungieName/all/
:Results in:
Get profile:
/Platform/Destiny2/3/Profile/4611686018468074858/?components=100