Xcode 11.3.1 Released Nearly One Month After Apple Last Seeded Betas of iOS, macOS, watchOS, and tvOS

MacRumors

macrumors bot
Original poster
Apr 12, 2001
46,796
8,962



Apple on Monday released Xcode 11.3.1 with bug fixes and improvements, including reducing the size of dependency files produced by the Swift compiler, which can improve incremental build times and disk usage for targets with many source files. Full release notes are posted on Apple's developer website.

As with Xcode 11.3, version 11.3.1 supports developing apps for iOS 13.3, iPadOS 13.3, macOS 10.15.2, watchOS 6.1, and tvOS 13.3.


It has been nearly one month since Apple seeded new betas for its software platforms, which is an unusually long time. The first betas of iOS 13.3.1, iPadOS 13.3.1, macOS 10.15.3, watchOS 6.1.2, and tvOS 13.3.1 were seeded on December 17, but no further builds have been made available since then.

Apple always stops seeding betas over the holidays, but the cycle usually resumes in early January, including January 7 in 2019, January 3 in 2018, and January 9 in 2017, so there is a bit of a delay this year.

On an Xcode-related note, Apple has reminded developers that, starting April 2020, apps submitted to the App Store must use an Xcode storyboard to provide the app's launch screen and must have an interface that supports any display size. Apple also strongly encourages supporting multitasking on iPad.

Apple:
Apps should look great on all models of iPhone and iPad, regardless of display size or aspect ratio. With features like Xcode storyboards and Auto Layout, your app's interface elements and layouts automatically fit the display. As announced at WWDC19, starting April 2020, apps submitted to the App Store must use an Xcode storyboard to provide the app's launch screen and must have an interface that supports any display size.

Support for Multitasking on iPad is strongly encouraged. Adding support for multiple windows, and adopting Multitasking capabilities, including Slide Over, Split View, and Picture in Picture, will ensure your app delivers a modern and complete experience on iPadOS.
Apple says it has addressed an Xcode bug in the storyboard canvas that could cause the development tool to crash.

Article Link: Xcode 11.3.1 Released Nearly One Month After Apple Last Seeded Betas of iOS, macOS, watchOS, and tvOS
 

Vjosullivan

macrumors 6502a
Oct 21, 2013
831
949
struct ContentView: View {
var body: some View {
List {
HStack {
Button("OK") {
print("OK")
}
Button("Cancel") {
print("Cancel")
}
}
}
}
}

SwiftUI is still not quite there. :confused:
(Tapping either button prints both "OK" and "Cancel")
 
Last edited:

zorinlynx

macrumors 603
May 31, 2007
5,722
7,075
Florida, USA
Apple really is ridiculous with these arbitrary requirements. I can’t wait for the day when they are forced to allow side loading of apps.
I don't mind requirements that say your app has to look good on all devices. TO THIS DAY I sometimes download an app on my iPad and it turns out to be an iPhone-only app that's scaled up. This is something we shouldn't have to deal with.

What I do have issue with are the other app store rules regarding content. Stuff like banning vaping apps, porn apps, emulators, etc... This is Apple taking a moral stance when morals differ between individuals.
 

jonblatho

macrumors 65816
Jan 20, 2014
1,444
3,601
Missouri
Apple really is ridiculous with these arbitrary requirements. I can’t wait for the day when they are forced to allow side loading of apps.
Yeah, I’ll gladly take the end of letterboxed and/or scaled apps over some crusade against “arbitrary requirements.”

A launch screen as a storyboard is preferable for the developer given the litany of window sizes an app must support between iPhones, iPod touches, and iPads (while I don’t know the exact number, it’s well into the dozens at this point for an app supporting all devices and Slide Over and Split View on the iPad). It also implicitly discourages the use of the launch screen as a splash screen, is far better futureproofed for new devices, and more.

As for supporting Auto Layout, Apple’s been increasingly strongly recommending, and now requiring, developers update their iOS apps to use Auto Layout since WWDC 2012. If done correctly (which for most apps isn’t that hard), this means that as iOS devices’ screen sizes and multitasking features evolve, all the work that is required of a developer is to recompile their app. Even before this requirement was announced it was blatantly obvious that it would one day be a requirement to anyone with a functioning brain. Not if, when. They will have had almost 8 years to get with the program, and at this point the work they’ve had to put in to not use Auto Layout almost certainly far exceeds that required to have just switched over, which is why the overwhelming majority of apps already support Auto Layout.

But no, it’s just an arbitrary requirement.
 

Kevin Palser

macrumors newbie
Jan 14, 2020
1
1
Dundee, Scotland
What I do have issue with are the other app store rules regarding content. Stuff like banning vaping apps, porn apps, emulators, etc...
Emulators are not entirely banned from the iOS/iPadOs App Store. They are just neutered because Apple does not allow functionality to allow programs to be loaded unless they are included within the emulator app. For example:

Jupiter ACE (iPad only)
ZX81 (an app that I wrote)
Spectaculator
iAltair

to list a few... Unfortunately, given the Apple Developer Guidelines I think emulator apps will always be unpopular on this platform and we're unlikely to ever see an "Emulators" store category.
 
Last edited:
  • Haha
Reactions: Babygotfont

jacjustjac

macrumors regular
Feb 12, 2008
195
307
New York, NY
Does this mean we’ll finally get a native Instagram app for iPad? Make fun of me all you want, but I use IG to successfully market my business and more people using it on tablets could mean a change in how I produce content for it. Like the way Dark Mode has affected the aesthetics for some accounts.
 

Ludatyk

macrumors 68000
May 27, 2012
1,771
766
Texas
Does this mean we’ll finally get a native Instagram app for iPad?
Perhaps, but I’m alright with using Safari on the iPad to browse. I’m anxious for developers to put an effort to implement Multi-Window support

And, Google is dragging their feet with YT Music Split-View support.
 
  • Angry
Reactions: Babygotfont

uneeko1ne

macrumors regular
Dec 16, 2017
109
55
Reno,Nv
Does this mean we’ll finally get a native Instagram app for iPad? Make fun of me all you want, but I use IG to successfully market my business and more people using it on tablets could mean a change in how I produce content for it. Like the way Dark Mode has affected the aesthetics for some accounts.
I hope so
 
  • Angry
Reactions: Babygotfont

jonblatho

macrumors 65816
Jan 20, 2014
1,444
3,601
Missouri
Does this mean we’ll finally get a native Instagram app for iPad? Make fun of me all you want, but I use IG to successfully market my business and more people using it on tablets could mean a change in how I produce content for it. Like the way Dark Mode has affected the aesthetics for some accounts.
No. Apps will still be able to support only iPhone/iPod touch or iPad, or both. For the device families they choose, they must now support all available display sizes, but it’s still up to the developer.
 
  • Like
Reactions: MarchyStar

MarchyStar

macrumors newbie
Mar 27, 2017
4
3
Toronto
I don't mind requirements that say your app has to look good on all devices. TO THIS DAY I sometimes download an app on my iPad and it turns out to be an iPhone-only app that's scaled up. This is something we shouldn't have to deal with.

What I do have issue with are the other app store rules regarding content. Stuff like banning vaping apps, porn apps, emulators, etc... This is Apple taking a moral stance when morals differ between individuals.
This requirement won't solve that. The App Store will still show apps that are design just for phone (iPhone) VS tablet (iPad), and by default the store DOESN'T show you phone apps. If you choose to install a phone-designed phone on an iPad, you will still get the scaled app since the developer never designed for that FORM FACTOR.

This requirement simply eliminates the letter-boxed phone apps which were designed for the iPhone 6 era, yet show up letterboxed on the taller fullscreen-era ones (ie: iPhone X/11). Same thing goes for those that were designed for JUST regular-size phones (ie: iPhone 6/X) but show up scaled on plus-sized ones (ie: iPhone 6 Plus, XR/11, X/11 Max)


Tablets and phones are different form factors, just like desktop, TV, in-car dash or a watch are different form factors. This requirement does not force apps to run on new form factors – since a lot of apps' use cases make sense only on one form factor or another. This definitely includes tablets which are not pocket-portable and thus have very different use cases in people's lives.
 

fairuz

macrumors 68020
Aug 27, 2017
2,245
2,334
Silicon Valley
Apple really is ridiculous with these arbitrary requirements. I can’t wait for the day when they are forced to allow side loading of apps.
They already allow it via Xcode and maybe other ways. But I'm not sure if you can just send people IPAs and let them load them that way.
- - Post merged: - -

As for supporting Auto Layout, Apple’s been increasingly strongly recommending, and now requiring, developers update their iOS apps to use Auto Layout since WWDC 2012. If done correctly (which for most apps isn’t that hard), this means that as iOS devices’ screen sizes and multitasking features evolve, all the work that is required of a developer is to recompile their app. Even before this requirement was announced it was blatantly obvious that it would one day be a requirement to anyone with a functioning brain. Not if, when. They will have had almost 8 years to get with the program, and at this point the work they’ve had to put in to not use Auto Layout almost certainly far exceeds that required to have just switched over, which is why the overwhelming majority of apps already support Auto Layout.

But no, it’s just an arbitrary requirement.
You shouldn't have to be forcing people to use something that's meant to be helpful. Auto Layout is confusing and overall bad compared to similar features in every other UI framework. Part of why people are jumping to React Native. Back when I wrote an app in 2014, I calculated all the layout in macros, no regrets (it even worked with newer screens). Now I use RN for side projects, and Xcode is just a dependency to me.
 
Last edited: