SwiftUI's onAppear acting differently on Watch 10 devices

Question

james_ma OP

Created Jan ’24

Replies 1

Boosts 0

Participants 1

Hi,

with the recent watchOS10 update, I have found a strange behavior on watchos10 devices.

Before watchOS10, fullScreenCovers on a view, when being dismissed, did not trigger the onAppear function of the underlying view, to which the fullScreenCover is attached to.

However, on watchOS 10.2 devices, I have noticed that onAppear is triggered in the same situation. Thus my app is showing unexpected behavior.

On a simulator, the onAppear is acting as before but the new behavior is seen on real devices.

Could this be a change to the onAppear mechanism on Apple watch devices? Or would this be a bug?

Boost

Answer 1

james_ma OP

Jan ’24

On further testing, I've found out behavior patterns for the following versions

watchos10.2 & actual device, watchos10.2 & simulators -> onAppear is called when a View shows after a fullScreenCover disappears
watchos10.0 & simulator -> onAppear is NOT called when a View shows after a fullScreenCover disappears
watchos9.4 & simulator -> onAppear is NOT called when a View shows after a fullScreenCover disappears

so for me, this issue seems to have appeared on watchos 10.2

0