JavaScript is required to use Bungie.net

Help - Destiny 2

Help us help you.
10/16/2024 1:42:48 AM
1

Saving displayName in my profile settings page fails with error code 17 ValidationInvalidInputError - The field \"displayName\" has an invalid value in it. Please provide a valid value for the field and try again

Hello Support I am having an issue with saving my displayName in the website my profile settings page. I am a software engineer and this should be a relatively simple issue to fix. The problem is in the javascript logic in the website. The issue is that there is an error in the POST request validation to the endpoint [quote]https://www.bungie.net/Platform/User/UpdateUser/?lc=en&fmt=true&lcin=true&&;[/quote] returning a 500 and an unresolved promise due to an internal error code 17 (ValidationInvalidInputError) [quote]"The field \"displayName\" has an invalid value in it. Please provide a valid value for the field and try again."[/quote] which is preventing the save. In my case this is the payload being posted and I don't see anything wrong with my chosen displayName. (NOTE: I removed the membership id value and replaced with dots) [quote]{ "displayName": "TheTothHome", "about": "", "profilePicture": 70432, "profileTheme": 1000, "statusText": "", "membershipId": "73.....", "locale": null, "emailAddress": null } [/quote] Looking at the website JS chunks all I can tell is that this is coming from thier UserService and the call to UpdateUser that is failing. The displayName allows up to 26 characters according to the HTML rule on the input and im only using capital and lower case letters so It must be inside the service where something is not treating the validation of the field properly. If the order of inputs changed or they added anything to the call it could be a case where its trying to validate a number or a boolean instead of a string and thus will always fail until that is corrected within the service logic or the post payload from the website on save. [quote]var j = function() { var e, t, n = arguments.length > 0 && void 0 !== arguments[0] ? arguments[0] : f, r = arguments.length > 1 && void 0 !== arguments[1] ? arguments[1] : g; if (l && n !== (null !== (e = null === u || void 0 === u || null === (t = u.user) || void 0 === t ? void 0 : t.locale) && void 0 !== e ? e : "en") || r !== g) { var a = { membershipId: u.user.membershipId, displayName: null, about: null, emailAddress: null, locale: n, localeInheritDefault: r, statusText: null }; x.a.UserService.UpdateUser(a).then((function() { k() } )).catch(o.b).catch((function(e) { return S.a.error(e) } )) } } , k = function() { B.a.show(E.a.Userresearch.SettingsHaveChanged, { position: "br" }) };[/quote]
English
#Help

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Edited by viiTactiiCZz: 10/16/2024 1:52:05 AM
    They're aware of the issue, it seems like an intentional disable due to the bug they're currently trying to fix from last episode. You'll run into the other 2 issues of saving and saving->reverting as well while the filter still checks names. [quote]Bungie Names cannot be changed. We hope to fix this as quickly as possible.[/quote] https://help.bungie.net/hc/en-us/articles/27062192032404-Destiny-2-Year-7-Known-Issues-and-Vital-Information Just a heads up for this bit '(NOTE: I removed the membership id value and replaced with dots)' - its not a secret thing to hide, you can pull anyones Membership id via the API.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

    1 Reply
    You are not allowed to view this content.
    ;
    preload icon
    preload icon
    preload icon