watchOS 5 contentSafeAreaInsets always zero
up vote
0
down vote
favorite
I might be missing something super obvious, but running an app compiled against watchOS 5 on the Apple Watch Series 4 simulator always results in the contentSafeAreaInsets and systemMinimumLayoutMargins returning zero (zero for left/right/top/bottom).
I've tried creating a sample project in case it was something weird in my app, but no luck.
The docs state:
The system’s built-in containers and controls automatically use the
content-safe area insets; however, if you build a custom user
interface with SpriteKit or SceneKit, you should check the
contentSafeAreaInsets and systemMinimumLayoutMargins, and lay out your
interface accordingly.
So I've tried adding a SceneKit scene to the Storyboard but that's had no effect, even when launching all permutations of the "full screen" and "fixed to screen edges" options enabled and disabled:
Edit: If I background and foreground the app the values are reported successfully, which makes me believe this could be a bug in watchOS if there's no workaround. It seems unreasonable to expect a user to background and foreground an app to get the correct behaviour.
watchkit watch-os-5
asked Nov 11 at 13:33
Kane Cheshire
1,0241016
add a comment |
up vote
0
down vote
favorite
I might be missing something super obvious, but running an app compiled against watchOS 5 on the Apple Watch Series 4 simulator always results in the contentSafeAreaInsets and systemMinimumLayoutMargins returning zero (zero for left/right/top/bottom).
I've tried creating a sample project in case it was something weird in my app, but no luck.
The docs state:
The system’s built-in containers and controls automatically use the
content-safe area insets; however, if you build a custom user
interface with SpriteKit or SceneKit, you should check the
contentSafeAreaInsets and systemMinimumLayoutMargins, and lay out your
interface accordingly.
So I've tried adding a SceneKit scene to the Storyboard but that's had no effect, even when launching all permutations of the "full screen" and "fixed to screen edges" options enabled and disabled:
Edit: If I background and foreground the app the values are reported successfully, which makes me believe this could be a bug in watchOS if there's no workaround. It seems unreasonable to expect a user to background and foreground an app to get the correct behaviour.
watchkit watch-os-5
asked Nov 11 at 13:33
Kane Cheshire
1,0241016
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I might be missing something super obvious, but running an app compiled against watchOS 5 on the Apple Watch Series 4 simulator always results in the contentSafeAreaInsets and systemMinimumLayoutMargins returning zero (zero for left/right/top/bottom).
I've tried creating a sample project in case it was something weird in my app, but no luck.
The docs state:
The system’s built-in containers and controls automatically use the
content-safe area insets; however, if you build a custom user
interface with SpriteKit or SceneKit, you should check the
contentSafeAreaInsets and systemMinimumLayoutMargins, and lay out your
interface accordingly.
So I've tried adding a SceneKit scene to the Storyboard but that's had no effect, even when launching all permutations of the "full screen" and "fixed to screen edges" options enabled and disabled:
Edit: If I background and foreground the app the values are reported successfully, which makes me believe this could be a bug in watchOS if there's no workaround. It seems unreasonable to expect a user to background and foreground an app to get the correct behaviour.
watchkit watch-os-5
asked Nov 11 at 13:33
Kane Cheshire
1,0241016
I might be missing something super obvious, but running an app compiled against watchOS 5 on the Apple Watch Series 4 simulator always results in the contentSafeAreaInsets and systemMinimumLayoutMargins returning zero (zero for left/right/top/bottom).
I've tried creating a sample project in case it was something weird in my app, but no luck.
The docs state:
The system’s built-in containers and controls automatically use the
content-safe area insets; however, if you build a custom user
interface with SpriteKit or SceneKit, you should check the
contentSafeAreaInsets and systemMinimumLayoutMargins, and lay out your
interface accordingly.
So I've tried adding a SceneKit scene to the Storyboard but that's had no effect, even when launching all permutations of the "full screen" and "fixed to screen edges" options enabled and disabled:
Edit: If I background and foreground the app the values are reported successfully, which makes me believe this could be a bug in watchOS if there's no workaround. It seems unreasonable to expect a user to background and foreground an app to get the correct behaviour.
watchkit watch-os-5
watchkit watch-os-5
asked Nov 11 at 13:33
Kane Cheshire
1,0241016
asked Nov 11 at 13:33
Kane Cheshire
1,0241016
edited Nov 11 at 14:27
asked Nov 11 at 13:33
Kane Cheshire
1,0241016
asked Nov 11 at 13:33
Kane Cheshire
1,0241016
asked Nov 11 at 13:33
Kane Cheshire
1,0241016
1,0241016
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53249256%2fwatchos-5-contentsafeareainsets-always-zero%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
