No callback from getApplicationInfo

Former Member
Former Member
Hello together,

I'm currently developing a prototype of a companion app for Android and face the following problem. I connect the device (which works flawless all the time) and afterwards try to load the application info for my watch app. This works sometimes, but most of the time it doesn't. Could it be, that the system is confused if you have a development app and at the same time the shop version of the app installed? What would be the solution for this? Change the UUID didn't help. Thanks in advance.
  • I'll forward this on for investigation, because I'm not familiar with what might cause this. Apologies for the inconvenience!
  • Former Member
    Former Member over 10 years ago
    I'll forward this on for investigation, because I'm not familiar with what might cause this. Apologies for the inconvenience!


    Thank you!
  • Former Member
    Former Member over 10 years ago
    Thank you!


    Is there any update on this? I'm currently on a complete stop with my development. Perhaps somebody could provide me a working sample. The sample from the mobile SDK lags the code of the watch app.
  • Former Member
    Former Member over 10 years ago
    I'll forward this on for investigation, because I'm not familiar with what might cause this. Apologies for the inconvenience!


    Do you need any additional info on the problem? I'm really stuck with this and need some advice here, please.
  • Former Member
    Former Member over 10 years ago
    Did anybody from the development team get to look at this?
  • This was reported, but I don't know whether it's been looked into yet. I'll check in with our mobile SDK developers and see if they can shed some light. Also, I didn't mean to ignore you--I was out of the office last week and am just now getting caught back up with some of the forum posts.
  • Former Member
    Former Member over 10 years ago
    This was reported, but I don't know whether it's been looked into yet. I'll check in with our mobile SDK developers and see if they can shed some light. Also, I didn't mean to ignore you--I was out of the office last week and am just now getting caught back up with some of the forum posts.


    Anything new here?
  • Former Member
    Former Member over 9 years ago
    Hi there,

    I'm having the exact same problem.
    Initializing the SDK always works.
    Retrieving the list of known devices also always works.

    But "getApplicationInfo(...)" almost never fires the "onApplicationInfoReceived(...)"-event inside the passed "IQApplicationInfoListener". :(
    Like RMZ84 also experienced... it works in very very rare cases (with the same code!).

    I'm also using a side-loaded development-app.
    I've tried restarting GarminConnectMobile and/or my watch several times... without luck.

    Any help would be greatly appreciated!

    Thanks.
  • Former Member
    Former Member over 9 years ago
    Hi all,

    I am having the same issue, except that I have never been able to make the getApplicationInfo method work, my listener never gets called.
    I am working on the Garmin forerunner 235. Everything works fine in simulation between the watch simulator and my mobile phone over ADB.

    For real testing, I first tested with the Android ADB SDK, then with the recommended Android BLE SDK, changing my code. In both cases I am not able to get the application info or send messages.

    Can that be a problem of:
    - Case in the writing of application UID?
    - Garmin connect configuration?
    - Permission on the watch app or on the Android app?

    Any help is welcome :)
  • We're still working through this issue. We've had several teams involved, and the trouble is that most people are unable to reproduce the issue. It seems somehow related to specific phones--members of one team are able to reproduce this reliably on a couple of specific devices. There aren't any workarounds that I am aware of, and since we haven't been able to identify the root cause, I can't give a timeline for a fix. I can assure you that the issue is being actively investigated!