0

There are a lot of posts on this 'type' of error 

[__NSCFNumber length]: unrecognized selector sent to instance 0xb000000000c58913

but none of it has bearing on my situation unfortunately.

The reason is our app is crashing on a background thread with the flurry SDK. I can't investigate the stack trace any deeper because I just get machine code.

enter image description here

I've tried commenting every line of code inside my flurry.m file but not of it encapsulates the error because this is happening inside the flurrySDK.

Its always crashing on thread 22 when I resume from background on the function

+[FlurryProtocolData limitStringLength:]

If you have any advice what so ever on how I look at this further I would love to hear it!

Aggressor
  • 13,323
  • 24
  • 103
  • 182
  • NSNumber unrecognized selector length check your [FlurryProtocolData limitStringLength:] – Huy Nghia Mar 05 '15 at 04:47
  • I dont have access to that, its in the SDK – Aggressor Mar 05 '15 at 04:48
  • so check param you sent to [FlurryProtocolData limitStringLength:]? is It right type? – Huy Nghia Mar 05 '15 at 04:50
  • As the above image shows, I don't call it, from 17 to 12, thats all the SDK – Aggressor Mar 05 '15 at 04:51
  • It sounds a lot like the API key that you're sending to the SDK is an `NSNumber` instead of an `NSString`. – Ian MacDonald Mar 05 '15 at 05:15
  • This surely is memory management issue, the memory previous occupied by object supporting "length" API is now occupied by some NSNumber. Try enabling "Enable Zombie Objects" under "Diagnostics" in "Run" for your scheme. – gagarwal Mar 05 '15 at 05:28
  • It looks like you're passing an NSNumber somewhere where you should be passing an NSString. This may be a simple parm error, or it could be a zombie issue. If it's not always an NSNumber then it's probably a zombie thing. – Hot Licks Mar 06 '15 at 03:26

1 Answers1

0

We were passing an ID as one of the session parameters to Flurry.

However it doesn't cause a crash until its loaded from a background thread oddly enough.r

Making sure the ID was a string before passing it fixed the issue.

Aggressor
  • 13,323
  • 24
  • 103
  • 182