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.
  • Former Member
    Former Member over 9 years ago
    Thank you for your quick answer.

    I am using my phone, which is a Motorola Moto G 4G, 1st generation. It's running Android 5.1.
    I can do some testing with other Android devices, to check if it comes from the device/OS version. I can give you more information if needed (specific logs, etc.)
  • Former Member
    Former Member over 9 years ago
    Hi,

    I am having the same problem with the Galaxy note 2, Android 4.4.2, application compiled on a different computer, with Android SDK 5.1. So quite different from my previous tests.
    I now test with my app that is published in the Connect IQ app store, so the release version.
    I am wondering if something is wrong with the AndroidBLE library or my code. I follow exactly what I find in the different examples.

    Do we need to declare specific permissions in the Android Manifest?
    Is there a specific value to use for the Android API level in the application Manifest?
  • Former Member
    Former Member over 9 years ago
    Any updates on this issue? Since the end users can be using many different devices, it is very important to be sure the Garmin recommended way of obtaining the AppInfo works all the time, for any device. Or, at least, please provide a list of devices that are problematic, so that we can include a warning to our end-users. Otherwise, they put all the blame on our apps.
  • Interesting you should ask!

    We've found the problem and got the fix for the issue in today. This fix will be available in an upcoming release of Garmin Connect Mobile, though I'm not certain of the timeline at this point. 3.2 was just made available to the public in the last day or two, so I suspect it will be a little while before the next release.
  • Former Member
    Former Member over 9 years ago
    Good news! Was it impacting any devices or specific ones?
    I wish I could test that :)

    Thank you eir3apps for refreshing this question.
  • I'm still confirming, but the fix may have actually gone out with the recent 3.2 release of GCM for Android. If this is an issue you've experienced, I'd recommend updating and checking to see if the problem persists.