Newly published watch face issue

No news for me.
I check every day, several times of the day.
It became something like a nightmare.

1 Like

A bit out off topic, i have a reported an offensive review to be removed and 2 months later it still being processed by their specialists… i think they are the same specialists handling the watch face section on Google store.

1 Like

Unfortunately after nearly a year of experience with Google Play Store, I can say that developers are treated worse than end users.

1 Like

The developers do not play a role for them. At least for their WearOS project.
When everyone sends them tickets and no one finally gets feedback from someone who really understood the problem, it’s obvious what’s going on. They currently don’t care or they don’t have a team that cares about WearOS apps.

The communication policy there is by far the worst I have ever seen in my business life.
I fear that nothing will change even after the Pixel Watch is released.

But if pure automation brings us to a point where only stupid, simple issues are solved and the real issues end up in a black hole … yeah … good luck with that.

Man, I’m pissed off about all this …

4 Likes

Actually, I didn’t want to get upset about this matter anymore and withdrew from the discussion for the time being. But I can’t help it: I have to report the result of my letter to the Google support team.

I have reported to the support team exactly where the problem lies. (Customers have not been able to download the latest Watch Faces for months, No ranking in Play Store, No registration as Watch Face etc.)

This was followed by multiple e-mail correspondence with Google.
Here are some answers from Google Support (only the most important text passages):

1st mail:
need as much of the following information as you have:

  • Name, type of the device*
  • IMEI/MEID number of the device: (Press Settings > About Phone > Status to find your device’s IMEI/MEID number)*
  • Primary account on the device*
  • Number of accounts on the device*
  • Time, date and location when the search was performed*
  • Device screenshot of the issue (these are really helpful!)*
  • Web screenshot of the issue*

2nd mail:
May I have a screenshot of the actual behavior of your app on your end and your expected behavior for your app (can be a screenshot from another app).

3. Mail:
I would recommend to clear the cache and data for the Play Store app and your device’s download manager. This will clear any settings and temporary information saved to your device. You can still access purchases you’ve made from Google Play, like apps, music, movies, and books.

  • Open your device’s main Settings app.*
  • Tap Apps or Application manager (depending on your device, this may be different).*
  • Tap Google Play Store.*
  • Tap Storage.*
  • Tap CLEAR CACHE > OK.*
  • Tap CLEAR DATA > OK.*
  • Tap the back arrow to go back to the main menu.*
  • Select Downloads or Download Manager.*
  • Tap CLEAR CACHE > OK.*
  • Tap CLEAR DATA > OK.*
  • Relaunch the app.*

4. Mail:
I would like to clarify if your issue is regarding having the option to install your app using Watch. May I know if the actual state of your app is that it only has the option to be installed in mobile devices currently please? Also, may I clarify if you would like your app’s expected result to be that it would be available to be installed in both options: mobile device and watch?

5. Mail:
If possible, please provide the email address of the account which is logged in on the watch which can’t install the app. Also I would need the name and type of the device you are currently using. This information is required by the technical team to proceed further on this investigation.

6. Mail:
Thanks for your reply.
I need more time to investigate your request. I appreciate your patience while I look further into your issue, and I will provide an update as soon as possible.

I explained the problem anew each time. I have explained to support that I am a developer and not an end user. I explained that customers in 172 countries around the world cannot download the Watch Faces. I have sent a list of all compatible watches to Google Support.
etc. ect.

All this is completely pointless because the support is completely incompetent.

1 Like

Hahaha (cynical laugh) guys, I’m living the same experience right now. :partying_face:

The most challenging part is to stay respectfull and nice when you just have to say to the support guy he is incompetent and you want to exchange with somebody who knows Wear OS … without sounding as an asshole.

After exchanging some messages with an actually nice but completely incompetent (about Wear OS) person, I told him, he is not competent because what he tells me makes no sense for Wear OS, that his answers shows he never even used a Wear OS watch … and I kindly asked him to escalate my request to a competent support member. He finally answered me :
ā€œI’ve documented your issue and escalated it to our technical team for further investigation. Our team is working to resolve this issue for you as soon as possible.ā€

As a show of complete lack of competency here are some chosen parts of his answers :

"To enlighten you with the issue, I have checked the compatibility of your app on a Samsung A31 phone. And the app is not compatible due to missing device features.

** **Missing device feature:*android.hardware.sensor.heartrate, android.hardware.type.watch

This means that whenever you access your app with the Samsung A31 phone, A device compatibility warning will show in the Play Store for Samsung A31 phone.

It is possible that the app you are comparing to your app is built for both Android phone and Wear OS which is why the other apps you tried do not show the compatibility warning."

ā€œWhat I am trying to explain is your app will show on the Play Store phone device even if the build is not compatible with the phone. However, it will prompt a device compatibility warning. Like the one you have sent in the picture. This means that the build is only compatible in the Wear OS device. I want to clarify that in my previous message I did not say that your app is not showing in the Android Phone Play Store. The device compatibility warning is expected on your phone device because the app is not compatible with Android phones. The real problem in your issue is the compatibility of the app in Android phones and not in your Wear OS. This is the reason why the compatibility warning when you access your app in your Android Phone.ā€

ā€œThe app is showing a device compatibility warning because your app is only compatible with Wear OS devices. This is the reason why you can only install the app within the web or directly the Wear OS devices. Basically your phone device is treating the app as a phone app when you access your app link via playstore on your phone. Thus, your phone device triggers the warning. This is expected since your app is for Wear OS devices.ā€

1 Like

If you have any Google (Alphabet) stock, maybe it’s time to think about selling :laughing:
Jokes a part… It’s a truly shameful fact.

2 Likes

So the situation has only gotten worse over time it seems. It’s really sad, for us developers as well as for the users that cannot even find our work, if by some miracle it does show up.

What other platforms are you looking at Matteo?

1 Like

Usual platforms that we all know…

After a year of investing all my energy with WFS, GW4, Wear OS and Play Store, I was completely disappointed. I don’t understand how Samsung found deals with these four-penny villains.

I’m so sorry for the WFS Team who did a really great job.
I feel embarrassed for them.

Wear OS management on Google is completely bankrupt. Please Samsung, let’s go back to Tizen and activate your store again.

They are litterally giving all the market to Apple.

Could not agree more, feels like we have been slowly laid off over the last year.

A very good Watch, brilliant software for us devs and then the worst store and support from google imaginable.

4 Likes

For me it’s like Wear OS has always been before Wear OS 3. Unlogical, unreliable, frustrating. They still don’t seem to care at all. Bugs can stay unfixed for monthes if not years.

I suppose Google has just lost the 2000 vibe. Whatever new project they launch, they don’t commit enough to it and fail. Sadly, that has been true for years. Social networks, smartwatches OS, online gaming …

1 Like

Guys, check your latest releases today. Looks like Google has finally fixed our issue ! :slightly_smiling_face:

3 Likes

They were really fast :rofl:

I propose July 9 as a national holiday.

2 Likes

Yes it is … all my published watchface have the selection option again.

2 Likes

I don’t have a device selection list in my Google Play App.
But the watch face is immediately installed on the watch.
So a companion app with an ā€œopen on watchā€ button is still useful.

@Futorum

Try to clean the cache on Play Store App.
I checked your watch faces and they all have the drop down menu.

1 Like

Thanks Matteo!
I cleared the cache and data right away, maybe it depends on the Wear OS version of the connected watch.
My watch has Wear OS 2.4.

In any case, I see my new watch faces in the top and it’s very good!

1 Like

UPDATE:

Also this issue seems to have been resolved.

Watch faces are now regularly ā€œtaggedā€ as watch faces.:

–

Summary

There seems to be a new issue …

The watch faces released from around the end of June are not ā€œtaggedā€ as watch faces on the Play Store even if the ā€œwatch faceā€ tag has been selected on the Play Console.

Then:

Now:

As a result, the watch faces will not appear in the rankings.

My last Watch Face TSD35 is now listed but still can’t be downloaded.