Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Unintended behavior
View staffing
Description
com.google.android.gms.tasks.Task
com.google.android.gms.wearable.*
Version used:
Emulator, Wear OS 3.5, API 30, Play Services 23.12.13 (220300-520023152)
Galaxy Watch4, Wear OS 3.5, Play Services: 23.12.13 (220300-520023152)
Detailed explanation: Using DataClient for communication between two devices does not work properly on Wi-Fi, LTE after every other Play Services update. When both devices are connected via Bluetooth, they will start communicating just fine. Problem is most probably on Wear device side.
What's interesting is that this issue only occurs when building .aab' and publishing on internal or public release on Play Store. When I build only signed apks and manually install them (adb install), communication via Wi-Fi, mobile data works fine. In both scenarios, .addOnSuccessListener / .addOnCompleteListener return success, only difference is that production / internal test releases are not responding to onDataChanged events.
What I've tried to workaround this with no success
1. restarting both devices
2. re-installing both wear and mobile apps
3. using setUrgent() and sending System.currentTimeMillis() to be sure that data event is always different
How did I manage to solve it? By wiping emulator / reset + connect to a new phone. After resetting the devices, and linking to the same mobile phone, production release apps started communicating via Wi-Fi and mobile data normally.
How to reproduce? It's hard to tell. Right now, after devices reset, everything works. Last time this error occurred was with play services v23.07.14. I've solved it with wipe because I though issue was on my end but this issue randomly re-appears on every other Play Services update. Maybe something randomly goes wrong between play services updates, making it impossible for the devices to communicate?
I was requested to open this issue based on Kotlin-Slack conversation
Full discussion about this issue here: