Finally, I got a workaround.
This thread was quite helpful.
https://developer.apple.com/forums/thread/123624
I just set these observer in awake function,
NotificationCenter.default.addObserver(
self,
selector: #selector(self.applicationDidBecomeActive),
name: WKExtension.applicationDidBecomeActiveNotification,
object: nil
)
thus, wrote callback for restore previous state like this.
func applicationDidBecomeActive()
{
if (PlayingRecord.currentHole == self.holeNum) {
self.becomeCurrentPage()
self.updateView()
}
}
I hope this would be someone's help.
vimtaku
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Post
Replies
Boosts
Views
Activity
Unfortunately, my user told me that the problem was still alive.... Do you have any solution?
I'll try a binary search debugging.
My app user who met the issue told me a workaround of this problem. If she turn off wrist detection feature on, the problem will be resolved. I'd like to resolve this problem by writing program. Do you have any clue of this problem?
My app user who met the issue told me a workaround of this problem. If she turn off wrist detection feature on, the problem will be resolved.
I'd like to resolve this problem by writing program. Do you have any clue of this problem?
My user who met this issue told me a workaround of this problem.
If she turn on wrist detection in the passcode menu of WatchOS, the problem disappear.
However, it's of course a workaround. Do you have any clues to resolve the issue by writing program?
I'm also facing a similar issue.
I have released counter app from last year.
Some users told me a problem about connection between iOS and watch OS.
She is using iPhone8 14.0.1 and AppleWatchSeries3 WatchOS 7.0.3 .
She updated iOS and Watch OS version and the problem happened.
My iPhone and watch(iPhone11 iOS14.0.1, Applewatch Series4 WatchOS7.0.2) have not seen this connection problem.
And also a simulator working fine.
I supplied a testflight debug version that shows connectivity on iOS to the user.
After that, the user told me that hers iOS app showed always unreachable.
Does anyone have a solution?
IMO, WatchSeries3 + watchOS7 is not good combination.