I have only troubleshooting tips.
The problem is the third line of StackTrace:
2 CoreFoundation 0x007ee3a1 - [__ NSArrayM insertObject: atIndex :] + 881
Obviously you are adding an element, and the libobjc.A.dylib thing is cloning itself:
1 libobjc.A.dylib 0x087ffe02 objc_exception_throw + 50 2
To diagnose the root cause, you need the classic ASP troubleshooting methodology. Debug.Print applications are everywhere!
You literally have to look for your code for where you add items to the collection. And this somewhere will probably be in the call to instantiateViewControllerWithIdentifier .
Since an exception is thrown before you can execute the code , the only option (other than debugging a memory dump) is to comment or Debug.Print all calls to narrow down the problem! In sequence: (
Its such a PITA and I sympathize with you . I believe that due to adding a null object in accordance with the error message, the object cannot be nil
It could be anything, but adding zero is probably a symptom of another problem. Maybe the element you are adding is too big, maybe it exceeds the bounds of the array, maybe you just need to clear the solution and redistribute it.
Perhaps trying to include exceptions may help if you can UIApplication.Main (args, null, "AppDelegate"); e.g. fooobar.com/questions/830914 / ...
Jeremy thompson
source share