[PFUser currentUser] does not update in Watch Extension when log out and vice versa

[PatrickAdams]

I'm having an issue where the Apple Watch is not reflecting the currentUser when changes are made in the iPhone app. Groups and keychains are set up correctly. Noticed some other people having this same issue. When I log out on the iPhone, currentUser is not nil on the watch. When the user is nil on the watch and I log in on the phone, currentUser is still nil.

[parse-github-bot]

Thank you for your feedback. We prioritize issues that have clear and concise repro steps. Please see our Bug Reporting Guidelines about what information should be added to this issue.

Please try the latest SDK. Our release notes have details about what issues were fixed in each release.

In addition, you might find the following resources helpful:

• Documentation: https://www.parse.com/docs
• Google Groups: https://groups.google.com/forum/#!forum/parse-developers
• Stack Overflow: http://stackoverflow.com/tags/parse.com

[richardjrossiii]

Thanks for the report. Any chance you can create a small project demonstrating the bug here on github? It really does help us track these things down easier.

[PatrickAdams]

Am I wrong in assuming this is the way it should work? With the [PFUser currentUser] always in sync?

-- 
Patrick L. Adams

On September 1, 2015 at 4:47:30 PM, Richard Ross ([email protected]) wrote:

Thanks for the report. Any chance you can create a small project demonstrating the bug here on github? It really does help us track these things down easier.

—
Reply to this email directly or view it on GitHub.

[nlutsenko]

Hey @PatrickAdams, your assumption is absolutely correct, there could be a few gotchas about this one, but I think there is a bug here somewhere, for sure.
That's why we have it marked as needs investigation in addition to simply needs more info.
The repro project would help us tremendously in tracking down the issue you are facing.

[PatrickAdams]

Yea, it would take me a decent amount of time to set up a repro project that I don't have at the time. Maybe you could take a look at my existing project?

[PatrickAdams]

@richardjrossiii @nlutsenko Ok, so I created a project that reproduces the bug, where should I send it?

[nlutsenko]

You can send it to [email protected].
Will take a look as fast as I can, and get back to you.
Probably next Tuesday (it's a public holiday here on Monday).

[PatrickAdams]

sent.

[PatrickAdams]

@richardjrossiii @nlutsenko Hey guys, have you dug into my bug repro project? Curious if you are getting anywhere with this. The launch of my app is dependent on it.

[amg1976]

I'm having a similar issue, although I was never able to see the logged user on the app extension

https://github.com/amg1976/Futebol365-iOS

[kentoh]

Any updates? We've struggled with this for quite some time. Original bug report (with sample project) that we've filed before issue tracking was moved to Github, if it helps:

https://developers.facebook.com/bugs/404027086449063/

[jf367]

Any updates on this one? It seems to still happen and it's been more than a year now since the original bug report. Thanks!

[TomWFox]

Closing this as no one has reported this issue recently, and we don't have the resources to investigate these historic reports.

Please ask me to reopen if you experience this issue in the latest version of this SDK.

[benpackard]

@TomWFox @mtrezza What would it take to get this one reopened? I believe the issue remains. I am happy to create a demo project on the latest SDKs, but need to be able to log in/out to demonstrate the issue. I don't think I can set up a new Parse Server for this.

I spent a few hours researching similar issues and stepping through the iOS SDK but I couldn't get to the bottom of it. In short, once you set up Keychain sharing and App groups correctly, the extension can access the logged in user, but if the user changes in the main app the extension still has access to the previous state. (Fetches fail, correct, since the token isn't valid.)

[mtrezza]

If you can reproduce the issue with the latest version of the SDK, I suggest you open a new issue (the template asks for more info) and reference this issue. If you could try to reproduce the issue with a failing test, that would be the best, otherwise you could link to a demo project with instructions on how to reproduce the issue. I am not sure how chances are that someone from the community will take a look at this, as this ObjC SDK is somewhat superseded by the Swift SDK.

[benpackard]

@mtrezza Thanks, will do.

[benpackard]

@mtrezza I created a new issue with a test project at #1648 - please let me know over there if I missed anything. Thanks.