• Replies 5 replies
  • Subscribers 18 subscribers
  • Views 101 views
  • Users 0 members are here
Options
Related

Can older SDK be used to compile and publish app? Latest one ruines activity recording.

SzymonP

Hello,
I've just published a bug report for latest SDK which throws error when setting up sport type for selected Fenix5 models BUG: Latest SDK ruins activity recording for selected Fenix5 models. 


1. Has anyone faced this issue?

2. Am I allowed to publish app using one of the previous SDK versions (no issues if I use SDK 8.1.0)?

Thanks

  • SzymonP said:
    2. Am I allowed to publish app using one of the previous SDK versions (no issues if I use SDK 8.1.0)?

    As per an announcement from last year, 8.1.0 should be the minimum SDK for publishing to the store, so you should be fine. Can't guarantee they won't increase that minimum version in the future though.

     Connect IQ SDK 8.2 Now Available 

    Side-Loading to System 8 Devices

    For System 8 devices receiving the 2025 Q2 QMR, any app that is being side-loaded to the device must be built with Connect IQ SDK 7.4.3 or greater. In July, we will be setting the minimum SDK version to 8.1 for uploading apps to the store.

  • in reply to flowstate

    Thanks! I taught they communicated that we are supposed to use only the latest one :) 

    In the end I had to use 8.3.0 which supports vivoactive6 and is free of the issue I described above. 

    However it turned out that for same fenix 5 devices I cannot disable the heart rate sensor:

    Sensor.disableSensorType(Sensor.SENSOR_HEARTRATE);
    It just throws similiar error. I'm thinking of getting rid of this line but I'm not sure if there are any downsides (so far it was invoked whenever user pauses/saves/discards activity), any ideas?




  • I also saw similar errors with the Position constants. But so far only locally (either during compilation or in the simulator), fortunately no ERA reports 

  • I also saw similar errors with the Position constants. But so far only locally (either during compilation or in the simulator), fortunately no ERA reports 

  • in reply to SzymonP
    SzymonP said:
    Thanks! I taught they communicated that we are supposed to use only the latest one

    No worries!

    That's the general recommendation, yes. As you can see with your experience with vivoactive6, there are reasons not to use older SDKs.

    Btw, you can see which CIQ API levels are supported by a given SDK version by opening compilerinfo.xml in the SDK's bin folder, and looking at the list of SDK versions under the targetSdkVersions key. (It should really be called targetApiVersions, but that name comes from a time when SDK and API versions were aligned.)

    For example, looking at SDK 8.1.1's compilerinfo.XML, we can see that the highest supported API level is 5.1.1, which would exclude any devices which released with a higher level (including vivoactive6, I guess).