4.2 Beta 1 sdk build errors

So I have a Dictionary that I'm accessing with strings like an array:

For example: response["weather"]["error"]
This works great for the old compiler, but gives this when trying it with the 4.2 beta sdk:

Invalid '$.Toybox.Lang.String' passed as container index of type '$.Toybox.Lang.Number'

Is this something that should be fixed by Garmin? Or should I fix it on my end somehow? Although that could be a rough rework as the data is coming from an API.

Top Replies

jim_m_58 over 2 years ago +1

The beta SDK has type checking on by default (like the earlier Compiler 2 betas)

What you are seeing is from type checking. To verify, you can turn off type checking with a complier flag, but the goal…

All Replies

0 MobileDriveway over 2 years ago

MARQ (Gen 2) Athlete / Adventurer simulator is broken - stretches the screen like this:

That is NOT caused by the app - you can see System fonts stretched there.

MARQ (Gen 2) Aviator works fine, even though it gave me a "can't load" error in the beginning.

0 jim_m_58 over 2 years ago in reply to MobileDriveway

As far as the Marq2 and the sim, there's bug report it.

forums.garmin.com/.../marq2-sim-works-bad

0 jim_m_58 over 2 years ago

The beta SDK has type checking on by default (like the earlier Compiler 2 betas)

What you are seeing is from type checking. To verify, you can turn off type checking with a complier flag, but the goal is to have you move to type checking.

Use -l 0 to turn it off.

0 Kyle.ConnectIQ over 2 years ago in reply to MobileDriveway

MobileDriveway said:
MARQ (Gen 2) Athlete / Adventurer simulator is broken - stretches the screen

This is now fixed. Download the Marq 2 from the SDK Manager to get the update.

0 VAW.BE over 2 years ago in reply to jim_m_58

Thanks Jim, didn't expect it to turn on automatically. Changing it to 'off' works. I would love to use types, but thing like this make it a pain rather than a help. So I just hope (and many with me), that it will always be possible to keep it 'off'.

0 flocsy🤠 over 2 years ago in reply to VAW.BE

Indeed it takes time to get used to it and adjust the existing code, but I would strongly advise to keep the type checking. It might take some time to get it work but it might just as well save you much more time because you won't need to debug strange bugs that could be avoided because you fixed the types in advance.

0 jim_m_58 over 2 years ago in reply to flocsy🤠

It kind of depends on how many apps you have. I have about 50 published and another 100-150 test or beta apps.

Many of my apps have been stable for years.

If you only have a couple apps, it might not take that much to conform to monkey types, but what about 50, where in some cases you really haven't looked at the code much in years?

Alpha Money mentioned in one of the Q&As at the GDVC, that the ability to control the level of type checking on a project level was coming. With that, I can use type checking for new stuff and not mess with my stable apps.