Complication not updating after 5 days

Question

Created Feb ’21

Replies 4

Boosts 0

Participants 2

I have developed a Watch app that features a complication.
It updates every minute and runs happily for 5 or 6 days, then stops updating. I.e. getTimelineEntries stops being called.
I have tried to replicate the issue using the simulator but it updates without problems. Has anyone else seen this problem? Any idea how to debug it without waiting a week or is this likely to be a device side bug?

Answered by alisdair_little in 661278022

Hi, and thanks for the reply. The app tells the time in German. As such it needs to update every minute.

The logging profile you have sent says it will expire after 3 days and I am only seeing the issue after 5-6 days.
Does this mean I will have to re-enable it after it expires?

If needed I can provide you the full source for the app to debug/profile locally.

Boost

Answer 1

Frameworks Engineer OP

Apple

Feb ’21

Hello! Can you please file Feedback with a sysdiagnose (see https://download.developer.apple.com/iOS/watchOS_Logs/sysdiagnose_Logging_Instructions.pdf) and a sample project? Thanks!

One thing to note is that if you're attempting to update your complication every minute, you're likely exhausting your BAR budget rather quickly. However, without understanding what your app and complication are doing, it's hard to diagnose without the information above.

0

Answer 2

alisdair_little OP

Feb ’21

Accepted Answer

Hi, and thanks for the reply. The app tells the time in German. As such it needs to update every minute.

The logging profile you have sent says it will expire after 3 days and I am only seeing the issue after 5-6 days.
Does this mean I will have to re-enable it after it expires?

If needed I can provide you the full source for the app to debug/profile locally.

0

Answer 3

alisdair_little OP

Feb ’21

I have the sysdiagnose tar and some source to share. What is the best way to get you the files?

0

Answer 4

alisdair_little OP

Feb ’21

I accidentally clicked solved but I still need to share the debug info and source! Hopefully an engineer will still pick up.

0