A modern programming language that makes developers happier.

kotlinlang

Sorry not fully wear compose related but discovering <https://issuetracker.google.com/issues/235538840> the hard way. Can someone confirm that removing the
```&lt;data android:scheme="wear" android:host="*" /&gt;```
Will not have impact on previous Android version and still work with Wear OS 1 (That I still support for now)?

My WearableListenerService also broke on Android 12, it is because I need to export it. Did you already export your WearableListenerService? Maybe it is not related.

Yes it's exported and working before Android 13. An applying the fix from <https://issuetracker.google.com/issues/235538840#comment7> does fix this for A13. Just need to be sure there's no side effects. I no more have a working Wear 1 watch and can't get the emulator to work and create 1.

<@UDU9YQ3JN> In general, we don’t recommend relying on a workaround from <https://issuetracker.google.com/issues/235538840#comment7> since `BIND_LISTENER` is deprecated quite a while: <https://android-developers.googleblog.com/2016/04/deprecation-of-bindlistener.html>. I don’t want to overpromise on ETA, but we’ve started rollout of the fix slowly (I will share more details on the issue once fix is fully applied), hopefully will be in next week. With this fix you will need to bump wearable gmscore version to make it work for `targetSDK=33`.

So the fix will also require that users have up to date Play Services on their devices? Or just a new build with new GMS dep? (Current not checking the version so might need to add that check to anticipate)

Yes, the fix will require both newer version of GMSCore on device and updated wearable play services dependency (`com.google.android.gms:play-services-wearable`)

<@UDU9YQ3JN> The fix for this issue has landed! See <https://issuetracker.google.com/issues/235538840#comment23>

Thanks for the record in <https://developers.google.com/android/guides/releases> the link to wearable release note gives 404 <https://developers.google.com/wear/releases>

Thanks for flagging, it will be fixed shortly. The page it’s pointing is at <https://developer.android.com/wear/releases>

Hum what is the sendRequest difference with sendmessage? Doc just mention RPC so it's more real time?

it’s an alternative to sendMessage that gives an acknowledgment when the message has been received on the other end