getting a lot of crashes with Backendless iOS SDK 3.0.22

app ID D12401BA-C118-2CC9-FF7D-A4B0700D0600

from the beginning, I get a few crashes with my iOS app using Backendless, mostly in HttpEngine.m.
I kept on updating the iOS Backendless SDK each time I publish a new release, for instance the actual version is using the SDK version 3.0.22, but the crash problem is getting worst now.

I have several hundreds of crashes in Crashlytics referenced as following:

HttpEngine.m line 264
-[HttpEngine processAsyncAMFResponse:]

Fatal Exception: NSInvalidArgumentException
-[BSMutableSettings dsId]: unrecognized selector sent to instance 0x12c5b0120
-[BodyHolderFactory dsId]: unrecognized selector sent to instance 0x15d85760
-[__NSCFType dsId]: unrecognized selector sent to instance 0x165d1e50
-[__NSArrayI dsId]: unrecognized selector sent to instance 0x155d5540

Also getting several dozains of crashes with those references:
BackendlessCache.m line 355
-[BackendlessCache invokeAsync:method:args:responder:]

Fatal Exception: NSRangeException
*** -[__NSArray0 objectAtIndex:]: index 3 beyond bounds for empty NSArray

I’m going to run a big test session in debug mode to try and understand if there’s a pattern which lead to those crashes.
If you have any information on your side that could help, I’m all ears :slight_smile:

Thank you for your help,
loïc b.


Described errors require debugging of your application.
According to our Support Policy we can not debug/troubleshoot your code.

Hi Kate, thank you for your message.

Maybe there’s a misunderstanding : The files referenced in the crashes are not my code, they come from the Backendless SDK. So it’s not about debugging my app, which I understand is not possible, it’s more about understanding how the Backendless SDK can crash : maybe the crash report can give you a hint about what’s happening.

The crash report itself doesn’t give us enough information, we need the exact steps to reproduce your issue. So if you could prepare a minimal self-contained sample, which would reproduce the error, then we might help you.