You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Well, I suppose it's got something to do with how OCMapper handles it's String parsing, and gets messed up at some point, which makes me think whether I should be concerned with content I try to parse that's been typed by the user, since the output string causing the problem had nothing special in it.
Feel free to remove the topic if you feel offended, I merely wanted to share a negative experience I had, which could help others.
On Oct 15, 2015, at 12:11 PM, Aryan Ghassemi [email protected] wrote:
hmmm what does this have to do with OCMapper?
—
Reply to this email directly or view it on GitHub #40 (comment).
sorry, I missed the part where you said convert object to dictionary :) My bad
for a second I thought you opened a bug in a wrong repo hehe
Will check to see why it's crashing, thanks
For some weird reason, converting an object to a dictionary crashed with the following error:
valueForUndefinedKey:]: this class is not key value coding-compliant for the key stringByRemovingPercentEncoding
if there was a string generated with the following code set to a property in the object
I have now changed to the following solution and it works, funny though:
The text was updated successfully, but these errors were encountered: