Fundamental problem with Ant.BurstPayload on SDKs at or after 4.1.6

Barney over 2 years ago

The "GenericChannelBurst" sample doesn't work in any of the SDKs at or above 4.1.6.

Error in example is on this line:

var burst = new Ant.BurstPayload();

Error is:

Error: Symbol Not Found

Error Details: Failed invoking <symbol>

I suspect the problem is due to the Ant.BurstPayload.size property being made private in SDK 4.1.6.

If so this would prevent ANT burst from working at all in CIQ. I have searched extensively but there is very little information on it, so perhaps there are very few people using it?

Is this a known problem?

jim_m_58 over 2 years ago

Starting with the 4.1.6 SDK, type checking is on by default. Are you sure that's not confusing things?

Use the current SDK (6.2.2) and add

project.typecheck=0

to the monkey.jungle of your project to turn off type checking. What happens then?

Barney over 2 years ago in reply to jim_m_58

Hi Jim,

Thank you for the quick response!

I tried this and it doesn't change anything. In fact I had already turned type checking off in the compiler options.

You can see for yourself just by running the GenericChannelBurst example, and then pressing the menu button.

Any other suggestions much appreciated!

Thank you

flowstate over 2 years ago in reply to Barney

Sounds like a clear-cut bug to me. Does this also happen on a real device? Either way, I would suggest posting in the CIQ Bug Reports forum.

Also, as type checking is strictly a compile-time thing, it shouldn't be possible to turn on type checking and see additional errors at run time. Conversely, turning off type checking shouldn't remove any run-time errors either. Although ofc, turning off type checking may allow your project to compile in cases when it otherwise wouldn't. (If you turn off type checking, you may see run-time type errors which would've otherwise been caught by the type checker, of course.)

jim_m_58 over 2 years ago in reply to Barney

Do a bug report and specifically note that this can be reproduced with the GenericChannelBurst sample from with the 6.2.2 SDK, as that means it's really easy for Garmin to see the bug.

Barney over 2 years ago in reply to flowstate

Thank you.

Previously Ihad not checked on the actual device, and now I have done it turns out it is a problem specific to the simulator. On the device it works fine, so good news there. Just a pain to debug!

Thank you

Barney over 2 years ago in reply to jim_m_58

Will do. Thank you.