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

My watch is listed in the settings. I can view my watch faces in the store when I click the link "view on play store "in the console dashboard.
It has been 2 weeks and they are all live in the store.
I am only wondering, why can’t I see any of them when I search for it. Clicking the link is easy. I have the link, people who want to download don’t have a link to see my watch face…
I didn’t understand this part, “Try opening the store from your watch to register it in the store.”
I open the store on my watch, one of them is already installed on the watch but I cannot find that or another one in the store when I search for it.
Thank You…

If it isn’t a Galaxy Watch4 but some other brand it won’t work.

Send me the name of one of your older watch faces and one of the newer ones and I’ll see if I can see them.

Ron

1 Like

It has nothing to do with the companion apps. I also uploaded these apps for almost all Watch Faces. However, my last watch face is not registered - only the companion app.

I am suffering yet another issue at the hands of playstore review team.with a new watchface i uploaded for approval.

Wear OS says active and it has been twice rejected now by playstore other review team.

I have applied for appeal as well as uploaded 3rd time watchface with screen previews literally showing how to change background.

The reason of rejection basic functionality missing backgrounds cannot be changed. What a bunch of power IQ people have been assigned to review watchfaces. Who dont care seeing screenshots and dont even test watchface fully and reject it.

What a bunch of bufoons gathered together.

Just delete “changeable background” from the description and upload the watch face again. Once the watchface has been approved, you can change it again.

I can only once again urgently ask those responsible at Samsung to finally “discuss” this paradoxical situation at Google.:face_vomiting:

1 Like

Write in the description line - “The functions of the watch may differ depending on the manufacturer and model.”

This will solve the submission problem. But will not solve the download problem. It remains to wait and hope that google robots will fix something. :slightly_smiling_face:

2 Likes

@r.liechty_SDR

Hello Ron. Any news from Google regarding the PlayStore bugs?

I expect you designers will find out before the feedback is channeled back to me. :slight_smile:

Ron
Samsung Developer Relations

1 Like

That would be great, but I fear that in this case we have no chance without the participation of Google.:grinning:

Well today my watchface got published.

  1. I added screen previews describing each style.
  2. I also added what you said about compatibility.
  3. Also again built and uploaded the watchface.

Today it was approved something worked. By the way i also emailed them telling that your testing team should at least do their job and care to test watchface before rejecting it and let us do ours.

Something worked and yes the watchface
at the moment can be downloaded in this way.

  1. User adds playstore coupon or purchases watchfaces wether from playstore app or webstore app.

  2. I saw watchface still showing not bought even after i added coupon successfully when i opened it inside watch playstore.

  3. Then watchface downloaded and installed thru Samsung internet browser to watch4

  4. Watch bluetooth off and wifi on and connected to network to install watch immediately.

I have found no watchface with playstore install button, published exactly after Apr 14

All my watchfaces after 14 Apr have play console bug and are missing install button for other devices and also show unpaid on watch playstore app. Can only be download by web playstore on phone or pc.

This one was published yesterday.


Hi,
today I published my first watch face…
and exacly the same problem that you’ve mentioned.

I can download only from Play Store on my watch, and I can only there find my watch face.
This watch face is free so there is no problem with make payment on phone to finish download.

That was only test… and for now nothing will change. Will wait for solution for this problem.

I am also tired of answering users downrating my new watchface. So i will not release any new watchface

This is just shit distributed by Google to undermine Watch4 series before pixel watch is released. I expect this nonsense to continue till pixel watch is released.

This intentional behaviour of Google to undermine watch4 to promote pixel watch has me so much pissed off I am reallly asking my self why shouldnt i shift from Android and buy an Apple Watch and an Apple Phone. I say intentional because it has been days it hasnt been fixed and Samsung does nothing about it.

3 Likes

I will also create more WF for Tizen and less for Wearos if this situation does not change. In addition, my Galaxy Watch 4 Classic broke after only 8 months. It cannot be charged. I never had something like that with my Tizen watches. It is currently for repair at Samsung.

2 Likes

I think that this is not a playstore bug because my watchfaces are installing as expected from playstore (I dont use watchface studio). This is probably happening because Google deprecated the old watchface libraries in WearOS 3 and I guess that Samsung hasn’t updated their watchface studio to use the new libraries.

This is the opinion and view of GS Watchfaces developer who i believe is a very experienced developer and there watchfaces are made in android studio and not Samsung Watchface studio

@r.liechty_SDR can you please look at this aspect as well.

Thanks

Please, read again previous posts. This is not WFS fault. I’m writing this second time…

Ok I will read it again can this be the reason

the helper app generated with android studio. I hope we are not using old deprecated files to make helper app. I dont have knowledge about android studio that much but those who have can check this?

This is definitely play console issue.
If you took the time to read all the posts, you would find that it doesn’t matter if the person uses a companion app. One developer who created the Wear OS application in the Android Studio also spoke here that he’s having same issue.

Why being sarcastic what i have said that offends you so much. I might have missed it while reading the thread.

1 Like

HI Osman,

This is probably happening because Google deprecated the old watchface libraries in WearOS 3 and I guess that Samsung hasn’t updated their watchface studio to use the new libraries.

WFS uses androidx libaries that is not the issue, it is purely a Play Store issue.

This is the opinion and view of GS Watchfaces developer who i believe is a very experienced developer and there watchfaces are made in android studio and not Samsung Watchface studio

Watch Faces/Apps made with Android Studio have the same issue with Play Store. It will probably bite GS at some time too.

TS-Design

I haven’t really heard or read anything that Samsung wants to do anything about it.

I am doing all that is possible to get action on this it is being escalated but we are Samsung not Play Store

Ron
Samsung Developer Relations

1 Like