Search Unity

  1. Calling all beginners! Join the FPS Beginners Mods Challenge until December 13.
    Dismiss Notice
  2. It's Cyber Week at the Asset Store!
    Dismiss Notice

PlayerPrefs in 2019.1

Discussion in 'WebGL' started by roka, Apr 21, 2019.

  1. roka

    roka

    Joined:
    Sep 12, 2010
    Posts:
    457
  2. APSchmidt

    APSchmidt

    Joined:
    Aug 8, 2016
    Posts:
    2,861
    Did you try?

    I'd like to test that problem in 2019.1.0f2 but I don't understand the description:
    • If I choose "build and run" the game will be build and I won't be able to add any text anywhere,
    • where am I supposed to add a text?

    Capture_3.JPG
     
  3. reitzensteinm

    reitzensteinm

    Joined:
    Feb 9, 2015
    Posts:
    12
    This is fixed now in 2019.2.0a13, so hopefully the fix is included in the next 2019.1 patch.
     
  4. roka

    roka

    Joined:
    Sep 12, 2010
    Posts:
    457
    According the tracker link , it's fixed on 2019.2 but if you look at the release date of the 2018.2 , the Unity 2018.2 has been released un July 2018, so, we have to wait after July 2019 to get this fixed?

    Do you think that it's normal???
     
  5. De-Panther

    De-Panther

    Joined:
    Dec 27, 2009
    Posts:
    289
    Read again, he wrote "the fix is included in the next 2019.1 patch"
     
  6. roka

    roka

    Joined:
    Sep 12, 2010
    Posts:
    457
    No, reitzensteinm said "hopefully the fix is included in the next 2019.1 patch" but the tracker link said "Fixed in Unity 2019.2" (Version that should be released in July....) https://issuetracker.unity3d.com/issues/playerprefs-dont-get-saved-in-a-webgl-build

    They have released the version Unity 2019.1.2 and it's still not fixed (according the release note) and this bug has been reported the 26 March ! Great job !
     
    OneManArmy3D likes this.
  7. De-Panther

    De-Panther

    Joined:
    Dec 27, 2009
    Posts:
    289
    Right :/
     
  8. reitzensteinm

    reitzensteinm

    Joined:
    Feb 9, 2015
    Posts:
    12
    I just tested a build with a sample project in 2019.1.2 and it does actually appear fixed. It really, really should be in the patch notes... This is/was a critical issue that impacts every single WebGL game.
     
    De-Panther likes this.