Watch Face Studio 1.6.10 now available

We are Facer “B” team guys.

1 Like

I updated 15 watch faces today. They are all still in review, but I’ve already received messages that the policy compliance issue has been addressed for 14 of them.

1 Like

Oh good Start . I have to drop my only security to get this .
.
.

I had to give extra description in new health policy requirment. This is new was not needed before by Google. Its a change at the Google Play Console end. My Watch face displays HR with Tag expression .

Updated watch face with latest watch face studio lets see how it goes. I have not sent update to companion app i believe that is not needed.

So I have installed WFS 1.6.10 and so far see nothing to note . I get this notice opening a File that I was working on 2 years ago .
.
.

old file

Makes me wonder if my watchface really needs the BODY_SENSORS permission. I don’t use any of the health tags to display heart rates and such. Is this permission for user defined complications needed?

If not couldn’t Watch Face Studio remove the BODY_SENSORS permission if the tags were unused?

Policy announcement: July 17, 2024

We will require developers offering the following services to register as an Organization: financial, health, VPN, and government products and services. This is to promote transparency and continuity of critical and sensitive services. This update will be rolled out to new developer accounts first. Existing developers will receive more information this year.

The following rights are considered to be covered by sensitive health-related data (not an exhaustive list):

ACCESS_BACKGROUND_LOCATION
ACCESS_COARSE_LOCATION
ACCESS_FINE_LOCATION
ACTIVITY_RECOGNITION
BLUETOOTH_ADVERTISE
BLUETOOTH_CONNECT
BLUETOOTH_SCAN
***BODY_SENSORS***
BODY_SENSORS_BACKGROUND
CAMERA
READ_CALENDAR
READ_SMS
RECORD_AUDIO
SEND_SMS
WRITE_CALENDAR

If you request any of these permissions, your app must clearly disclose how it uses user data, describe the type of data that will be accessed, and obtain explicit consent user’s consent to the use of that data. You can see the full list of Android permissions and corresponding descriptions on the Android Developers site.

Health features in the app

Your app uses the android.permission.BODY_SENSORS permission and must meet the Health Apps policy requirements. If your app doesn’t have any health-related features, remove this permission from your app’s manifest

So the watch face developer must also register as an organization?

Since I synced a Couple of my own faces to my GW4 Classic it is running on Donkey Power . It has never been so Shit . Even with Facer it was never so Shit . What is this Decaritive nonsense Apparently it Foes Nothing . Looks like Samsung Bust thier own Shit .
.
.
.

Fewer devices supported - is this to be expected with the new sdk target?

It’s what renders WFF watch faces. So Samsung DWF in the battery usage list is basically your watch face :slight_smile:

1 Like

Thank you . Things obviously look a little different . :+1:

Well, I don’t want to sound rude but… 6 months of work to only support a new sdk. I guess they’re not investing that much energy into this project.

1 Like

Indeed. One year later of Watch Face Format 1 isn’t yet fully implemented while Watch Face Format 2 is already out.

1 Like

I am also disappointed how slow the implementation of the Watch Face Format in WFS is. But it isn’t fair in this case.

The API level thing was kind of a emergency release. I think what happened was that the WFS team took version 1.6.9, raised the API level and released it ASAP without any further changes.

I believe they are still hard at work to support the Watch Face Format and didn’t want to release any buggy or unfinished code. Just in time before the Google deadline hits at the end of July 2024. So we should be grateful. :slight_smile:

1 Like

With a face from WFS 1.6.10 my Battery Consumption has jumped to 7.5% ph before it was never more tha 3%ph . My old GW4 is now going to be charged twice a day .

Sadly same here, how come?

1 Like

New Watch Face Format . We are the Beta Testers . I hope things will improve . :+1::blush::grin::rofl:

1 Like

Short question to the developers who have already sent an update to Google for checking. Are they already approved? I got on July 23rd. submitted and it is still being checked. Unusually long …

I uploaded my recompiled watchface on July 23 and it was approved the very next day.