WKExtendedRuntimeSession not starting

Question

Created May ’21

Replies 2

Boosts 0

Participants 2

It's late and I'm hoping I'm doing something really stupid. I'm trying to keep my watch app running without user interaction for a total of 45 minutes (this is a referee timer for a niche sport).

I'm trying to make use of WKExtendedRuntimeSession, after reading through the Apple documentation, and finding some samples online. It appeared people were finding this as simple as;

var session = WKExtendedRuntimeSession()

session.start() and session.invalidate()

I am testing from buttons for now, but I get nothing from session.start() at all. The button with session.invalidate() gives me an error in the console that there isn't a session running.

Where am I going wrong?

Boost

Answer 1

Frameworks Engineer OP

Apple

May ’21

What kind of extended runtime session are you trying to use? A referee timer does not naturally fit into any of the use cases (Self Care, Mindfulness, Physical Therapy, or Smart Alarm) for which this API is available.

0

Answer 2

Lihp8270 OP

May ’21

Thanks for your reply.

I was using it as Physical Therapy as this is the closest use case.

Unless I’m missing something though the only other option for keeping it running when the wrist is lowered or has no user action is as a workout.

However, I do not want to run any of the sensors as if this is a workout so I was avoiding using the Health Kit API.

0