Black status bar on the iPad Pro with rounded corners
My app always runs in compatibility mode on the new iPad Pro Simulator. I've installed the latest Xcode 10.1. I've verified it is linked against the latest iOS 12.1. When I run it on an iPhone XS, it correctly uses Safe area insets. Yet it shows a black status bar and a black stripe at the bottom where the Home indicator is located.
Even when I create a sample app with Xcode 10.1 and run it on the iPad Pro Simulator, it is launched in compatibility mode:
How to make the app use the whole screen?
ios xcode ipad xcode10 ios12
asked Nov 8 '18 at 12:52
Vladimir GrigorovVladimir Grigorov
7,24574654
add a comment |
My app always runs in compatibility mode on the new iPad Pro Simulator. I've installed the latest Xcode 10.1. I've verified it is linked against the latest iOS 12.1. When I run it on an iPhone XS, it correctly uses Safe area insets. Yet it shows a black status bar and a black stripe at the bottom where the Home indicator is located.
Even when I create a sample app with Xcode 10.1 and run it on the iPad Pro Simulator, it is launched in compatibility mode:
How to make the app use the whole screen?
ios xcode ipad xcode10 ios12
asked Nov 8 '18 at 12:52
Vladimir GrigorovVladimir Grigorov
7,24574654
@matt - you tell me. It's a plain vanilla Single View app with the background color set to green.
– Vladimir Grigorov
Nov 9 '18 at 9:35
Can you post a sample project? I still can't reproduce the issue on the 11-inch or the 12-inch 3rd gen simulator. Have you restarted the computer? Cleaned out derived data? Deleted all simulators and recreated them? Those are all things I always do whenever there's an Xcode upgrade.
– matt
Nov 9 '18 at 21:36
add a comment |
My app always runs in compatibility mode on the new iPad Pro Simulator. I've installed the latest Xcode 10.1. I've verified it is linked against the latest iOS 12.1. When I run it on an iPhone XS, it correctly uses Safe area insets. Yet it shows a black status bar and a black stripe at the bottom where the Home indicator is located.
Even when I create a sample app with Xcode 10.1 and run it on the iPad Pro Simulator, it is launched in compatibility mode:
How to make the app use the whole screen?
ios xcode ipad xcode10 ios12
asked Nov 8 '18 at 12:52
Vladimir GrigorovVladimir Grigorov
7,24574654
My app always runs in compatibility mode on the new iPad Pro Simulator. I've installed the latest Xcode 10.1. I've verified it is linked against the latest iOS 12.1. When I run it on an iPhone XS, it correctly uses Safe area insets. Yet it shows a black status bar and a black stripe at the bottom where the Home indicator is located.
Even when I create a sample app with Xcode 10.1 and run it on the iPad Pro Simulator, it is launched in compatibility mode:
How to make the app use the whole screen?
ios xcode ipad xcode10 ios12
ios xcode ipad xcode10 ios12
asked Nov 8 '18 at 12:52
Vladimir GrigorovVladimir Grigorov
7,24574654
asked Nov 8 '18 at 12:52
Vladimir GrigorovVladimir Grigorov
7,24574654
edited Nov 16 '18 at 10:23
Vladimir Grigorov
asked Nov 8 '18 at 12:52
Vladimir GrigorovVladimir Grigorov
7,24574654
asked Nov 8 '18 at 12:52
Vladimir GrigorovVladimir Grigorov
7,24574654
asked Nov 8 '18 at 12:52
Vladimir GrigorovVladimir Grigorov
7,24574654
7,24574654
@matt - you tell me. It's a plain vanilla Single View app with the background color set to green.
– Vladimir Grigorov
Nov 9 '18 at 9:35
Can you post a sample project? I still can't reproduce the issue on the 11-inch or the 12-inch 3rd gen simulator. Have you restarted the computer? Cleaned out derived data? Deleted all simulators and recreated them? Those are all things I always do whenever there's an Xcode upgrade.
– matt
Nov 9 '18 at 21:36
add a comment |
@matt - you tell me. It's a plain vanilla Single View app with the background color set to green.
– Vladimir Grigorov
Nov 9 '18 at 9:35
Can you post a sample project? I still can't reproduce the issue on the 11-inch or the 12-inch 3rd gen simulator. Have you restarted the computer? Cleaned out derived data? Deleted all simulators and recreated them? Those are all things I always do whenever there's an Xcode upgrade.
– matt
Nov 9 '18 at 21:36
@matt - you tell me. It's a plain vanilla Single View app with the background color set to green.
– Vladimir Grigorov
Nov 9 '18 at 9:35
@matt - you tell me. It's a plain vanilla Single View app with the background color set to green.
– Vladimir Grigorov
Nov 9 '18 at 9:35
Can you post a sample project? I still can't reproduce the issue on the 11-inch or the 12-inch 3rd gen simulator. Have you restarted the computer? Cleaned out derived data? Deleted all simulators and recreated them? Those are all things I always do whenever there's an Xcode upgrade.
– matt
Nov 9 '18 at 21:36
Can you post a sample project? I still can't reproduce the issue on the 11-inch or the 12-inch 3rd gen simulator. Have you restarted the computer? Cleaned out derived data? Deleted all simulators and recreated them? Those are all things I always do whenever there's an Xcode upgrade.
– matt
Nov 9 '18 at 21:36
add a comment |
2 Answers
2
active
oldest
votes
I was seeing the same issue simply by creating a fresh iOS app using the Single View app or the Master-Detail app templates.
I got it working as expected by doing the following:
I deleted all versions of Xcode installed on my computer. I went to my ~/Library/Developer/Xcode folder and I deleted the following:
- All files named
DeveloperPortal* - The
DerivedDatafolder - The
Installsfolder (which just had some empty folders in it) - Under
UserData/IB SupportI deleted theSimulator Devicesfolder
Then I did a fresh download and install of Xcode 10.1 from the App Store.
After that, a clean build of the test app worked as expected. I don't know which of the above steps was really needed but I got it working.
answered Nov 14 '18 at 19:01
rmaddyrmaddy
245k27324388
Delete Xcode and install it again + delete DerivedData fixed the problem for me. Somehow the old installation of Xcode 10.1 kept on linking the projects with iOS 12.0 and that was the problem.
– Vladimir Grigorov
Nov 16 '18 at 10:22
As the answer indicated, simply upgrading to Xcode10.1 and removing ** DerivedData** did not work for me. I happened to have access to another laptop with brand new Mojave & Xcode10.1 installed, then it just worked.
– Wei WANG
Dec 10 '18 at 5:13
@WeiWANG I'm not sure I understand the point of your comment here. My answer does not simply say to upgrade to 10.1 and remove DerivedData. No one ever said that would solve the problem. And of course a fresh install of macOS and Xcode 10.1 works. My answers explains how I was able to get it working when starting from an existing installation of macOS and Xcode 10.0. I required several steps of cleanup, then installing Xcode 10.1.
– rmaddy
Dec 10 '18 at 15:08
@rmaddy You did misunderstood... :-) my bad though. I just wanted to back up your answer that simply upgrading will not work.
– Wei WANG
Dec 10 '18 at 21:45
add a comment |
I tried the above answer and it did not fix my problem. I did fix my problem by setting a .storyboard file as my Launch Screen File in Project->Target->General. Previously, I had been using Launch Images for my splash screen.
This is mentioned in the "Optimizing Your UI" section here: https://developer.apple.com/ipad/
answered Nov 26 '18 at 16:41
ryanrrryanrr
265
Based on the screenshots in the question, the OP is already using a Launch screen storyboard so my answer didn't address that. Without that storyboard, the black bars are much bigger.
– rmaddy
Dec 10 '18 at 15:03
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
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%2f53208148%2fblack-status-bar-on-the-ipad-pro-with-rounded-corners%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I was seeing the same issue simply by creating a fresh iOS app using the Single View app or the Master-Detail app templates.
I got it working as expected by doing the following:
I deleted all versions of Xcode installed on my computer. I went to my ~/Library/Developer/Xcode folder and I deleted the following:
- All files named
DeveloperPortal* - The
DerivedDatafolder - The
Installsfolder (which just had some empty folders in it) - Under
UserData/IB SupportI deleted theSimulator Devicesfolder
Then I did a fresh download and install of Xcode 10.1 from the App Store.
After that, a clean build of the test app worked as expected. I don't know which of the above steps was really needed but I got it working.
answered Nov 14 '18 at 19:01
rmaddyrmaddy
245k27324388
Delete Xcode and install it again + delete DerivedData fixed the problem for me. Somehow the old installation of Xcode 10.1 kept on linking the projects with iOS 12.0 and that was the problem.
– Vladimir Grigorov
Nov 16 '18 at 10:22
As the answer indicated, simply upgrading to Xcode10.1 and removing ** DerivedData** did not work for me. I happened to have access to another laptop with brand new Mojave & Xcode10.1 installed, then it just worked.
– Wei WANG
Dec 10 '18 at 5:13
@WeiWANG I'm not sure I understand the point of your comment here. My answer does not simply say to upgrade to 10.1 and remove DerivedData. No one ever said that would solve the problem. And of course a fresh install of macOS and Xcode 10.1 works. My answers explains how I was able to get it working when starting from an existing installation of macOS and Xcode 10.0. I required several steps of cleanup, then installing Xcode 10.1.
– rmaddy
Dec 10 '18 at 15:08
@rmaddy You did misunderstood... :-) my bad though. I just wanted to back up your answer that simply upgrading will not work.
– Wei WANG
Dec 10 '18 at 21:45
add a comment |
I was seeing the same issue simply by creating a fresh iOS app using the Single View app or the Master-Detail app templates.
I got it working as expected by doing the following:
I deleted all versions of Xcode installed on my computer. I went to my ~/Library/Developer/Xcode folder and I deleted the following:
- All files named
DeveloperPortal* - The
DerivedDatafolder - The
Installsfolder (which just had some empty folders in it) - Under
UserData/IB SupportI deleted theSimulator Devicesfolder
Then I did a fresh download and install of Xcode 10.1 from the App Store.
After that, a clean build of the test app worked as expected. I don't know which of the above steps was really needed but I got it working.
answered Nov 14 '18 at 19:01
rmaddyrmaddy
245k27324388
Delete Xcode and install it again + delete DerivedData fixed the problem for me. Somehow the old installation of Xcode 10.1 kept on linking the projects with iOS 12.0 and that was the problem.
– Vladimir Grigorov
Nov 16 '18 at 10:22
As the answer indicated, simply upgrading to Xcode10.1 and removing ** DerivedData** did not work for me. I happened to have access to another laptop with brand new Mojave & Xcode10.1 installed, then it just worked.
– Wei WANG
Dec 10 '18 at 5:13
@WeiWANG I'm not sure I understand the point of your comment here. My answer does not simply say to upgrade to 10.1 and remove DerivedData. No one ever said that would solve the problem. And of course a fresh install of macOS and Xcode 10.1 works. My answers explains how I was able to get it working when starting from an existing installation of macOS and Xcode 10.0. I required several steps of cleanup, then installing Xcode 10.1.
– rmaddy
Dec 10 '18 at 15:08
@rmaddy You did misunderstood... :-) my bad though. I just wanted to back up your answer that simply upgrading will not work.
– Wei WANG
Dec 10 '18 at 21:45
add a comment |
I was seeing the same issue simply by creating a fresh iOS app using the Single View app or the Master-Detail app templates.
I got it working as expected by doing the following:
I deleted all versions of Xcode installed on my computer. I went to my ~/Library/Developer/Xcode folder and I deleted the following:
- All files named
DeveloperPortal* - The
DerivedDatafolder - The
Installsfolder (which just had some empty folders in it) - Under
UserData/IB SupportI deleted theSimulator Devicesfolder
Then I did a fresh download and install of Xcode 10.1 from the App Store.
After that, a clean build of the test app worked as expected. I don't know which of the above steps was really needed but I got it working.
answered Nov 14 '18 at 19:01
rmaddyrmaddy
245k27324388
I was seeing the same issue simply by creating a fresh iOS app using the Single View app or the Master-Detail app templates.
I got it working as expected by doing the following:
I deleted all versions of Xcode installed on my computer. I went to my ~/Library/Developer/Xcode folder and I deleted the following:
- All files named
DeveloperPortal* - The
DerivedDatafolder - The
Installsfolder (which just had some empty folders in it) - Under
UserData/IB SupportI deleted theSimulator Devicesfolder
Then I did a fresh download and install of Xcode 10.1 from the App Store.
After that, a clean build of the test app worked as expected. I don't know which of the above steps was really needed but I got it working.
answered Nov 14 '18 at 19:01
rmaddyrmaddy
245k27324388
answered Nov 14 '18 at 19:01
rmaddyrmaddy
245k27324388
answered Nov 14 '18 at 19:01
rmaddyrmaddy
245k27324388
answered Nov 14 '18 at 19:01
rmaddyrmaddy
245k27324388
245k27324388
Delete Xcode and install it again + delete DerivedData fixed the problem for me. Somehow the old installation of Xcode 10.1 kept on linking the projects with iOS 12.0 and that was the problem.
– Vladimir Grigorov
Nov 16 '18 at 10:22
As the answer indicated, simply upgrading to Xcode10.1 and removing ** DerivedData** did not work for me. I happened to have access to another laptop with brand new Mojave & Xcode10.1 installed, then it just worked.
– Wei WANG
Dec 10 '18 at 5:13
@WeiWANG I'm not sure I understand the point of your comment here. My answer does not simply say to upgrade to 10.1 and remove DerivedData. No one ever said that would solve the problem. And of course a fresh install of macOS and Xcode 10.1 works. My answers explains how I was able to get it working when starting from an existing installation of macOS and Xcode 10.0. I required several steps of cleanup, then installing Xcode 10.1.
– rmaddy
Dec 10 '18 at 15:08
@rmaddy You did misunderstood... :-) my bad though. I just wanted to back up your answer that simply upgrading will not work.
– Wei WANG
Dec 10 '18 at 21:45
add a comment |
Delete Xcode and install it again + delete DerivedData fixed the problem for me. Somehow the old installation of Xcode 10.1 kept on linking the projects with iOS 12.0 and that was the problem.
– Vladimir Grigorov
Nov 16 '18 at 10:22
As the answer indicated, simply upgrading to Xcode10.1 and removing ** DerivedData** did not work for me. I happened to have access to another laptop with brand new Mojave & Xcode10.1 installed, then it just worked.
– Wei WANG
Dec 10 '18 at 5:13
@WeiWANG I'm not sure I understand the point of your comment here. My answer does not simply say to upgrade to 10.1 and remove DerivedData. No one ever said that would solve the problem. And of course a fresh install of macOS and Xcode 10.1 works. My answers explains how I was able to get it working when starting from an existing installation of macOS and Xcode 10.0. I required several steps of cleanup, then installing Xcode 10.1.
– rmaddy
Dec 10 '18 at 15:08
@rmaddy You did misunderstood... :-) my bad though. I just wanted to back up your answer that simply upgrading will not work.
– Wei WANG
Dec 10 '18 at 21:45
Delete Xcode and install it again + delete DerivedData fixed the problem for me. Somehow the old installation of Xcode 10.1 kept on linking the projects with iOS 12.0 and that was the problem.
– Vladimir Grigorov
Nov 16 '18 at 10:22
Delete Xcode and install it again + delete DerivedData fixed the problem for me. Somehow the old installation of Xcode 10.1 kept on linking the projects with iOS 12.0 and that was the problem.
– Vladimir Grigorov
Nov 16 '18 at 10:22
As the answer indicated, simply upgrading to Xcode10.1 and removing ** DerivedData** did not work for me. I happened to have access to another laptop with brand new Mojave & Xcode10.1 installed, then it just worked.
– Wei WANG
Dec 10 '18 at 5:13
As the answer indicated, simply upgrading to Xcode10.1 and removing ** DerivedData** did not work for me. I happened to have access to another laptop with brand new Mojave & Xcode10.1 installed, then it just worked.
– Wei WANG
Dec 10 '18 at 5:13
@WeiWANG I'm not sure I understand the point of your comment here. My answer does not simply say to upgrade to 10.1 and remove DerivedData. No one ever said that would solve the problem. And of course a fresh install of macOS and Xcode 10.1 works. My answers explains how I was able to get it working when starting from an existing installation of macOS and Xcode 10.0. I required several steps of cleanup, then installing Xcode 10.1.
– rmaddy
Dec 10 '18 at 15:08
@WeiWANG I'm not sure I understand the point of your comment here. My answer does not simply say to upgrade to 10.1 and remove DerivedData. No one ever said that would solve the problem. And of course a fresh install of macOS and Xcode 10.1 works. My answers explains how I was able to get it working when starting from an existing installation of macOS and Xcode 10.0. I required several steps of cleanup, then installing Xcode 10.1.
– rmaddy
Dec 10 '18 at 15:08
@rmaddy You did misunderstood... :-) my bad though. I just wanted to back up your answer that simply upgrading will not work.
– Wei WANG
Dec 10 '18 at 21:45
@rmaddy You did misunderstood... :-) my bad though. I just wanted to back up your answer that simply upgrading will not work.
– Wei WANG
Dec 10 '18 at 21:45
add a comment |
I tried the above answer and it did not fix my problem. I did fix my problem by setting a .storyboard file as my Launch Screen File in Project->Target->General. Previously, I had been using Launch Images for my splash screen.
This is mentioned in the "Optimizing Your UI" section here: https://developer.apple.com/ipad/
answered Nov 26 '18 at 16:41
ryanrrryanrr
265
Based on the screenshots in the question, the OP is already using a Launch screen storyboard so my answer didn't address that. Without that storyboard, the black bars are much bigger.
– rmaddy
Dec 10 '18 at 15:03
add a comment |
I tried the above answer and it did not fix my problem. I did fix my problem by setting a .storyboard file as my Launch Screen File in Project->Target->General. Previously, I had been using Launch Images for my splash screen.
This is mentioned in the "Optimizing Your UI" section here: https://developer.apple.com/ipad/
answered Nov 26 '18 at 16:41
ryanrrryanrr
265
Based on the screenshots in the question, the OP is already using a Launch screen storyboard so my answer didn't address that. Without that storyboard, the black bars are much bigger.
– rmaddy
Dec 10 '18 at 15:03
add a comment |
I tried the above answer and it did not fix my problem. I did fix my problem by setting a .storyboard file as my Launch Screen File in Project->Target->General. Previously, I had been using Launch Images for my splash screen.
This is mentioned in the "Optimizing Your UI" section here: https://developer.apple.com/ipad/
answered Nov 26 '18 at 16:41
ryanrrryanrr
265
I tried the above answer and it did not fix my problem. I did fix my problem by setting a .storyboard file as my Launch Screen File in Project->Target->General. Previously, I had been using Launch Images for my splash screen.
This is mentioned in the "Optimizing Your UI" section here: https://developer.apple.com/ipad/
answered Nov 26 '18 at 16:41
ryanrrryanrr
265
answered Nov 26 '18 at 16:41
ryanrrryanrr
265
answered Nov 26 '18 at 16:41
ryanrrryanrr
265
answered Nov 26 '18 at 16:41
ryanrrryanrr
265
265
Based on the screenshots in the question, the OP is already using a Launch screen storyboard so my answer didn't address that. Without that storyboard, the black bars are much bigger.
– rmaddy
Dec 10 '18 at 15:03
add a comment |
Based on the screenshots in the question, the OP is already using a Launch screen storyboard so my answer didn't address that. Without that storyboard, the black bars are much bigger.
– rmaddy
Dec 10 '18 at 15:03
Based on the screenshots in the question, the OP is already using a Launch screen storyboard so my answer didn't address that. Without that storyboard, the black bars are much bigger.
– rmaddy
Dec 10 '18 at 15:03
Based on the screenshots in the question, the OP is already using a Launch screen storyboard so my answer didn't address that. Without that storyboard, the black bars are much bigger.
– rmaddy
Dec 10 '18 at 15:03
add a comment |
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.
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%2f53208148%2fblack-status-bar-on-the-ipad-pro-with-rounded-corners%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
@matt - you tell me. It's a plain vanilla Single View app with the background color set to green.
– Vladimir Grigorov
Nov 9 '18 at 9:35
Can you post a sample project? I still can't reproduce the issue on the 11-inch or the 12-inch 3rd gen simulator. Have you restarted the computer? Cleaned out derived data? Deleted all simulators and recreated them? Those are all things I always do whenever there's an Xcode upgrade.
– matt
Nov 9 '18 at 21:36