-
-
Notifications
You must be signed in to change notification settings - Fork 874
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PFDateFormatter dateFromString method Error #830
Comments
The change was in place to mitigate an bug in JavaScript SDK actually, that was encoding dates incorrectly, specifically If you can provide more info on your deployment - that would help tremendously in analyzing on where this issue is coming from. |
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.
|
Sure thing, this is what I am facing from the crash
And when I po the string I get this
|
If you need more info, let me know :) |
The only question that I would have here - where do you get the data from? |
It's coming from the PFUser's |
Parse.com or Self-hosted Parse Server? |
parse.com |
Another one, sorry it's a little bit too many, but I am trying to isolate the issue. |
All good, ask away! We do not use any beforeSave/afterSave hooks. The version of the JS SDK we are using is 1.4.2. |
Updating it right now to 1.6.14. Gonna see if that helps it. |
Updated to 1.6.14, still crashing. |
Sounds pretty sad, there was a bug in JS SDK before 1.6.7 that encoded the So, here is the most important question - what triggered the wrong save of the object in the first place. |
Thanks for your help on this but the problem was occurring on our end. I had read issue #414 awhile back. Checked our system for any occurrences. I overlooked one where someone had been trying to change the updatedAt field and save the object. |
Glad you found it. Let me know if you need any help. |
When I was using Parse pod 1.10.0, I noticed that method dateFromString was commented out and was just returning [NSDate new]. When I updated my Parse podfile to 1.12.0, that method was uncommented out. Now when I log in as a PFUser, kill the app, and open the App I get a crash. The crash error is that a NSDictionary instance is being sent to the method dateFromString. Commenting out dateFromString on pod 1.12.0 resolves the crash.
The text was updated successfully, but these errors were encountered: