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
Hi, I just updated to 2.5 and I'm really excited with the new features :)
Before the update I was using a modified version in which I surrounded some methods with a try/catch to avoid crashes in the testers devices because of the API changing constantly. Now I was thinking of use the new version to accomplish the same purpose, but I encountered a problem with an assertion.
This Asserts on line 252: AssertTrueOrReturn([key isKindOfClass:NSNumber.class]); inside the enumeration block.
The problem is natural. I'm giving an array to the mapper when it expects a dictionary. The crash is absolutely normal but with the new feature I was hoping that this won't happen anymore.
If this is the desired behaviour there is no problem ;)
The text was updated successfully, but these errors were encountered:
Hi, thanks for checking out new version :).
Can you try to compile in KZPM as Release? It should not fire assert and should not crash.
I thought it might be useful to know when JSON is different then expected while you developing.
I agree with @marek, asserts are for catching problems in debug builds, if you strip asserts (as release does by default) this will not crash, it will just ignore that mapping.
Hi, I just updated to 2.5 and I'm really excited with the new features :)
Before the update I was using a modified version in which I surrounded some methods with a try/catch to avoid crashes in the testers devices because of the API changing constantly. Now I was thinking of use the new version to accomplish the same purpose, but I encountered a problem with an assertion.
JSON I expect:
Mapping:
JSON I'm reciving:
This Asserts on line 252:
AssertTrueOrReturn([key isKindOfClass:NSNumber.class]);
inside the enumeration block.The problem is natural. I'm giving an array to the mapper when it expects a dictionary. The crash is absolutely normal but with the new feature I was hoping that this won't happen anymore.
If this is the desired behaviour there is no problem ;)
The text was updated successfully, but these errors were encountered: