Failed invoking symbol Error on Edge but not on watches

Hi,

A couple of people are having trouble with an app that I developed on their Edge 520 or 820 computers. The app works on a Fenix and a Vivoactive and on several other watches. I've been sent the error from the CIQ_LOG file but it isn't very helpful when it comes to finding the line of code with the problem:

ERROR: Symbol Not Found Error
DETAILS: Failed invoking <symbol>
STORE_ID: c692286155644fefb88453cxxxxxxx
CALLSTACK:
@PC = 0x00000000

I think I've had this type of error when something is null or unassigned that shouldn't be. But how do I go about working out what the real error is on a device that I don't have? It works on the simulator on most device types and my watch. I've had this kind of error before when trying to assign a null value to a label and probably a few other ways on my own watch. I've then had a lot of pain stepping through code on an app sideloaded to my own watch to isolate the problem. The trouble is that it isn't an issue on my watch, but it is on another device and the error message is really uninformative, to me.

Any thoughts on how to solve this would be appreciated.

Thanks,

R.

jim_m_58 over 8 years ago

One thing you can try is running your app for a 520 target in the sim with the 2.2.0 beta SDK. It's got a new feature where the calls available are based on the target and might point you right to it.

Here are a couple things you might want to look into:

If you are trying to use VibeProfile, that will case the error, as there's no vibrate on these devices
If you are using anything from ActivityMonitor, that will too - The Edge devices don't have step tracking, etc....

Phimby over 8 years ago

Thank you.

Thank you, Jim, for the swift and perfect reply. I had a double whammy of VibeProfile and ActivityMonitor.

For anyone who sees this post and has the same head-scratcher. I wrapped where I did VibeProfile things in

if (Attn has :VibeProfile) {
// I'm pickin' up good vibrations
}

Where Attn is what I called Attention in the using statement at the top of the module.

R.

One thing you can try is running your app for a 520 target in the sim with the 2.2.0 beta SDK. It's got a new feature where the calls available are based on the target and might point you right to it.

Here are a couple things you might want to look into:

If you are trying to use VibeProfile, that will case the error, as there's no vibrate on these devices
If you are using anything from ActivityMonitor, that will too - The Edge devices don't have step tracking, etc....