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

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?

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

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.)

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.

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