app deployed not working how to debug

In the log of my Watch, I have :

[HTML]
ERROR: Too Many Arguments Error
DETAILS: Failed invoking <symbol>
STORE_ID: c5242975c9874c2b844f379879fbc880
CALLSTACK:
@PC = 0x00000000

[/HTML]

But this means nothing for me ...

I try to add :

function initialize()
{
AppBase.initialize();
}


as this was suggested in this topic , but this changes nothing...

The too many arguments should be launch when a method have more than 10 arguments, but I don't have such a method, and this is difficult to test,because this happens only on the deployed version : I need to try changes, deployed (there is then a lot of version deployed), and for the moment see that this didn't work

Have you looked at this thread? https://forums.garmin.com/showthread.php?358985-Too-Many-Arguments-Error

A common problem was not having a parameter specified for onStart() and onStop() (they should be onStart(state) and onStop(state) )

Many thanks Jim,

that was it ... with the onStart(state) and the onStop(state), this works :)

One other thing you can do to better troubleshoot issues like this is use the Build For Device Wizard in Eclipse and make sure that 'Build release version of project' is unchecked, then side-load the app to a device to test. This will include the PC-to-line number table and print out a more useful call stack to the CIQ_LOG file. Instead of @PC = 0x00000000 you'll actually see file names and line numbers where the errors are occurring. We strip this information our of apps packaged for the store to cut down on the file size.

Another thing I found is that in the simulator, for target that can still be running on 1.2, try it with 1.3/2.x and that may catch these things in the sim (I found this when looking into a "too many arguments" error that happened on the watch - in the sim I was testing for 1.2, and it wan't caught as it wasn't enforced in 1.2, but when I used 1.3, it was...

ok thanks Brandon and Jim, I'll follow your advice for the next deployments.

Rgds

One other thing you can do to better troubleshoot issues like this is use the Build For Device Wizard in Eclipse and make sure that 'Build release version of project' is unchecked, then side-load the app to a device to test. This will include the PC-to-line number table and print out a more useful call stack to the CIQ_LOG file. Instead of @PC = 0x00000000 you'll actually see file names and line numbers where the errors are occurring. We strip this information our of apps packaged for the store to cut down on the file size.

I try to do it, but I didn't see anything as 'Build release version of project' , is that because I'm on mac ?

Does it exists a way to deploy in my Watch, without the usb cable (in GC app), but this will be deployed only for me and not for the others ?

In "Build for Device" the checkbox for "Build release version" is on the very bottom of the dialog box, and on my Windows machine, you need to scroll down in the dialog box to see it. Make sure you scroll down.

As you can see in my screenshot, it seems that I didn't have the checkbox.

But with this checkbox unchecked, you can upload in GC without releasing for others ?