Parse.User.current() doesn't update local storage. about parse-sdk-js

[Sikandarkhan]

User is being logged out everytime he quits the app. Let me know, If I can get help from localStorage () function?

[andrewimm]

Under the hood, we update an in-memory cache of the current user, but we don't save back to disk on each successful server save.

The solution is to special-case the save of a ParseUser object, checking to see if it is the current user; if it is, we can save back to localStorage before resolving the outermost Promise.

[GauravButola]

Is this a regression in the latest version? Because; I have 1.5.0 in one of my projects where saving the current parse user saves the object to localStorage as well, but on the other project where I'm using 1.6.7 I'm having this issue; the object doesn't persist in localStorage.

Same for fetch() the latest version only saves the current user to memory not localStorage but the earlier version I'm using updates localStorage as well.

[andrewimm]

Just pushed a fix. We will release 1.6.9 later today with these issues resolved.

[bradyhigginbotham]

Is 1.6.9 still being released? I see the tag in this repo, but site and CDN only have 1.6.7. Really need this fix in. Thanks!

[h4rm]

Hi, just checking in to ask if 1.6.9 will be available soon? The CDN is still at 1.6.7 and I am also eager to distribute the fixed version.

[passcod]

The CDN is at 1.6.14 at time of writing, the (recommended way of getting this aka the) npm module is at 1.6.14, this is fixed and should be closed.