Complications not showing in Wearable App

Yes I spoke too soon. It was only health complications the ones and I think Short Text and Long Text complications the icons are missing.
And all other complications

Ron

@amoledwatchfaces and @r.liechty_SDR my watch still cant select complications from wearable app?

Gw 5 pro

Why the wearable app only shows complication for certain watch/update.

Should they fixed it at the app level not the watch?

Itā€™s the second update this year, that after the update the complications are not visible.
It is no longer understandable that Samsung is not testing these functions sufficiently. And then the next update will take that long.

2 Likes

iā€™m a little confused about the update. in the google play store it says the app was last updated Oct 25, which i know is not right. the samsung galaxy store says it was last updated Nov 17. both places show the same version number, which also matches the version number on my phone, but my phone says it was last updated Jan 4 (google play store). :man_shrugging:

I understand and I am trying to do my best to bring the developers voice heard by the teams that are affected.

It appears that the system update was mainly for health and had nothing to do with the complications. I jumped the gun on that

Ron
Samsung Developer Relations

Iā€™ve got the exact same problem on my Watch6 Classic: I updated the firmware to AWK4, and the Wearables app on my phone has updated itself to 2.2.57.23102461 and my ā€œcircleā€ complication slot now only shows ā€œNoneā€ and the ā€œSamsung Healthā€ complications - identical to the screenshot above - but not all the other complications (such as weather) that are supported in this slot.

Desperately hoping the Samsung devs will patch this bug soon!

@r.liechty_SDR do we have any update for this? Currently itā€™s ruining apps ranking / decreasing average rating a lotā€¦

I will ask if they have an ETA on the fix. It may be something that required changes elsewhere.

Ron

1 Like

@amoledwatchfaces Iā€™d recommend you put some type of notification in your apps and/or your website. I installed several of your watch faces including a paid one and the complications did not work. I didnā€™t see anything in the app descriptions or your website to indicate their is an issue affecting 3rd party watch faces. It took me some time to find this thread and other customers will probably leave a 1 star review or keep sending you emails. Reading this thread, I can see this is clearly a Samsung issue and it looks like they are aware and working on a fix. It will help your revenue and reputation to make sure that information gets passed on to customers. That said, waiting for a fix so I can fully enjoy Simple Digital!

Problem is, I have 100+ watch face portfolio updated with latest WFS. Itā€™s not an easy job to update all descriptions and then, after fix, remove disclaimers again. It doesnā€™t make sense.

This is so frustrating, Itā€™s already one month with the issue (27 Oct -->)
Iā€™ve tried my best to notify Samsung about it. Now we need to wait. It took Google less than 20 days to fix this from the day they introduced it. Hopefully we wont wait for fix like 3-4 months which is, unfortunately, for Samsung, normal.

Iā€™ll soon update webpage but majority of users are not reading website / store description.

4 Likes

The website update looks good and probably the best you can do for now. Now we wait for Samsungā€¦

@jdutton @amoledwatchfaces

I would advise against posting that this was a Samsung Galaxy Wearable error.

Ron
Samsung Developer Relations

Well, it happens only in Galaxy Wearable app and only for Samsung devices so it is clear that the error is visible or noticeable in the Galaxy Wearable app. I have to do something, Iā€™m sorry about this. Samsung forced devs (if they wanted to keeps watch faces updated) to rebuild with latest WFS (1.4.20 / 1.5.7) by removing older WFS 1.3.13 download link.

Every day, for about 3 weeks now, Iā€™m solving like 20+ negative emails where users asks why this is not working and that it started with Galaxy Wearable update. Also, receiving tons of 1-star review for something I canā€™t fix.

Itā€™s only damage control I can do.

Tomas

6 Likes

Can you explain why? Because it literally is a Samsung Wearable error. The bug is caused by the Samsung Wearable app, it only exists on Samsung watches, and only Samsung can fix it. Why should watch face designers like @amoledwatchfaces not truthfully inform their customers that this is Samsungā€™s problem and Samsung needs to fix it? Why should they take the blame for something that Samsung is dragging its feet over?

Sorry but this kind of response is not helpful. Samsung needs to take ownership, and more importantly, Samsung needs to release an urgent hotfix quickly.

3 Likes

Because I was told that this was actually a Google SDK error. I heard today that Google has corrected it and there should be a solution soon.

Ron
Samsung Developer Relations

I donā€™t know whose fault this is, but mistakes like this really are a lawsuit material. Developers such as amoledwatchfaces have financial damage because of this. If this really is Googleā€™s fault, then someone who they listen to (maybe, you, Samsung) should tell them to get their shit together.

I wouldnā€™t say that. We all should be thankful for what Samsung / Google provided us to unleash our creativity.

Itā€™s how this field works. It is difficult for an ordinary person to recognize where the error is. When the fault is only associated with a certain watch face, user is convinced that the fault lies with the watch face.

Many things could be improved. For example,

  1. I donā€™t think there is some initial guide on Galaxy Watches to show user that he can also customize watch faces directly on watch. Thus, from my experience a lot of users think that only way to customize watch face is through Wearable app.
  2. More frequent hotfix / bugfix updates for some core services like Galaxy Manager / Wearable app.
  3. Some bug / issue notice directly in the Wearable app, maybe push notification to give notice to the user that something is not working atm and it will be fixed soon.

We third-party developers are literally dependent on the functionality of Samsung applications like Manager / Wearable. This should be taken into account and if any error appears, it should be corrected immediately, and not after two months.

4 Likes

@amoledwatchfaces @matze_styles4you @Ballozi @SGWatchDesign @Peter @MergeLabs @Raydesign @Osman @russellcresser @rzrshrpstudio

For Samsungā€™s problems, itā€™s Googleā€™s fault.
For Googleā€™s problems, itā€™s Samsungā€™s fault.

For problems on watch faces, itā€™s always the designers/developersā€™ fault.

When (every day) I receive complaints and negative reviews about things that I cannot fix myself, I have gotten into the habit of telling users that Google & Samsung, depending on the bugs found, are directly responsible.

After two years of feeling offended by users, Iā€™m tired of acting as a filter for all these issues.

I have always worked meticulously and I want users to understand that I am not stupid enough to release apps with these bugs.

BTW, I have always supported Samsung and have always thanked them publicly for the great opportunity they gave us with GWD and WFS.

I remain of the opinion that Samsung made the biggest mistake in relying on Google for the new generation of smart watches.

Note: I hope this post also doesnā€™t get deleted like a previous post of mine where I was expressing my opinions, about 2 months ago. This is one of the reasons why they are also distancing me from this forum.

I add: in the golden days of the Galaxy Store, I released 2/3 watch faces a week with great enthusiasm. Now Iā€™m having a hard time even drawing a layout with 2 lines and 3 circles with all these messes.

9 Likes

It doesnā€™t matter what the original source of the error is. What matters is that the bug was introduced with an update to the Samsung Wearable app, which Samsung is responsible for, and it will presumably be fixed by Samsung with a future update to the Samsung Wearable app.

Samsung, and Samsung alone, is responsible for testing their apps before releasing them. Samsungā€™s Quality Assurance Engineers should have noticed that the complications were broken in the new version of the app before they released the app to the public. Whether the source of this is from a third-party SDK is immaterial.

Nobody here expects Samsung to be perfect, of course. Bugs happen. But itā€™s not helpful to try and pass the buck on to Google, when Google isnā€™t the company responsible for the Samsung Wearable app on Samsung phones and Samsung watches. :slight_smile:

2 Likes

Well thank you @Matteo_Dini for your Heart felt Message . Please do not despair and give up . It will get better . I spend quite a bit of time with Facer and improvements are being made . It is complicated and there is a Lot at stake . I am Grateful to Samsung for their Platform and the opportunity to make decent faces for lots of watches free .

3 Likes