IQ crash on S60 but works in the simulator - troubleshooting recommendations?

My first app just got approved and released on Friday, WUradar Widget. Today I started getting some questions and one report of CIQ crash every time the widget is opened. The report is from S60 user using GCM-IOS version 3.22.

My development environment set up is:
Windows 7
eclipse 4.70
CIQ SDK 2.3.4

The user was able to send me the CIQ_LOG.TXT file and this is what I see.

ERROR: Invalid Value
DETAILS: failed inside handle_image_callback
STORE_ID: 9c692f2757d6448891ae5dd846a4ad26
CALLSTACK:

ERROR: Invalid Value
DETAILS: failed inside handle_image_callback
STORE_ID: 9c692f2757d6448891ae5dd846a4ad26
CALLSTACK:

Given the statement about image callback, I suspect this has something to do with the use of makeImageRequest method. I am at a loss on how to reproduce the issue to troubleshoot as I don't have neither a S60 nor an IOS device to confirm the results.

Any suggestions on where to start the troubleshooting?

sabeard over 8 years ago

As a step in troubleshooting, I did have the user power down and back on their S60. It does not appear that had an effect on the crash.

peterdedecker over 8 years ago

First step would be to create a debug build and have the user sideload that one it ll give you an exact line where it goes wrong

Next if it is indeed the function you think it is create a small test app and have the user verify the small test app also crashes. Then post it in the bug forum in the desired bug format - see sticky

Cheers
Peter

sabeard over 8 years ago

Peter,

Thanks for the feedback and recommended next steps. I will start with the debug build and see how it goes.

I guess for the debug build I need to do the side load and create the txt file to go in the garmin/apps/logs folder. Then get the copy of the log file to see what is going on.

peterdedecker over 8 years ago

That might also provide extra info. But the info in the ciq_log.txt will also be more verbose with a debug build.

Former Member over 8 years ago

peterdedecker is correct. You should be provided the line number of the error with the debug build in the CIQ_LOG.txt.

Thanks,
-Coleman

sabeard over 8 years ago

All, thanks for the recommendations and to Brandon.ConnectIQ for the assistance in troubleshooting. After some further troubleshooting with the user experiencing the crash, it turns out they had entered a DarkSky API key instead of a Weather Underground key. The first time it appears to have crashed the app, later it stuck on the getting image page which highlighted a improper/missing key. I know where my work is for version 1.3, better error checking on the URL. ;)

Former Member over 8 years ago

Great to hear that we were able to figure it out!

Thanks!
-Coleman