KWGT Giving Missing Requirements Error For Fitness Data

Tried hit “Fix” but nothing happens. All permissions have been given and everything seems to work, but would be nice to clear the error. Any ideas please?

S24 Ultra
Android 14 One UI 6.1
KWGT 3-77b432414

I’m getting this issue in KLWP as well. When I open KLWP, the permission comes up. I tap fix and then the dialogue box just comes up again. This will happen over and over. I have all permissions allowed in Health Connect. This began for me after the update to 3.77. I have a Pixel 6a with Android 14.

Additionally, I went to see if activity time would work. When attempting to add text showing this, I would get a dialogue when tapping on fitness data that told me I did not have the permission. I had an option to manage permissions and that actually took me to the permissions for KLWP in settings, where I verified everything is allowed. KLWP would not allow me into the fitness data section for the text. Hopefully this information helps the developer. Let me know if any clarification is needed.

I am working on this, will fix ASAP

2 Likes

There Is exaclyvthe same issue on KWCH.

Regards
KZM

I have issue with fitness data exactly like OP in KWGT.
My device also exactly like OP.

Yup same issue, I have a Samsung A35 and it keeps preventing me from creating those widgets(I’m using the free version of the app)

Don’t worry. It Is months that i reported this in KWCH. I have noticed this error in KLWP too.
I doubt they Will care to fix.

Wait to pay until they will fix It.
(And probably now i’ll be kicked off)

Regards
KZM

1 Like

The pop up no longer appears in KWGT, not exactly sure how, as as far as I can see no update to app or any other changes made.

Watch software got an update, possibly related as I use KWCH on it and fitness data used by both.

Just taken.
The message Is still there and if i fix the modal doesn’t disappear.

Latest Version.

Bye.

Regards
KZM

I’m not saying the issue has been resolved, just on my devices I’m no longer getting the pop up. I was simply providing information the dev may find helpful as it seems to be an issue across all his apps.