Latest WatchFace Studio 1.1.9 WearOS Status and Supported devices in the catalog Problem!

I am aware of that. And I don’t blame you either. I’m sure you passed on the information. You’re doing great work here. Unfortunately, those actually responsible at Samsung and Google don’t do this, otherwise we wouldn’t have had a number of problems since September of last year. And yes: Samsung is not PlayStore - but Samsung uses the Playstore as a platform. If I rent a car, for example, I’m responsible for ensuring that it doesn’t break down. (I know: bad comparison)

I think. Watch faces which we made with Watch Face Studio are not compatible with the Google Wear OS application, That is Google blocks our watch faces.

No, they are fully compatible…

Can you connect your watch to the Wear Os app?

No because it uses Samsung Wearable app for connecting, which does basically same thing as Wear OS app. This thread is about play console issue. Doesn’t matter if you have GW4, fossil, mobvoi, use WFS, Android Studio, create companion app or watch face. The issue we are all getting is connected to corrupted review process which is caused by “instant Active” status of Wear OS release type. Searching for any other reason is contraproductive.

No, Google is not blocking anything. Google is just unable to solve play console issue or doesn’t want to do it as it’s not their priority.

1 Like

No. That doesn’t work

Quite right.
It doesn’t matter what the watch face is made in (WFS or Android Studio) and whether it has a companion app.

I make watch faces in Android studio and since april or even since march my new watch faces can’t be installed on watch from Google Play on phone.
Only through a web browser or through the functionality of the companion application.
Also, these watch faces are not in the search in the Google Play application on the smartphone (if you select the search for device “watch”).

6 Likes

Why don’t we all write to Google support with the “same” email content?

We all send the same message over and over until they solve their problems.

The main issue is that Watch Faces cannot be downloaded or searched on the Play Store with a “watch” device and we need to focus the email content on this issue.

Who feels like writing a quick email here to forward to Google? I am not very good with English.
A short and effective content.

We make continuous support requests with the same email content. Sooner or later they will understand it or some of them will report it to those in charge.

If we continue at this rate, we will talk about it again in 2025.

3 Likes

hello.

We recommend that you send emails with consistent content to Google.
If feedback from many developers continues with the same content,
Google appears to be aware of the seriousness of the situation.

How do you feel about creating standardized, identical mail and constantly sending feedback to Google?

I am like that. And I am ready to send them such a message, even several times a day. :wink: :grin:

This is absolutely ridiculous how long this issue has been , why can’t someone from Samsung get to the right people at Google.

I’m so glad my mortgage doesn’t depend on developing watch faces for WearOS, if this issue was in my company it would be priority number 1 and fixed in few hours not several months.

I think we should send communication to the press sites who review all this shiny wearos watches and tell them what a shambles this whole experience has been. I understand this is not Samsungs fault but aren’t they in some kind of partnership here.

It’s all very strange and I suspect something to do with the upcoming launch of their own new WearOS watch.

3 Likes

If we can’t contact and get solutions from google Samsung could at least extend the galaxy store support for watch 4 all over the world which already works for the Chinese market.

Simply as an alternative to the Play Store as happens for Galaxy smartphones, users will then choose which platform to use.

Since March 1st I have not been able to release watch faces on the Play Store due to this bug and we are now on May 8th … more than two months. Slowly everyone is being affected and switching accounts is only a temporary solution.

I know it’s neither Samsung nor ours, but here we’re all making a bad impression on users …

I can answer everyone that it is google’s fault if we cannot release what we have promised but on the user side I would find it hard to blame a giant like google by losing faith in those who say it.

Let’s hope the Pixel Watch will come out soon and they realize that the Wear OS platform also exists.

I’m not convinced that if google hasn’t done anything so far it will do it for our tickets but if we prepare a standard message and decide a frequency with which to send it, I’m in.

1 Like

"Hi, since 1 march I released several new watch faces for wear OS (with a companion app for phone).

For each of the watch faces in the Play Console section:
[Setup → Advanced settings → Release types]
Wear OS type is marked as “Active”
and in
[Reach and devices → Device catalog → Filter: Device type: Wearable]
every single smartwatch is in the “Supported” status

In the Play Store, it is only possible to install the mobile companion app and not the smartwatch version (there is no drop-down menu as there is for the watch faces released before March 1st).

Due to this bug, no user can download or search the watch face.

How can I solve it?

Thank you"

This is the message that I sent several times to google support along with screenshots to explain better, always getting answers like “Let me check a second” than “I could not solve, I pass the problem to the right sector, wait” and then more no answer…
If we want we can use this as a template (with all the necessary corrections) for the standardized message.

2 Likes

[edit: broken auto-link to https://github.com/android/wear-os-samples/tree/main/WearVerifyRemoteApp#readme has been removed]

this is a sample source code that opens wear os link from companion app on phone and also can do vice versa. So if you know how to import source code in Android Studio and make a companion app this will definitely help.

I am in process of discussions with few android developers to get paid work done on upwork and locally as well.

If i manage to make it done i will share it for free to every one whatever amount it costs me. Even if it takes me a month to get it done.

NOTE





New Companion Apps Result

still doesn’t work for me
watch all my screenshot they are in sequence

  1. I tried getting this Messa watchface .
  2. Installed fine from playstore android app.
  3. The new companion apps open link on watch still shows upaid.
  4. where as my phone shows paid and installed.
  5. i rebooted watch and phone.
  6. Waited 4 hours to let my purchase sync .
  7. Still shows unpaid.
  8. I also tried clicking it results in asking to pay
  9. Then i opened it in phone web browser
  10. From there it got installed to my watch.
5 Likes

Yes guys.
The companion app doesn’t solve our problem either.
Installation on the watch is still possible only through the browser.

1 Like

As i promised i have shared complete source code for making a companion app that opens link on connected wear OS device. Yet i still agree with Futorum developer and others we need more to get done from Google to resolve our issues. :slight_smile:

4 Likes

If the watch face was received with a promo code, it will again show you what to buy. If you confirm the purchase on the watch, the watch face will be received for free.

well it didnt work for me. When i press to buy it shows me to complete purchase on phone. I have tried 7 watchfaces and 6 developers in last 24 hours. If i even click to buy on watch. i get simillar like below , it opens on phone and asks to purchase

This one was with promo code , have also tried paid ones from other 4 x developers . free ones ofcourse wont have this issue being free.

So Google is making life difficult for us again. Everything worked great before.

As i mentioned in previous posts this method is working for some and also not working for people like me. So it can help some and at same time not to others.people like me have to install it via phone web browser and i have no problems with it but

there are all kind of customers those who even dont know what web version of playstore is :slightly_smiling_face:

it is simply opening
www.play.google.com in your phone browser, login, open watchface link install to watch and thats it :slightly_smiling_face:.
They think its some Science :sweat_smile:

I will add new companion app source code i have shared link is in one of my posts above , which will open my watchfaces in the watch but as mentioned by other worthy developers above this is not the complete solution .

Google has to fix this nonsense going on with our developer accounts