Push crashes iOS app with incorrect "custom" payload

Solar2D Network
#1

Hello,

When receiving a push message on an iOS (os v. 7) device, if the “custom” payload is not formatted properly, the app will crash when opening after touching the push message alert.  It would seem like a catch of some type should be implemented for this issue.

Apr 8 10:39:04 develephants-iPod SpringBoard[33] \<Warning\>: LICreateIconForImage passed NULL CGImageRef image Apr 8 10:39:04 develephants-iPod pushy[2329] \<Error\>: -[\_\_NSCFString count]: unrecognized selector sent to instance 0x1558cd50 Apr 8 10:39:04 develephants-iPod pushy[2329] \<Error\>: \*\*\* Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[\_\_NSCFString count]: unrecognized selector sent to instance 0x1558cd50' \*\*\* First throw call stack: (0x2e661fd3 0x38daaccf 0x2e665967 0x2e664253 0x2e5b37f8 0x8f51b 0xaf889 0x10d11f 0x125971 0x95bd7 0x3108441d 0x31084237 0x30e83085 0x30e82871 0x30ee6cc9 0x334b8aed 0x334b86d7 0x2e62cab7 0x2e62ca53 0x2e62b227 0x2e595f4f 0x2e595d33 0x334b7663 0x30ee116d 0x8857f 0x88538) Apr 8 10:39:04 develephants-iPod ReportCrash[2412] \<Notice\>: ReportCrash acting against PID 2329 Apr 8 10:39:05 develephants-iPod ReportCrash[2412] \<Notice\>: Formulating crash report for process pushy[2329] Apr 8 10:39:05 develephants-iPod com.apple.launchd[1] (UIKitApplication:com.develephant.pushy[0xe03d][2329]) \<Warning\>: (UIKitApplication:com.develephant.pushy[0xe03d]) Job appears to have crashed: Abort trap: 6 Apr 8 10:39:05 develephants-iPod backboardd[28] \<Warning\>: Application 'UIKitApplication:com.develephant.pushy[0xe03d]' exited abnormally with signal 6: Abort trap: 6 Apr 8 10:39:05 develephants-iPod ReportCrash[2412] \<Notice\>: Saved crashreport to /var/mobile/Library/Logs/CrashReporter/pushy\_2014-04-08-103904\_develephants-iPod.ips using uid: 0 gid: 0, synthetic\_euid: 501 egid: 0

Additionally, the format for putting together the “custom” payload does not seem to be consistent between Android and iOS.  The payloads need to be formatted differently to get them to work properly on each OS.  Is that something that can be addressed within Corona?

Let me know if you need any other information.

Cheers.

#2

hello,

I have the same problem :frowning:

#3

Can you file a bug report please?

Thanks

Rob

#4

Rob, it seems like this is the same issue reported on 25 January … http://forums.coronalabs.com/topic/43605-bug-ios-push-messages-custom-data-parsing/?hl=payload#entry241249

I believe a bug report was submitted back then but not sure. Can you kindly confirm?

Also on a related note, FogBugz has a case from a year ago (to the day actually) that looks somewhat related. It looks like that one was closed but its not clear what the resolution was.  Case # 22669 - “iOS Push Notification custom data is expected at the wrong place inside the JSON data” . 

Just wondering if this is all related? Thanks for your help.

#5

22669 is marked as Resolved back around build 1092.

And yes, Kerem, this seems to be the same post that @develephant made in the other forum post.   If he made a bug report, he didn’t post the number back here as a reference and I don’t see one in the database.

#6

Ok. Thanks for clarifying. No bug report = no corrective action since January.

#7

Submitted: #Case 32132 iOS app crashes using custom payload.

#8

Such a great bug report number… 3… 2… 1… go! I bet this one will be fixed sooner than later thanks to having such an awesome number. Great job posting it. Thank you. 

#9

hello,

I have the same problem :frowning:

#10

Can you file a bug report please?

Thanks

Rob

#11

Rob, it seems like this is the same issue reported on 25 January … http://forums.coronalabs.com/topic/43605-bug-ios-push-messages-custom-data-parsing/?hl=payload#entry241249

I believe a bug report was submitted back then but not sure. Can you kindly confirm?

Also on a related note, FogBugz has a case from a year ago (to the day actually) that looks somewhat related. It looks like that one was closed but its not clear what the resolution was.  Case # 22669 - “iOS Push Notification custom data is expected at the wrong place inside the JSON data” . 

Just wondering if this is all related? Thanks for your help.

#12

22669 is marked as Resolved back around build 1092.

And yes, Kerem, this seems to be the same post that @develephant made in the other forum post.   If he made a bug report, he didn’t post the number back here as a reference and I don’t see one in the database.

#13

Ok. Thanks for clarifying. No bug report = no corrective action since January.

#14

Submitted: #Case 32132 iOS app crashes using custom payload.

#15

Such a great bug report number… 3… 2… 1… go! I bet this one will be fixed sooner than later thanks to having such an awesome number. Great job posting it. Thank you.