Hello, it looks like we don't have a channel for W...

# compose-wear

[louiscad]

Hello, it looks like we don't have a channel for WearOS Watch Face developers. Is anyone busy making one here?

[John Nichol]

I am happy to explore the option for a watch face and complication channel. Guess we need to see if the kotlinlang folks would be happy for it to be hosted here.

[John Nichol]

In the mean time is there a specific question/topic? I can relay it to the Watchface team as I am involved.

[louiscad]

Yes, I have a specific topic: I have a TicWatch E3 and a Samsung Galaxy Watch 4, and the latter one, which I believe has the largest market potential, has a major issue where watch faces made with androidx.wear.watchface, and legacy watch faces made with the support library, don't update while in always-on/ambient mode, which means it shows the wrong time.

I submitted an issue 2 days ago here, but I got no acknowledgement yet, and I'm really worried about my plans of publishing a freemium Watch Face soon if all Samsung Galaxy Watch 4 users that use always-on mode are to be affected for an unknown amount of time.

[John Nichol]

I understand that this is a known issue with the Samsung Galaxy watch and that they plan to fix in next maintenance release. - But this is just whatI have heard not an official position

[louiscad]

Thank you for the info, I'm glad to learn that a fix is planned.

IMO, for such major regressions, there should be a hot fix, we shouldn't wait for the next scheduled released. That's what we app developers do, even though we usually have much less budget than Samsung (or Google), if you can get the message across, that could be good. 🙂

[louiscad]

Another question I have on the topic: Are there any Samsung Developer Advocates for their WearOS watches? I think it'd be mutually beneficial to have a community relationship with them since they're making quite a customized version of WearOS while we want to make apps that work nicely on all watches.

[Kseniia Shumelchyk]

cc @Garan Jenkin

[Thomas]

If someone here has contacts at Samsung please let them know that there's a huge ANR issue in their latest Watch4 software update. It's affecting my Wear compose app really bad and the ANR graphs on Google Play are even worse. https://issuetracker.google.com/issues/220190983

[Austin Nelson]

I think I’m having the same ANR issues :/

[Thomas]

Yes, that looks like it. At least you don’t have to worry about it as it appears to affect everyone.

[Thomas]

I already received a few thousand ANRs so far. Not a single users has complained to me about it, so it seems they don’t notice. For me the ANRs are 100% in background (shown on Firebase).