Forum Discussion

REDACTED__USER's avatar
REDACTED__USER
Explorer
1 year ago
Solved

Cannot read property ‘display_name’ of null

When I open my Quest Store on my Quest 2, it says the message above. It started at 10:28 pm.

  • KorvinNasa13's avatar
    KorvinNasa13
    1 year ago

    A working solution (temporary, until they fix it):

    I managed to fix it on my end. What helped me (permanently) was to open the Meta app (via phone), connect to the device, then enable and disable Developer Mode. That is, if Developer Mode is already enabled, you need to disable it and enable it again, then restart the device. If Developer Mode is disabled, simply enable it and restart the device.

    I’m not sure if everyone will see Developer Mode in the app because I created an organization in Meta a while ago to have the ability to enable and disable Developer Mode. Therefore, this advice might not work for everyone. By the way, I’m using v72.

    Meta app --> headset settings --> Developer mode

     

    CURRENT UPDATE: Factory reset doesn’t help (don't waste your time). We’re currently waiting for a solution from official support.

     

    Original post:

    It helped me; I was able to download and install a couple of games (from the store), but then the problem came back after a while. So, it’s probably not worth spending time on this—it seems like something on their end

    UPD 

    Most likely, when I did a factory reset, the store cache (another cache?) was also cleared, and then when it was reloaded, a null reference occurs due to a mismatch of variable names or something like that (and  the problem returned)

32 Replies

  • CoolstuffTF2's avatar
    CoolstuffTF2
    Honored Guest
    1 year ago

    Same here. I'm unable to use the store on my Meta Quest 3. No fix AFAIK. Soz.

  • KorvinNasa13's avatar
    KorvinNasa13
    Explorer
    1 year ago

    The exact same error appeared after I installed the v72 update. I'll try doing a factory reset

    • KorvinNasa13's avatar
      KorvinNasa13
      Explorer
      1 year ago

      After the factory reset, everything started working—annoying. In general, it’s recommended to do a factory reset after every major update, for example, when moving from v71 to v72 (patches within the same version can be ignored).

      • HoliamRoberts's avatar
        HoliamRoberts
        Adventurer
        1 year ago

         

        KorvinNasa13 wrote:

        After the factory reset, everything started working—annoying. In general, it’s recommended to do a factory reset after every major update, for example, when moving from v71 to v72 (patches within the same version can be ignored).

        May I ask WHO recommends a factory reset after every major update? I have never seen this quoted anywhere. A factory reset is only required as an absolute last resort. My Q3 is 11 months old and never been factory reset and is used daily.

  • Artimus_777's avatar
    Artimus_777
    Explorer
    1 year ago

    I have th same error in the store and I'm still on v71, dont have v72 yet. I tried reset twice but it did not fix the problem. I hope after update when I get it.

    • Anderzie's avatar
      Anderzie
      Honored Guest
      1 year ago

      thanks for posting this i was just about to factory reset but if it didn't fix the issue i might wait for a response from meta 

  • KorvinNasa13's avatar
    KorvinNasa13
    Explorer
    1 year ago

    A working solution (temporary, until they fix it):

    I managed to fix it on my end. What helped me (permanently) was to open the Meta app (via phone), connect to the device, then enable and disable Developer Mode. That is, if Developer Mode is already enabled, you need to disable it and enable it again, then restart the device. If Developer Mode is disabled, simply enable it and restart the device.

    I’m not sure if everyone will see Developer Mode in the app because I created an organization in Meta a while ago to have the ability to enable and disable Developer Mode. Therefore, this advice might not work for everyone. By the way, I’m using v72.

    Meta app --> headset settings --> Developer mode

     

    CURRENT UPDATE: Factory reset doesn’t help (don't waste your time). We’re currently waiting for a solution from official support.

     

    Original post:

    It helped me; I was able to download and install a couple of games (from the store), but then the problem came back after a while. So, it’s probably not worth spending time on this—it seems like something on their end

    UPD 

    Most likely, when I did a factory reset, the store cache (another cache?) was also cleared, and then when it was reloaded, a null reference occurs due to a mismatch of variable names or something like that (and  the problem returned)

  • DaEmBe's avatar
    DaEmBe
    Honored Guest
    1 year ago

    Same Problem here.

    Yesterday after I signed in in quest + I got this bug

  • Zellss's avatar
    Zellss
    Explorer
    1 year ago

    Same problem here, quest 3 (v72). Started yesterday at night. Did a factory reset, but the problem returned.

  • Aenaya's avatar
    Aenaya
    Honored Guest
    1 year ago

    Quest 3 here and the same thing happened to me. I was in the store and then logged out to review a game on YouTube and when I came back 10 mins later I was unable to log back into the store. Quite frustrating!

  • Gee.See's avatar
    Gee.See
    Honored Guest
    1 year ago

    Brand new Quest 3 here as well (v72) foreced upon me during set-up 😀.

    Same issue as above, no access to the store on the headset.

    Same error message: Cannot read property ‘display_name’ of null

    Also Facebook, Messenger, Horizon Worlds, and WhatsApp keep re-loading to my library although I uninstalled those apps.  Most strange. I hope this gets a fix soon.

     

Related Content