WearableListenerService onMessageReceived will not get fired [android wear]

Question

I am trying to send to send a message from handheld to wear-emulator, (according to this tutorial). Unfortunately my WearableListenerService.onMessageReceived doesn't get called.

Here on SO I have read it could be somehow related with gradle.build file,

my gradle.build in 'mobile' module (handheld):

apply plugin: 'com.android.application'

android {
compileSdkVersion 20
buildToolsVersion "20.0.0"

defaultConfig {
    applicationId "com.example.benji.data"
    minSdkVersion 15
    targetSdkVersion 20
    versionCode 1
    versionName "1.0"
}
buildTypes {
    release {
        runProguard false
        proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
    }
}
}

dependencies {
compile fileTree(dir: 'libs', include: ['*.jar'])
wearApp project(':wear')
compile 'com.google.android.gms:play-services-wearable:+'
}

my gradle.build in 'wear' module:

apply plugin: 'com.android.application'

android {
compileSdkVersion 20
buildToolsVersion "20.0.0"

defaultConfig {
    applicationId "com.example.benji.data"
    minSdkVersion 20
    targetSdkVersion 20
    versionCode 1
    versionName "1.0"
}
buildTypes {
    release {
        runProguard false
        proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
    }
}
}

dependencies {
compile fileTree(dir: 'libs', include: ['*.jar'])
compile 'com.google.android.support:wearable:+'
compile 'com.google.android.gms:play-services-wearable:+'
}

I have everything else set up as it is in the previously mentioned tutorial.

Thanks for any possible answers

Did you register it in your Manifest? – Gabriele Mariotti Aug 28 '14 at 11:05 — Gabriele Mariotti, Aug 28 '14 at 11:05

score 0 · Accepted Answer · answered Aug 28 '14 at 11:31

0

Problem relies in modules start order, first launch Handheld module app, and THEN wear emulator app, not vice-versa as I did before :)

answered Aug 28 '14 at 11:31

romanos

1,288
2
11
20

Why does this matter, and how did it fix your problem? – Glenn Bech Feb 28 '15 at 07:25
Without keeping of correct order of apps, they are unable to connect to each other. At least it was so when I was experiencing this issue. – romanos Mar 06 '15 at 20:25

score 0 · Answer 2 · edited May 23 '17 at 12:05

0

It's work for me

If you use Proguard to protect your apk , you need to ensure that the Gson class won't be Proguard, If you use the Gson class

Like this ProGuard for Android and GSON

Then you must ensure that the apk on your phone and wear must have the same signature, in other word, you need to use the same KeyStore file to export the singed APK.

edited May 23 '17 at 12:05

Community

1
1

answered Jan 04 '15 at 13:30

Angus

91
2

You should paste relevant content of your links here to avoid dead links issues – Benoît Latinier Jan 04 '15 at 13:54

WearableListenerService onMessageReceived will not get fired [android wear]

2 Answers2