Watch face app is only compatible with watches, it is not bonded with the phone device. So it will show compatibility with your Galaxy Watch 4 (R870/R880) and not compatible with the Z Fold (or other phones). Unless you add a binary for the phone too in the release, e.g. watch app with a companion app.
I didn’t create a companion app, it’s just the binary created from WFS. What is Play dev support talking about Fold 3 conflicts with heart senor package in the watch face?
Something is going with with Fold 3 or my Fold 3. My Fold 3 is paired with a Watch4 Classic, R890. Play store is still can’t detect it as a compatible device. It’s not a Play store lag issue, I re-paired the watch with a S10, there is no incompatible message on S10 and shows the paired watch as compatible device.
However when I click on the install button from Play store, it states “installing soon”. That was 3 hours ago and it is still showing “installing soon”.
That’s normal, if you can install it that means it is no problem with compatibility. And yeah installing soon sometimes works immediately on watch, sometimes you need to hit the install button again. Or you can try to download it directly from the watch play store to speed up the download.
Well, the same S10 is now showing the incompatible message. Nothing has changed, both S10 and Watch4 just sat on my desk for the last few hours. So weird!
This is a problem in a watch device that do not support the off-body sensor and this should be improved in a second update sometime this Autumn.
It is recommended when you publish your watch face application exclude the devices that do not support off-body sensor. You can rebuild and update after the next WFS release.
We are aware that the OPPO Watch does not support the off-body sensor there may be others.
Ron
Samsung Developer Relations
What is a off-body senor? My listing excludes every devices, except for Galaxy4 series and two TicWatch 3 series watches that have been confirmed to receive WearOS 3.0 update later this year.
I assume off body sensors are just what it says, They need to be worn in order to send HR data. WFS probably needs to check and return NULL or something when that happens.
Ron
Samsung Developer Relations
1 Like
I found something. (But not a solution)
I have customer in USA. I made a watch face for him but his Phone says it is incompatible. The watch model is SM-R925U which is an LTE Watch5 Pro. When I check my device compatibility in Play Console, there are only 6 Galaxy Watch5 versions, and all of them ending with W920. I have assigned myself as the tester. I deleted the watch face from My Watch6 Classic. Then Install button apperead in Play Store, so I insalled it. Then I wanted to try the same thing with the customer’s watch5. I connected to his PC and his Phone via Team Viewer. I did everything same but I was unable to install it.
My guess is it is because his watch5 is an LTE one and none of my watch faces compatible with LTE watches. I don’t even know how to make it compatible.
My last attemp was installing watch face studio on the customer’s pc using Watch Face Studio. I tranferred my Watch Studio folder to his PC. I published it and tried to send it to his watch but it didn’t work because he couldn’t enter the ip and port numbers on the pc in the required time because of his health problems.
I am trying to fix this problem for the last 2 months. There is no way because Google is taken over by Skynet. I am asking a question to them and a bot is answering and the answer doesn’t solve my problem. It’s not only about this problem. I asked why they deactivated my google ads account, I appealed why my app size was too big for their bots to realese. Always robotic answers.
When I ask Samsung something, I can tell a human being is answering my questions. It is not only a human being, it is also a nice hearted human being. If there is nothing they can do about it, they answer you nicely and tell you the reason.
Not like R2D2…
I wish Samsung carried on accepting watch faces all over the world, not only for Wear OS for China… I am not even sure if they accept Wear OS watch faces on Galaxy Store. I am going to try it now.
I made 26 watches for Google. Only sold 30 within 1 year. Because my watch faces are either incompatible or people cannot find any of my watch faces. Even I cannot find it even I search for the exact name of the watch face. As you all know nobody in the world is going to type the exact name of your watch face. Everybody searcher for Watch Faces, they don’t know my name or the name of the watch face. Everything is incompatible with Skynet.
In Galaxy Store, when I open watch tab, I can see many of my watch faces.
Thank You for reading…
Hi what do you mean by required time? To my knowledge there is no time limit to enter the ports.
Unless wifi debuging is disconnected because watch goes and switch of its wifi or switch to Bluetooth.
Only need to switch off bluetooth or put watch on charger
1 Like
That’s exactly what I meant. When the screen turns of, the watch goes to the main screen and the port numbers change untill the person comes back to the same screen.
I am now trying to sideload my watch face to my watch with an app called Easy Fire Tools. Nothing worked so far.
Try asking user to put his watch on his charger when doing the pairing…
1 Like
I will do that. Thank You…
By the way, I just uploaded a Wear OS watch face to Galaxy store. I don’t care if it is only China and their population is very small… 
On it could be screen time out…mean if idle to long it will just close…so suggest just taping on the screen.
Alternatively why not create a new topic. See if any fellow developers has the same watch, help to test.
1 Like
I will…
Thank you again…
What version of WFS did you use to create your watch face. I assume it is at least 1.3.13 that is the minimum version compatible with Wear4. If it is older than that version then it is indeed incompatible.
If your created it with WFS 1.5.7 and he is still running Wear 3 it may be incompatible you would need to see if he has updated to the latest One UI 5 wear API 33 for that.
My guess is if it isn’t one of those, then you have a default complication that requires a phone perhaps something like calendar or upcoming events or something like that.
Ron
Samsung Developer Relations
1 Like
I created it with 1.57. I checked for updates on his Samsung Phone’s Weareble App and there were no new updates. I didn’t pay attention to any version number. I have Galaxy Watch 4 and 6 Classic and they are both upto date. I still get Your Phone is Incompatible error until I assign myself as a tester. I assigned him as a tester but it didn’t work.
About complications. The original date order in the Watch Face Studio is like this: [DAY_WEEK_S], [MON_S] [DAY_1_31_Z] but in my watch faces it is like this: ([DAY_WEEK_S])-([DAY_1_31_Z])-([MON_S])
I wonder if this is complicating the complications. I only change commas into dashes.
Thank You…
Both you and your customer go to play.google.com and in your profile see Library and Devices and see if your watches are listed. You need the same google mail account as you use for your devices.
Ron
Samsung Developer Relations
1 Like
I will do that. Thank You…