Hello dear support team!
I am a developer of the iOS app which uses Backendless
The reason I am writing is that I faced with the issue during the development
I have 1 table in my Backendless and now I am getting crashes during the work with this table. When I try to save the object I get this crash with the reason - "[<NSConcreteValue *> valueForUndefinedKey:]: this class is not key value “coding-compliant for the key objCType”
It does not matter is the object recently created or retrieved from the table and saved again - I get this crash
I was thinking that the issue may be in the inconsistency of data between the table and the class that describes that table in the app. After checking the fields and making them consistent the crash is still happening.
Also the Backendless is acting weird on this table when I try to set new objects with relations to other tables. The pop-up with the error of duplicate fields appears and it is said that the relation is failed to set, but, after the updating of the table the new relations appear in the table’s schema. After this the real tables data begin not to appear and Backendless says that something went wrong and the new crash ticket is created. After the removal of that fields, the data begin to appear again. So. I’d assume that there is a problem with this table and its relations to other tables.
I use Backendless v5.1.0 at the moment (I’ve made a migration from v4.0.17 to 5.1.0, but this did not solve the crash)
Could you please advice how to solve the crash and this weird behavior. Thank you