No callback from getApplicationInfo sdk 2.1

Hi,

I'm using new sdk 2.1 with Edge 1000 and Samsung Galaxy s6 (6.0.1). With the Comm sample widget supplied by Garmin, I am not receiving the onApplicationInfoReceived event.
Trying to send or receive data doesn't works.

Any help would be greatly appreciated!

Thanks.
  • Hi,

    I'm using new sdk 2.1 with Edge 1000 and Samsung Galaxy s6 (6.0.1). With the Comm sample widget supplied by Garmin, I am not receiving the onApplicationInfoReceived event.
    Trying to send or receive data doesn't works.

    Any help would be greatly appreciated!

    Thanks.


    Hi,

    I have changed the widget program to app program with the same results. I also tried with another phone with Android 5.0 but not works.
  • Which version of GCM are you using? We made some recent improvements in regards to onApplicationInfoReceived in GCM 3.9. If you have a previous version of GCM, do you mind retesting and reporting back your results here?
  • My version is 3.8.0.1, where I can download version 3.9 to make the test?
  • Sorry, I gave some bad advice as 3.9 isn't available yet. It should be available in the next week or two as far as I know.
  • Ok, I will test it when the new version is available.
  • I have installed new sdk 2.1.2 and CGM 3.9 with the same results, no works the callback.
  • We had a report similar to this a few months back, and we believed it to be fixed. We'll take a look and see if we can figure out what's happening.
  • @ManuDominguez Are you using the same application ID in both the Connect IQ app at the Android app?
  • Yes, It's the same ID. I have only changed in the example widget to add edge 1000 for compatible devices.
  • Former Member
    Former Member over 9 years ago
    I can confirm, that working companion app with working watch app stopped receiving callback onApplicationInfoReceived after I was forced to update sideloaded version of my watch app to latest SDK version (last working version was sideloaded with SDK 1.2.11) due to watch update with SDK 1.3.1 on ForeRunner230. And there is now no more another way to make watch accept sideloaded app unless it is signed (this requires SDK 2.1.x to be set as current). This is a serious issue.

    Please, Garmin devs, check this. Maybe connectiq.jar for Android needs to be updated?

    P.S. reinstallin my app of previous version from Garmin market didn't resolve the problem: there is still no callback in companion app. Is there any way to make things work again other than resetting watch to firmware with previous SDK?
    P.P.S. it seems that this problem is indeed related to the firmware 5.20 for ForeRunner 230 since I created small watch app with mobile companion from scratch (used new id) and still no callback... Please, Garmin, be nice and at least provide link to download previous fw (FR230 = 4.7, cannot find links to previous FW on garmin support) since new update brought just inconviniencies.

    P.P.P.S. I did comprehensive research since I was actually rather enranged with the current state of events: I did revert to FW 4.70, used combinations of my app compiled with SDK 2.1.2 and 1.2.11 to no avail. Finally I found rather old Garmin Connect Mobile apk on some forum (3.5.1) and connectivity options suddenly came back to life even with app compiled using latest SDK and latest watch FW featuring SDK 1.3.1. Thus, for everyone who is facing Android companion connectivity issues, I recommend to not update to GCM 3.9 which is currently present on Google Play but use previous version instead.


    This problem bothered me so much, so that I even took half day off to make things run normal, thus here is my last commit for today.
    I did the clean experiment starting from actual watch firmware and GCM (I have FR230, actual FW5.20, phone is Andrioid 6.1, GCM v3.9):
    1. FW5.20 + GCM3.9 - android app doesn't receive getApplicationInfo callback
    2. FW4.70 + GCM3.9, watch deleted from GCM before update and paired after update - android app works as expected (all callbacks are received), watch app receives data be it compiled either with SDK 1.2.11 or 2.1.2

    Additionally, if I update watch to FW5.20 after pairing with GCM3.9 then things keep working until phone is rebooted. It seems that bluetooth instruction set was changed since GCM v3.7.2 since it's not possible to pair watch with FW5.20 to older GCM like 3.5 anymore. So, I'll stay with 4.70 for a while until this problem is resolved, since this FW guarantees predictable behavior.