All complications are blank

[kellogg76]

Updated to latest version in the app store a few days ago, now all the complications for Watchla are blank on the watch. If I edit the watch face, the description of the complications has the text but no icons. Changing to another app's complication works, changing back to Range (for example) is blank again. Refresh watch app on the phone does nothing.

[dbgerhard]

I have this issue as well. When I tap on the blank space on my watch where the complication should be, it opens the Watchla watch app and things seem to work ok.

[kellogg76]

I have this issue as well. When I tap on the blank space on my watch where the complication should be, it opens the Watchla watch app and things seem to work ok.

Me too, but when I go back to the watch face by pressing the crown, the icons are all blank again. They seem to work when you go into the app but that doesn't get populated back to the complications.

[kellogg76]

Commenting to add that 3.5.2 released today doesn't fix anything.

[zunzster]

I found the issue is the background on all the Watchla Complications now show as mostly white (and hence barely viewable) when I have my Modular watchface with a rainbow background as opposed to black.

[itsMeDavidV]

This is a known issue and we are diligently working to address it. V3.5.2 addresses other issues raised. This will have its own update very shortly.

[AngryPotato99]

Watchla app compilations not showing on apple watch ultra 2

[claire078]

on 3.53 same to me. Battery status works, relevant vehicle status doesn’t. Phone+watch apps are up to date.

[claire078]

It seems to have been fixed over the weekend, thanks.

But not to me.

fyi Apple Watch and iPhone on 10.3, 17.3

[AngryPotato99]

Not fixed yet

[TeslaOwnerTips]

Latest app 3.5.5 (338) I deleted and installed again Turned both watch and phone off/shutdown then on Relevant vehicle status and sentry mode widgets blank.

First image relevant vehicle status blank. Second image sentry mode status not showing

[TeslaOwnerTips]

Not showing, just a grey circle Flash lights Honk horn Lock/unlock Open doors Open frunk I stopped checking

[kellogg76]

Are these issues being actively worked on? The functionality has really taken a massive hit in recent "updates". If the data in the complications isn't being updated there's not really much point to the app. It doesn't report correct range, the open charge port and home link don't work either.

More often than not I get the spinny wheel icon filling the whole screen and then nothing.

[mbvisiontt]

It’s April 10th and still the same issue??

Having bought the app, pretty annoying to have it not work properly for months now.

[CassandraMarie]

Hi @zunzster, @dbgerhard, @kellogg76, @claire078, @mbvisiontt, @TeslaOwnerTips, @AngryPotato99, we apologize for the late reply. Are you still experiencing this issue?

Complications should be visible with the latest version 3.8. You can check the version of both your iOS and watchOS by navigating to preferences and scrolling to the bottom of the screen.

[zunzster]

The complications are now visible when the background is not black for me so my issue is fixed.

[zunzster]

Hrmm... I'm still getting the issue that I needed to reauthenticate the watch app again (it seems to need that quite often - is that normal?) and after doing that, it seems connected to my tesla, but when I go into preferences to select vehicles to view my wife's tesla, no vehicles are listed so I can't switch. That used to be quite useful prior to the rewrite to unlock her charging port.

The phone app can see both vehicles - but the watch app 'select vehicle' screen can't. No vehicles are listed, not even the one it's connected to. I selected Refresh watch app in the Phone app and that doesn't fix it either so I don't know how to fix this.

[mbvisiontt]

Hi,Yes they are visible, but NO, they are not updating (km indicator stuck on 240km, no matter what the real value is).Thanks for fixing this in the next update.BR, mbvisionttOp 2 aug 2024 om 02:19 heeft Cassandra Marie @.***> het volgende geschreven: Hi @zunzster, @dbgerhard, @kellogg76, @claire078, @mbvisiontt, @TeslaOwnerTips, @AngryPotato99, we apologize for the late reply. Are you still experiencing this issue? Complications should be visible with the latest version 3.8. You can check the version of both your iOS and watchOS by navigating to preferences and scrolling to the bottom of the screen.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[CassandraMarie]

@zunzster, We believe you may be experiencing a known authentication issue. Could you please send your email and mention this GitHub issue via https://watchla.app/contact/. Thank you

[CassandraMarie]

Hi @mbvisiontt, Could you please confirm that you are using version 3.8.1 of Watchla?

[mbvisiontt]

Confirmed. 3.8.1 since 2 months.Also did “refresh watch app” to no avail.Op 6 aug 2024 om 04:46 heeft Cassandra Marie @.***> het volgende geschreven: Hi @mbvisiontt, Could you please confirm that you are using version 3.8.1 of Watchla?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[mbvisiontt]

And I just fully powered off and back on my phone and Watch, no solution.Also authenticated Watch app again, no solution.Op 6 aug 2024 om 06:03 heeft Martijn @.> het volgende geschreven:Confirmed. 3.8.1 since 2 months.Also did “refresh watch app” to no avail.Op 6 aug 2024 om 04:46 heeft Cassandra Marie @.> het volgende geschreven: Hi @mbvisiontt, Could you please confirm that you are using version 3.8.1 of Watchla?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[mbvisiontt]

And… I just tried to switch the complication to range % and it was blank!! Nothing visible. Switched back to km complication and is visible but frozen on 240km as before.😕😕😕Op 6 aug 2024 om 06:11 heeft Martijn @.> het volgende geschreven:And I just fully powered off and back on my phone and Watch, no solution.Also authenticated Watch app again, no solution.Op 6 aug 2024 om 06:03 heeft Martijn @.> het volgende geschreven:Confirmed. 3.8.1 since 2 months.Also did “refresh watch app” to no avail.Op 6 aug 2024 om 04:46 heeft Cassandra Marie @.***> het volgende geschreven: Hi @mbvisiontt, Could you please confirm that you are using version 3.8.1 of Watchla?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[CassandraMarie]

@mbvisiontt, Can you send over your support code via https://watchla.app/contact/ so we can investigate your case?

Support codes can be found by going to Preferences > Support/ Feedback > Support code Please be sure to link to this issue when you reach out.

[mbvisiontt]

Hi,This is: [redacted]hanks.Op 6 aug 2024 om 19:54 heeft Cassandra Marie @.***> het volgende geschreven: @mbvisiontt, Can you send over your support code via https://watchla.app/contact/ so we can investigate your case? Support codes can be found by going to Preferences > Support/ Feedback > Support code Please be sure to link to this issue when you reach out.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[pymiras]

Same here. All complications are blank. Very annoying. Are you still working on the app? This issue is open since January...

[mbvisiontt]

Hi,Not working still either… either blank or showing wrong value and not updating it.I shared my code from the app but heard nothing afterwards..! Please update and fix.Op 15 sep 2024 om 16:04 heeft pymiras @.***> het volgende geschreven: Same here. All complications are blank. Very annoying. Are you still working on the app? This issue is open since January...

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[CassandraMarie]

Hi @mbvisiontt, You seem to be using version 3.8.2, please update both of your devices to version 3.8.3. Which contains background efficiency improvements that directly relate to your issue. Additionally, Watchla has registered your vehicle has been either slow to respond or slow to wake on different occasions. This is most likely due to the vehicle's internet connection and/or being in a state of sleep for an extended period of time.

[mbvisiontt]

Hi,It seems to be working at this point, I’m on 3.8.3. It has been working before for very short periods, so let’s hope it keeps working this time! ☺️Op 17 sep 2024 om 01:35 heeft Cassandra Marie @.***> het volgende geschreven: Hi @mbvisiontt, You seem to be using version 3.8.2, please update both of your devices to version 3.8.3. Which contains background efficiency improvements that directly relate to your issue. Additionally, Watchla has registered your vehicle has been either slow to respond or slow to wake on different occasions. This is most likely due to the vehicle's internet connection and/or being in a state of sleep for an extended period of time.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[CassandraMarie]

@mbvisiontt, Good news! If you run into any more issues please reach out to us via https://watchla.app/contact/.

[mbvisiontt]

Hi,Again the watch face isn’t updating, very disappointing for a paid app. Please check. Op 24 sep 2024 om 04:25 heeft Cassandra Marie @.***> het volgende geschreven: @mbvisiontt, Good news! If you run into any more issues please reach out to us via https://watchla.app/contact/.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[CassandraMarie]

Hi @mbvisiontt, Could you send over your support code via https://watchla.app/contact/ so we can investigate your case?

[mbvisiontt]

Hi,It’s still the same issue as before… you got all the info from me in orevious mails under this case?!Op 8 nov 2024 om 18:49 heeft Cassandra Marie @.***> het volgende geschreven: Hi @mbvisiontt, Could you send over your support code via https://watchla.app/contact/ so we can investigate your case?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[CassandraMarie]

Yes, I have your previous support code; however, support codes can sometimes change during updates. Since it’s been a few months, I wanted to confirm that we are looking into the correct one. Additionally are both of your devices up to date with the latest update, 3.9.2?

[mbvisiontt]

Hi,Yes both latest versions, problem persists. Logged out and in, changed complication and back, restarted both devices, resfreshed watch app. To no avail.Support code now says: MsKmgQuQx0Thx. Op 8 nov 2024 om 19:16 heeft Cassandra Marie @.***> het volgende geschreven: Yes, I have your previous support code; however, support codes can sometimes change during updates. Since it’s been a few months, I wanted to confirm that we are looking into the correct one. Additionally are both of your devices up to date with the latest update, 3.9.2?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[CassandraMarie]

Hi @mbvisiontt, we recently released an update that addresses complications. After reviewing your support code we noticed you are using an older version. Please update to 3.9.3 which addresses issues where complications may not be updated. Please reach back out if the issue persists. Thank you.

[mbvisiontt]

Hi,I’m on 3.9.3 both on phone and watch, problem persists.Op 11 nov 2024 om 21:10 heeft Cassandra Marie @.***> het volgende geschreven: Hi @mbvisiontt, we recently released an update that addresses complications. After reviewing your support code we noticed you are using an older version. Please update to 3.9.3 which addresses issues where complications may not be updated. Please reach back out if the issue persists. Thank you.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[CassandraMarie]

When you open Watchla on your watch, does the vehicle data appear to be up to date?

[mbvisiontt]

Yes, that part seems to work well. Always has actually.Op 11 nov 2024 om 21:37 heeft Cassandra Marie @.***> het volgende geschreven: When you open Watchla on your watch, does the vehicle data appear to be up to date?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[CassandraMarie]

Hi @mbvisiontt, Could you let me know which complication isn’t updating and how accurate the displayed value is? For example, would you say the information is only slightly out of date or significantly inaccurate? Could you please include the values?

[zunzster]

I have 3.9.3 and the watch app shows 98% and the complication still shows 94% - which would be from when the Tesla was charging it last night.

[mbvisiontt]

Hi,Values are completely off. Whether I change vehicles, doesn’t matter either; it has value 118 km currently, was from a car that once had that. If I switch to another that has 423, nothing happens. Still says 118.Only once every week or so (if I’m lucky), currently I’m not and 118 has been there longer, the value changes.Op 12 nov 2024 om 06:24 heeft Cassandra Marie @.***> het volgende geschreven: What complication and how far off is the data? Would you say it’s only slightly off or significantly inaccurate? Could you please include the values?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[itsMeDavidV]

Hi @mbvisiontt & @zunzster we made some changes to better address the issue of complications being slightly off (eg: shown range 195, actual range 200)

Please let us know if you see this behavior corrected over the next day or so or if you still see this unintended behavior persist.

[mbvisiontt]

Hi,Mine was way off, or better: not updated for days/weeks, and still is for now.Op 13 nov 2024 om 03:56 heeft David Villegas @.***> het volgende geschreven: Hi @mbvisiontt & @zunzster we made some changes to better address the issue of complications being slightly off (eg: shown range 195, actual range 200) Please let us know if you see this behavior corrected over the next day or so or if you still see this unintended behavior persist.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[mbvisiontt]

I just realised: I think my complication completely stopped working (to be clear: it was already bogus most of the time) when I added a 3rd car to my account.Please look into that if that explains something.Op 13 nov 2024 om 09:07 heeft Martijn @.> het volgende geschreven:Hi,Mine was way off, or better: not updated for days/weeks, and still is for now.Op 13 nov 2024 om 03:56 heeft David Villegas @.> het volgende geschreven: Hi @mbvisiontt & @zunzster we made some changes to better address the issue of complications being slightly off (eg: shown range 195, actual range 200) Please let us know if you see this behavior corrected over the next day or so or if you still see this unintended behavior persist.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[mbvisiontt]

I haven’t heard from you?I also experience the Watch complications resetting to the car with the lowest alphabet letter, so always to the D, whilst I select car names that begin with an M or W. Very annoying.Op 17 nov 2024 om 19:44 heeft Martijn @.> het volgende geschreven:I just realised: I think my complication completely stopped working (to be clear: it was already bogus most of the time) when I added a 3rd car to my account.Please look into that if that explains something.Op 13 nov 2024 om 09:07 heeft Martijn @.> het volgende geschreven:Hi,Mine was way off, or better: not updated for days/weeks, and still is for now.Op 13 nov 2024 om 03:56 heeft David Villegas @.***> het volgende geschreven: Hi @mbvisiontt & @zunzster we made some changes to better address the issue of complications being slightly off (eg: shown range 195, actual range 200) Please let us know if you see this behavior corrected over the next day or so or if you still see this unintended behavior persist.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>