Connect IQ Android SDK throwing internal exception during mConnectIQ.sendMessage processing?

Former Member over 5 years ago

Hello - I am developing a Garmin Connect IQ app that is generally behaving quite well on several types of watches (Fenix 5x, Forerunner 235). I've integrated your latest Android SDK into our Mobile Medical Application to deliver important information, alerts, etc. Since it's a medical device, the reliability & timeliness of the phone messages are important. On an Android Pixel 2 running the latest Android 9, API 28, I am experiencing fairly frequent FAILURE_DURING_TRANSFER message status returns which may delay the watch updates until SUCCESS eventually occurs. I only send messages when the watch is connected according to the device status returned from onDeviceStatusChanged in the IQDeviceEventListener. It appears (please see the below Android logcat extracts) that an exception internal to the ConnectIQ SDK is occurring somewhat frequently. Interestingly, the phone message send succeeds at times even after the exception (traces of both success/failure below). I do not see this exception on a Samsung S9+ (also running latest Android 9, API 28) running identical software. Is this a likely or known bug in the Connect IQ SDK? Perhaps my app is behaving in a way that causes the link to be fragile? Is this normal? The phone messages are slightly more than 1K bytes in length generally occurring at 5 minute intervals. Any insights or suggestions would be most welcome. Thanks, Matthew

2019-09-12 17:40:55.646 1385-1385/com.senseonics.androidapp W/Bundle: Key com.garmin.android.connectiq.EXTRA_REMOTE_DEVICE expected Long but value was a com.garmin.android.connectiq.IQDevice. The default value 0 was returned.
2019-09-12 17:40:55.646 1385-1385/com.senseonics.androidapp W/Bundle: Attempt to cast generated internal exception:
java.lang.ClassCastException: com.garmin.android.connectiq.IQDevice cannot be cast to java.lang.Long
at android.os.BaseBundle.getLong(BaseBundle.java:1070)
at android.content.Intent.getLongExtra(Intent.java:7397)
at com.garmin.android.connectiq.IQMessageReceiver.onReceive(IQMessageReceiver.java:134)
at android.app.LoadedApk$ReceiverDispatcher$Args.lambda$getRunnable$0(LoadedApk.java:1391)
at android.app.-$$Lambda$LoadedApk$ReceiverDispatcher$Args$_BumDX2UKsnxLVrE6UJsJZkotuA.run(Unknown Source:2)
at android.os.Handler.handleCallback(Handler.java:873)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:193)
at android.app.ActivityThread.main(ActivityThread.java:6718)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
2019-09-12 17:40:55.649 1385-1385/com.senseonics.androidapp D/RichWatch: RichWatchUtility sendMessage status # 1509 - FAILURE_DURING_TRANSFER

2019-09-12 17:44:00.399 1385-1385/com.senseonics.androidapp W/Bundle: Key com.garmin.android.connectiq.EXTRA_REMOTE_DEVICE expected Long but value was a com.garmin.android.connectiq.IQDevice. The default value 0 was returned.
2019-09-12 17:44:00.400 1385-1385/com.senseonics.androidapp W/Bundle: Attempt to cast generated internal exception:
java.lang.ClassCastException: com.garmin.android.connectiq.IQDevice cannot be cast to java.lang.Long
at android.os.BaseBundle.getLong(BaseBundle.java:1070)
at android.content.Intent.getLongExtra(Intent.java:7397)
at com.garmin.android.connectiq.IQMessageReceiver.onReceive(IQMessageReceiver.java:134)
at android.app.LoadedApk$ReceiverDispatcher$Args.lambda$getRunnable$0(LoadedApk.java:1391)
at android.app.-$$Lambda$LoadedApk$ReceiverDispatcher$Args$_BumDX2UKsnxLVrE6UJsJZkotuA.run(Unknown Source:2)
at android.os.Handler.handleCallback(Handler.java:873)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:193)
at android.app.ActivityThread.main(ActivityThread.java:6718)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
2019-09-12 17:44:00.413 1385-1385/com.senseonics.androidapp D/RichWatch: RichWatchUtility sendMessage status # 1542 - SUCCESS

Top Replies

ArtaudAntonin / Jiri Richter over 5 years ago +1

Hi Matthew, brace yourself for a bumpy ride if you plan to use the Android ConnectIQ SDK.

As far as my experience goes, the development on the Android SDK has been abandoned. There was a survey from Garmin…
ArtaudAntonin / Jiri Richter over 5 years ago in reply to ArtaudAntonin / Jiri Richter +1

Brandon.ConnectIQ bump here for the old comm issue...

All Replies

Former Member over 5 years ago

Minor note: I now see this exception on the Samsung S9+ (also running latest Android 9, API 28) as well. I imagine it's just luck I didn't see it before. Thanks, Matthew

ArtaudAntonin / Jiri Richter over 5 years ago

Hi Matthew, brace yourself for a bumpy ride if you plan to use the Android ConnectIQ SDK.

As far as my experience goes, the development on the Android SDK has been abandoned. There was a survey from Garmin about the SDK 3 years ago (see here) and NOT ONE of the issues that we complained about was addressed.

The biggest issue is reliability of the messaging system in general.
Please see

For an extensive overall feedback by one of the prominent developers, see https://forums.garmin.com/developer/connect-iq/f/discussion/7985/general-wishes-ideas-for-connect-iq-future

ArtaudAntonin / Jiri Richter over 5 years ago in reply to ArtaudAntonin / Jiri Richter

Brandon.ConnectIQ bump here for the old comm issue...

Former Member over 5 years ago in reply to ArtaudAntonin / Jiri Richter

Appreciate the insights! I'm not adverse to bumpy rides but I also do not have a death wish. ;}

A few trivial notes below but first: I'm starting prototyping using the iOS SDK. Did you have similar experience on the iOS side? Please don't suggest it's worse!

One note on this old note (https://forums.garmin.com/developer/connect-iq/f/discussion/4853/failure_during_transfer/41230#41230) - I am strictly sending one-way, from phone to watch app. I can try re-starting GCM although I wanted to try waiting 10s or so to see if it clears consistently on it's own. In my case, it does eventually clear & comm returns SUCCESS.

Interesting that this also notes the exception years ago (https://forums.garmin.com/developer/connect-iq/f/legacy-bug-reports/5144/failure_during_transfer-issue-again-now-using-comm-sample/913495#913495).

Again, thanks for the insights, Matthew

ArtaudAntonin / Jiri Richter over 5 years ago in reply to Former Member

Sorry, I have only ever done Android integration so no ideas about iOS. I only got a feeling from posts on the forum that there are some different issues on iOS than on Android but don't know anything specific.

Alexis_Lecanu over 5 years ago in reply to ArtaudAntonin / Jiri Richter

@ArtaudAntonin For you it's over? it's no use continuing to dream. Too bad because I had lots of cool ideas.

ArtaudAntonin / Jiri Richter over 5 years ago in reply to Alexis_Lecanu

For this issue I'm using the ContextWrapper workaround which works fairly well. I hate that I have to do it but it seems to have no side effects.

2668223 over 2 years ago

It might not solve everyone's problem, but the problem I had was in release only and was solved when I changed by android build.gradle to stop minifying and use proguard instead so I could:

-keep class com.garmin.android.connectiq.** { *; }

build.gradle at the app level

buildTypes {
 debug {
 signingConfig signingConfigs.debug
 }
 release {
 signingConfig signingConfigs.release
 shrinkResources false
 minifyEnabled false
 proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
 }
 }

with the proguard-rules.pro file

## Flutter wrapper
-keepattributes Signature
-keep class io.flutter.app.** { *; }
-keep class io.flutter.plugin.** { *; }
-keep class io.flutter.util.** { *; }
-keep class io.flutter.view.** { *; }
-keep class io.flutter.** { *; }
-keep class io.flutter.plugins.** { *; }
-keep class com.google.firebase.** { *; }
-keep class com.garmin.android.connectiq.** { *; }
-keepattributes JavascriptInterface
-keepattributes Annotation
-dontwarn com.razorpay.**
-keep class com.razorpay.** { *; }
-optimizations !method/inlining/
-keepclasseswithmembers class * {public void onPayment*(...);}
-keepclassmembers class com.yourpackagehere.models.** { *; }
-dontwarn io.flutter.embedding.**