Since yesterday, my app crashes and, after some debug, I found that the problem is in this code
// Update user
[backendless.userService update:backendless.userService.currentUser response:^(BackendlessUser *updated) {
Do something
} error:^(Fault *fault) {
Fault
}];
The console shows me this error
“[NSDictionary initWithDictionary:copyItems:]: dictionary argument is not an NSDictionary’”
The app doesn’t enter into the block and the fault isn’t never called but crashes and shows me the above error.
(I have the latest SDK installed)
I don’t know what is the problem, could you help me?
Same problem with this error message:
-[BackendlessUser allKeys]: unrecognized selector sent to instance 0x1410c3710
2016-04-28 17:23:53.944 Delicac[1465:441291] *** Terminating app due to uncaught exception ‘NSInvalidArgumentException’, reason: ‘-[BackendlessUser allKeys]: unrecognized selector sent to instance 0x1410c3710’
This is a disaster, I had to pull my product of the market (which is obviously costing).
Ideas? Quick fix needed as there is nothing we can do on our side.
Our app is now crashing as well. This is not good, any help will be appreciated.
Marco, when was your product published? Trying to determine which build you’re using.
Rick,
What version of the library are you using?
Mark
see other message, I’ve been using backendless for about 2 months I believe
Not sure at the moment, but it is a static lib in Xcode, dated 3/24/16. We are beta testing this version in TestFlight.
My static library is dated 2/22/16
The user gets created but does not get updated (in case this helps). Also updates of other objects seem to go fine, but not the user (which is a big deal because the app crashes at registration and therefore doesn’t really make a good impression… + I loose the data entered as it is never pushed due to the update failure)
I was able to reproduce the problem. We’re working on a solution for this.
The problem has been resolved. I apologize for the inconvenience this has caused you.
Thank you for the quick fix!
We seem to be running stable again, too. Thanks!
Yes, it works good now. Thanks