FLIR One Developer / Blog / Topics / crash / iOS crash

iOS crash


This topic contains 5 replies, has 5 voices, and was last updated by Profile photo of stlasin stlasin 2 years, 5 months ago.

Viewing 6 posts - 1 through 6 (of 6 total)

  • Author


  • #3423

    Profile photo of Steve Petersen
    Steve Petersen


    I am getting the following crash on SDK v0.2.10, iOS 9.0.2, and the SLED, on the first attempt to connect to the device after starting my application. Is anyone else seeing this?

    Exception Type: SIGABRT
    Exception Codes: #0 at 0x33648df0
    Crashed Thread: 0

    Application Specific Information:
    *** Terminating app due to uncaught exception ‘NSInvalidArgumentException’, reason: ‘*** -[__NSArrayM insertObject:atIndex:]: object cannot be nil’

    Last Exception Backtrace:
    0 CoreFoundation 0x2469efef <redacted> + 126
    1 libobjc.A.dylib 0x32fccc8b objc_exception_throw + 38
    2 CoreFoundation 0x245b8efb -[__NSArrayM insertObject:atIndex:] + 638
    3 <redacted> 0x0023a4ad -[RosebudAdapter(FPGA) switchToNewFramebufferSize] + 452
    4 Foundation 0x253de5cf <redacted> + 386
    5 CoreFoundation 0x24664faf <redacted> + 14
    6 CoreFoundation 0x246643bf <redacted> + 218
    7 CoreFoundation 0x24662a25 <redacted> + 772
    8 CoreFoundation 0x245af201 CFRunLoopRunSpecific + 476
    9 CoreFoundation 0x245af013 CFRunLoopRunInMode + 106
    10 GraphicsServices 0x2c040201 GSEventRunModal + 136
    11 UIKit 0x27d7ba09 UIApplicationMain + 1440
    12 <redacted> 0x0002f591 main + 108
    13 libdyld.dylib 0x3357eaaf <redacted> + 2


    This is how the FLIROneSDK handles different FLIROne devices being connected
    if you connect a new FLIROne then it will crash the first time that your app is opened but works after that
    if you then connect one of the old FLIROnes then it will crash the first time but work after that
    if you later reconnect one of the new FLIROnes then it will crash the first time the app is opened but work after that

    this exception is uncatchable since the method is dispatched to the main thread from one of the 20+ threads that the FLIROneSDK starts



    w.r.t. the actual exception that is thrown, calling [NSMutableArray addObject:nil] is just an easy way to crash the app and force the user to go back to the springboard and restart your application
    there is no actual bug here


    Profile photo of renato


    @Intellectual Juggernaut, good observation. Thanks!


    Profile photo of pablo pusiol
    pablo pusiol


    I’m having the same problem. It is a bug!, i’m doing the same thing with official FLIR apps and those apps do not crash. Is there a workaround?



    Profile photo of stlasin


    Apple will undoubtedly fix this problem quickly through an iOS update, but as people wake up on December 2 in the United States and other countries throughout the world, there’s likely to be quite a lot of confusion when devices begin inexplicably respringing over and over again.

    If you’re experiencing continual crashing, the first thing to try is disabling notifications for apps that send regular reminders. It can, however, be difficult to tell which apps are responsible, so a secondary solution is to set the date on your iPhone to before December 2 as you await a fix from Apple.
    If you are still facing the issue, delete the external profiles like Appvn iOS download.

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.