bug: venusqm CIQ version isn't updated

Again:

1) The CIQ team agrees with us that it would be beneficial to allow building with older devices files / older SDKs, so hopefully they will eventually distribute old device files

2) The CIQ team also says you shouldn't edit device files files by hand because the device could crash and I gave an EXAMPLE which again has nothing to do with these theories that you mentioned:

"it means new firmware can have not only API but also duplicated api (for app built the older SDK and the newest). Or upgrading of firmware upgrading installed app to the newest CIQ."

My point is that I don't think these theories ^ are true at all.

My point isn't that my example is meaningful to you, but that's it's an explanation for why the device could crash due to editing device files by hand which has nothing to do with those theories.

Even long before this exact discussion, I had guessed that if you change firmwareVersion in compiler.json, you also have to know the correct connectIqVersion to use.

And whenever you talk about editing compiler.json, you never say where you get the old firmwareVersion / connectIqVersion from.

If you just change firmwareVersion / connectIqVersion "randomly" (I'm not saying this is what you do, but anybody could do it, right), then that's where a crash could occur.

If you get those values from an old backup copy of compiler.json then that's ok - I think. If you have a backup copy of the device files it might even be safer to replace the entire folder with the backup. Who knows what else in that folder needs to be rolled back?

3) "There is no reason to limit device by firmware"

You said this multiple times and I can't help you with that. I can only guess that the CIQ team wants to give devs a way to force users to upgrade (as I said) and this is how they chose to do it (whether we agree with it or not).

Your problem should be partially solved if and when Garmin allows old devices files to used.

- with old device files, at least the user is only forced to have older firmware

- with old device files, at least you can build

4) "I don't use type check"

I don't think I said anything about type check at all. I searched all the comment for the word "type" and only your more recent comment (and this comment) have that word at all.

5) "I don't use compile has check"

But others might. What if compile-time has checks are used by default (with default optimization settings / default compiler options)? After all "--disable-api-has-check-removal" was added as an option for a reason, because many people complained about compile-time has checks. They didn't necessarily opt-in to compile-time has checks nor were they necessarily aware compile-time has checks happen in the first place (which comes up in the forums *all* the time).

This stuff isn't about any one dev or group of devs.

Again:

1) The CIQ team agrees with us that it would be beneficial to allow building with older devices files / older SDKs, so hopefully they will eventually distribute old device files

2) The CIQ team also says you shouldn't edit device files files by hand because the device could crash and I gave an EXAMPLE which again has nothing to do with these theories that you mentioned:

"it means new firmware can have not only API but also duplicated api (for app built the older SDK and the newest). Or upgrading of firmware upgrading installed app to the newest CIQ."

My point is that I don't think these theories ^ are true at all.

My point isn't that my example is meaningful to you, but that's it's an explanation for why the device could crash due to editing device files by hand which has nothing to do with those theories.

Even long before this exact discussion, I had guessed that if you change firmwareVersion in compiler.json, you also have to know the correct connectIqVersion to use.

And whenever you talk about editing compiler.json, you never say where you get the old firmwareVersion / connectIqVersion from.

If you just change firmwareVersion / connectIqVersion "randomly" (I'm not saying this is what you do, but anybody could do it, right), then that's where a crash could occur.

If you get those values from an old backup copy of compiler.json then that's ok - I think. If you have a backup copy of the device files it might even be safer to replace the entire folder with the backup. Who knows what else in that folder needs to be rolled back?

3) "There is no reason to limit device by firmware"

You said this multiple times and I can't help you with that. I can only guess that the CIQ team wants to give devs a way to force users to upgrade (as I said) and this is how they chose to do it (whether we agree with it or not).

Your problem should be partially solved if and when Garmin allows old devices files to used.

- with old device files, at least the user is only forced to have older firmware

- with old device files, at least you can build

4) "I don't use type check"

I don't think I said anything about type check at all. I searched all the comment for the word "type" and only your more recent comment (and this comment) have that word at all.

5) "I don't use compile has check"

But others might. What if compile-time has checks are used by default (with default optimization settings / default compiler options)? After all "--disable-api-has-check-removal" was added as an option for a reason, because many people complained about compile-time has checks. They didn't necessarily opt-in to compile-time has checks nor were they necessarily aware compile-time has checks happen in the first place (which comes up in the forums *all* the time).

This stuff isn't about any one dev or group of devs.