Complete
over 5 years ago

SDK 3.1.8 just break support for vivoactive 3 trainer

I compiled samples included with SDK 3.1.8 and installed to v3t using side load method (copy the prg to /garmin/apps). And all apps result in error of:

Error: Symbol Not Found Error
Details: Could not find symbol initResources.

And I submitted an app to CIQ app store using beta testing method, when I tried to download the app to v3t, I got prompt I should upgrade my firmware. But the firmware is up to date, which is 2.3 (APAC version).

I did further investigation and found that, the latest version of firmware of v3t with support of CIQ 3.0.3, but SDK 3.1.8 only support v3t with CIQ version 3.1.x (In fact v3t never support CIQ 3.1.x, at least my APAC version support only 3.0.3 with latest firmware.). Thus make apps compiled with SDK 3.1.8 cannot run on v3t with CIQ below 3.1.

V3T (world edition or APAC edition) are currently on sale and are popular in many countries, and CIQ store support is very important to customers, if you just buy the new device and found most apps cannot be installed, it will be disappointing and against the advertisement which clearly indicates the V3T support CIQ app store.

Using some methods I confirmed that CIQ 3.0.x can run most apps, please support apps to be run on v3t with CIQ 3.0.x in further SDK release, or release firmware upgrade for v3t (don't forgot APAC edition please) if you only support CIQ 3.1.x in further SDK.

Latest FW is 2.3:

CIQ SDK 3.1.8 support only CIQ 3.1.x for v3t with part number 006-B3446-00, but latest version 2.3 FW carry with CIQ support 3.0.3. It's so weird.

Previous SDK 3.0.12 which supports CIQ 3.0.3 for v3t just working fine.

SDK 3.1.6 also support CIQ 3.0.3 for v3t.

When build app for vivoactive 3 (which v3t categorized into this class) in SDK 3.1.6, you can see it support CIQ 3.0.x and 3.1.x which should be correct:

 

But SDK 3.1.8 support 3.1.x only, and break support for devices with CIQ lower than 3.1.

Former Member
Former Member
  • Former Member
    Former Member over 5 years ago in reply to jim_m_58

    Thanks for your information, really appreciate it!

  • over 5 years ago in reply to Former Member

    Hacking the SDK is frowned upon, and you want to check with someone like before using it to publish apps. There is a -u parameter you can use BTW.

  • Former Member
    Former Member over 5 years ago in reply to Travis.ConnectIQ

    Thanks for your reply. Previous SDKs were unable to downloaded because Garmin removed all download links, so I just did some hack to 3.1.8 devces.xml to support my device as temporary workaround. But really annoying is that most apps in CIQ store were unable to downloaded because of "need to upgrade the device" error, before new firmware release or developer submit new version of app using fixed SDK, the issue will continue.

  • Former Member
    Former Member over 5 years ago

    After tried compile with different SDKs (in fact different versions of monkeybrains.jar), I found a simple fix:

    Just change the line of device info with part number 006-B3446-00 in devices.xml from:

    <part_number connectIQVersion="3.1.6" firmwareVersion="720" number="006-B3446-00">

    to

    <part_number connectIQVersion="3.0.3" firmwareVersion="230" number="006-B3446-00">

    the devices.xml should be changed in 5 locations:

    1. bin/devices.xml

    2. within bin/monkeybrains.jar

    3. within package content folder of ConnectIQ.app

    4. within package content folder of MonkeyMotion.app

    5.within file monkeybrains.jar in package contents of MonkeyMotion.app

    When build for vivoactive 3, just select 3.0.x target, and everything works for side load install and beta testing install.

    Hope Garmin fix this in next SDK release, I believe better support for existing customers is vital for growth.

  • over 5 years ago

    According to the data in the devices.xml that you've posted, the firmware version 7.20 for that device (006-B3446-00) should have support for the 3.1.6 SDK. All indications are that there is no 7.20 firmware for your device, which seems to imply that there is an error in devices.xml or a product firmware didn't get released before the ConnectIQ SDK did.

    As a workaround, you can continue using the 3.1.6 SDK if you still have it around.