Acknowledged
4 months ago

bug: venusqm CIQ version isn't updated

On a physical venusqm the API level is 3.3.6, but in compiler.json it's only 3.3.1 and here: https://developer.garmin.com/connect-iq/compatible-devices/ it's only 3.3.0

flocsy🤠
Parents
  • 4 months ago

    1. I don't use compile check has

    2. I don't use type check

    3. I have to use the newer SDK because I'm forced to do it just because they don't support the newest devices (not firmware) and e.g. 7.4.3 can't build for fenix123

    I have written my apps for devices and minSDK pointed in manifest and expect all the tools will respect my settings, settings which are prepared just for it - selecting the device I want to support...

    So modify jsons is only forcing sdk to fulfilled my expectation. If it's danger it means SDK is not designed correctly.

    There is no any information in doc connected with firmware version. Let see...

    Notification message types

    Since:

    API Level 5.1.0

    I don't want to use notification, so why sdk 8.1 remove all fenix7 below 20.x? Just because they don't support 5.1.0? I don't need it! And for older firmware I can use has to check if I can send notification.... The new function have the new id. Can you tell that in the new firmware the id of the function are overwritten?

    There is no reason to limit device by firmware on condition developer knows what to do but if don't ERA give that knowledge. 

    For me the problem is quality, new sdk, new bugs, memory, testing the same code with the new sdk...My apps are free but for people earning money less potential users means less potential money. 

Comment
  • 4 months ago

    1. I don't use compile check has

    2. I don't use type check

    3. I have to use the newer SDK because I'm forced to do it just because they don't support the newest devices (not firmware) and e.g. 7.4.3 can't build for fenix123

    I have written my apps for devices and minSDK pointed in manifest and expect all the tools will respect my settings, settings which are prepared just for it - selecting the device I want to support...

    So modify jsons is only forcing sdk to fulfilled my expectation. If it's danger it means SDK is not designed correctly.

    There is no any information in doc connected with firmware version. Let see...

    Notification message types

    Since:

    API Level 5.1.0

    I don't want to use notification, so why sdk 8.1 remove all fenix7 below 20.x? Just because they don't support 5.1.0? I don't need it! And for older firmware I can use has to check if I can send notification.... The new function have the new id. Can you tell that in the new firmware the id of the function are overwritten?

    There is no reason to limit device by firmware on condition developer knows what to do but if don't ERA give that knowledge. 

    For me the problem is quality, new sdk, new bugs, memory, testing the same code with the new sdk...My apps are free but for people earning money less potential users means less potential money. 

Children
No Data