parse-community
ParseReact with Parse 1.6.0 and react-native
Hi, Parse 1.6.0 has more changes than I expected so I will go back to 1.5.0, but I am just posting the errors I ran into.
- StubParse does not require('parse/react-native')
- LocalSubscription and Channel do not use Parse.User.currentAsync
- ParseUser fromJSON didn't have a classname
- provider was undefined in ParseUser provider.restoreAuthentication probably because there is no way to init Parse.FacebookUtils
Thank you. We've been actively working on getting an update to Parse+React today to follow up on these changes.
1.6 is supported in version 0.5.0 of Parse+React. Let me know if you encounter any issues!
@ecesena Can you be more specific about the issue in 4? I've run it against our FB Login integration tests and it seems to be fine, but because using fb login on React Native current hooks into "private" methods, you may be doing something different than our tests. (we're currently working on publicizing this hook, and improving the way auth providers are registered)
@bobintornado are you using require('parse-react/react-native')?
I'll test and send more details tonight, however I got the same error message also with normal user+pass login (i.e. not fb). For FB, I'm using FBDSK now.
@ecesena I think it may happen when you have Parse Users with FB auth data, but the application isn't registered to use the FB Auth Provider. I have a fix coming in 1.6.2 of the JS SDK.
@andrewimm tried removing auth data from a user, used username+password login, but it still errors. I'll wait for 1.6.2 then. BTW is there a way to monitor for js releases? You don't have a public repo that I can watch, do you? Thanks!
@ecesena Very odd. In this case, I'd love to know more about this specific error. Version numbers and stack traces will help a lot -- if you can build a reproducible case that fails, that's the ideal scenario. That's what we do for the open source SDKs, and I plan to move to that method of bug triage once we open the JS SDK later this week. Keep an eye on blog.parse.com or the ParsePlatform Github Org for when that happens.
@thewizster Can you be more specific about your issue? I appreciate the feedback, but I can't do anything without knowing any version numbers. Pulling old users from disk should be fixed in 1.6.1, but I'd like to know if I overlooked something.
Errors 1-3 are not an issue for me anymore. I am only running into error 4 using [email protected] and [email protected].
In parseuser.js authproviders is {} causing provider = authproviders[facebook] to be undefined
We need a way to call registerauthenticationprovider since using facebookutils.init isnt an option right?
@ethandt92 I just released 1.6.2 on npm. Among other things, it adds a clause that will skip synchronization of an unknown auth provider, so this error should no longer occur.
@andrewimm Is /lib/react-native/Parse.js (actually the whole react-native) missing from the 1.6.2 dist?
Ah crap, you're right. I'll have to figure out how that happened -- our publish script first runs the build script for all 3 releases. Well, onto 1.6.3!
Awesome! This seems to fix, my app is back up & running with react-native 0.11 and parse 1.6.3.
Fantastic to hear. I'll leave this task open for another day or so before closing out.
Hi, I have similar problems with Parse.FacebookUtils.logIn using Parse 1.6.3 and parse-react 0.5.0
Could you look at it?
