PSA: 10.xx Beta firmware CIQ Position bug

Hey all,

I'd like to bring your attention to a CIQ GPS/Positioning bug in the 10.xx Alpha/Beta releases (10.42 right now). While it is under investigation by Garmin (I reported from the 10.33 alpha but was overlooked until 10.39 Beta report by user), I don't know whether it will be fixed by final release: forums.garmin.com/.../bug-apps-with-gps-crashes-at-start-10-39-epix2

Basically if you're trying to set any GPS :constellations or :configuration the app will crash when you invoke Position.enableLocationEvents. Garmin's own code snippet also crashes. This means that only "GPS Only" works (no Galileo, etc.)

So if you have any app that tries to set :constellations or :configuration you may want to have a version ready that doesn't do that and be ready to push it, should Garmin decide to release the firmware without fixing the bug.

Top Replies

FlowState over 1 year ago in reply to jim_m_58 +1

jim_m_58 said:
Notice the difference between "CONSTELLATION_*" (3.2.0)

and "CONFIGURATION_*" (3.3.6)

Use what I posted to determine System 5 (or System 6)

Go back and read what I said…
sabeard over 1 year ago in reply to jim_m_58 +1

Jim, FlowState is correct in this based on my reading of the 4.2 SDK docs.

System 4 = 3.2.x & 4.0.x

System 5 = 3.3.x & 4.1.x

System 6 = 3.4.x & 4.2.x

Anything feature that came in 3.3.6 is…
sabeard over 1 year ago in reply to jim_m_58 +1

So my statement about the Positioning features and the supported hardware was before I downloaded an looked at the Instinct Crossover. It is indeed a CIQ 3.3.x device with the same GPS as the F7. So it…

All Replies

FlowState over 1 year ago in reply to flocsy

flocsy said:
For this reason I am trying to get this documented for a long time: https://forums.garmin.com/developer/connect-iq/i/bug-reports/improve-documentation-add-api-levels-and-system-levels-to-device-reference

Thanks for this feature request. Upvoted!

FlowState over 1 year ago in reply to Travis.ConnectIQ

Travis.ConnectIQ said:
System 6 is ConnectIQ versions 3.4.0 and 4.2.0. In some cases, we push features in earlier than that. i.e., the Position.CONFIGURATION_* stuff was made available for API version 3.3.6.

It isn't ideal for us to do this, but we sometimes break our own rules.

Normally, the right thing to do here is to use has checks to determine if the device has support for a feature or not. I haven't looked at the actual bug reported in the OP, but if it is broken as described there, I don't see that the has check would have avoided this particular problem.

Thank you!

Cuiv over 1 year ago in reply to Travis.ConnectIQ

OP here, about the last paragraph - correct, the has check doesn't avoid this particular issue!