Apple Releases Xcode 9.3.1 Update

[MacRumors]

Apple today released an updated version of Xcode, Xcode 9.3.1. The new version of Xcode comes over a month after the release of Xcode 9.3, which was launched alongside iOS 11.3 back in late March.

Xcode 9.3.1 is a minor bug fix update. According to Apple's release notes, it addresses an issue that could cause a user to have to log in with their Apple ID repeatedly and it fixes a bug that could cause Xcode to hang when using Playgrounds.

Xcode 9.3, the previous update, introduced a new Energy organizer designed to help developers detect when an app or app extension is using too much battery life on a user's device.

The software also brought a new 64-bit testing mode for macOS 10.13.4, which is designed to let developers test software for 64-bit compatibility as Apple prepares to start phasing out 32-bit Mac apps. As of Xcode 9.3, Xcode support for macOS 32-bit support has been depreciated.

Xcode 9.3.1 will be followed by Xcode 9.4, which is currently in beta testing. Apple has seeded two betas of Xcode 9.4 to developers thus far.

Article Link: Apple Releases Xcode 9.3.1 Update

 

[hunt2013]

That goodness for the fix to Playgrounds crashing. It is hard to test stuff when it crashed every 5 minutes.

 

[Luigi3]

That goodness for the fix to Playgrounds crashing. It is hard to test stuff when it crashed every 5 minutes.

It's better just to use new, clean project. Error descriptions are better and buildtime diff is little to none.

 

[Markoth]

That goodness for the fix to Playgrounds crashing. It is hard to test stuff when it crashed every 5 minutes.

How can I crash thee, let me count the ways... Xcode crashing is basically expected for me at this point, you just never know what's going to make it crash the next time.

 

[CJM]

Xcode really does crash a fair bit, doesn’t it.

 

[Reason077]

Xcode really does crash a fair bit, doesn’t it.

Mines pretty stable so long as you stick to the code editors. But once you start messing around in Interface Builder, it can be a nightmare.

 

[chrono1081]

Finally fixed playgrounds! They're so useful and it sucks not having them.
[doublepost=1526048728][/doublepost]

How can I crash thee, let me count the ways... Xcode crashing is basically expected for me at this point, you just never know what's going to make it crash the next time.

I go months between crashes and I use it for at least 8 hours a day. I'm not sure how so many people are getting so many crashes. The only crashes I experienced frequently were not even crashes, but rather slowdowns and unresponsiveness in the playgrounds.

I'm not saying you're lying about the crashes, I'm rather just curious on why some people experience so many of them and what the common denominator among those experiencing crashes is.

 

[tayalva]

Finally fixed playgrounds! They're so useful and it sucks not having them.
[doublepost=1526048728][/doublepost]

I go months between crashes and I use it for at least 8 hours a day. I'm not sure how so many people are getting so many crashes. The only crashes I experienced frequently were not even crashes, but rather slowdowns and unresponsiveness in the playgrounds.

I'm not saying you're lying about the crashes, I'm rather just curious on why some people experience so many of them and what the common denominator among those experiencing crashes is.

Xcode rarely crashes for me as well... playground... another story. I’m curious as well why it crashes so often for others

 

[SeminalSage]

It's better just to use new, clean project. Error descriptions are better and buildtime diff is little to none.

Except, when someone is using the Apple provided lessons in App Development with Swift (which Apple is promoting as the definitive teaching solution), the student has to use playgrounds for a majority of chapters.

I'm glad Apple fixed it.
[doublepost=1526053450][/doublepost]

Finally fixed playgrounds! They're so useful and it sucks not having them.
[doublepost=1526048728][/doublepost]

I go months between crashes and I use it for at least 8 hours a day. I'm not sure how so many people are getting so many crashes. The only crashes I experienced frequently were not even crashes, but rather slowdowns and unresponsiveness in the playgrounds.

I'm not saying you're lying about the crashes, I'm rather just curious on why some people experience so many of them and what the common denominator among those experiencing crashes is.

I'm guessing here, but I'm betting this line from your signature has something to do with it: "Mac Pro (2010): 3.33Ghz Intel Xeon (6 core) - 24 GB RAM - NVidia Quadro k5000".

Before this latest bug, my 15" MacBook Pro had no issues, but my 13" MacBook Pro would hang from time to time.

 

[tzm41]

Finally fixed playgrounds! They're so useful and it sucks not having them.
[doublepost=1526048728][/doublepost]

I go months between crashes and I use it for at least 8 hours a day. I'm not sure how so many people are getting so many crashes. The only crashes I experienced frequently were not even crashes, but rather slowdowns and unresponsiveness in the playgrounds.

I'm not saying you're lying about the crashes, I'm rather just curious on why some people experience so many of them and what the common denominator among those experiencing crashes is.

It definitely depends on the complexity of your project. It doesn't handle very large projects, or projects with a lot of RxSwift, or code that puts compiler's typer inference ability to test, very well. Also if there are some IBDesignables, IB crashes very often.
[doublepost=1526055140][/doublepost]

Except, when someone is using the Apple provided lessons in App Development with Swift (which Apple is promoting as the definitive teaching solution), the student has to use playgrounds for a majority of chapters.

I'm glad Apple fixed it.
[doublepost=1526053450][/doublepost]

I'm guessing here, but I'm betting this line from your signature has something to do with it: "Mac Pro (2010): 3.33Ghz Intel Xeon (6 core) - 24 GB RAM - NVidia Quadro k5000".

Before this latest bug, my 15" MacBook Pro had no issues, but my 13" MacBook Pro would hang from time to time.

For me, Xcode 9 itself probably only crashes once per week. I consider that huge improvement from 7 and 8. The crashes are mostly not due to the power of the machine though. Often times it's code editor trying to access an non existent line and causes index out of bounds, or some other cryptic crash on NSView loading frames.

IB engine crashes quite often, as well as compiler when I switch branches.

 

[MauiPa]

Xcode really does crash a fair bit, doesn’t it.

Nope, Mine never crashes. I'm always on the Beta too.

 

[Markoth]

Finally fixed playgrounds! They're so useful and it sucks not having them.
[doublepost=1526048728][/doublepost]

I go months between crashes and I use it for at least 8 hours a day. I'm not sure how so many people are getting so many crashes. The only crashes I experienced frequently were not even crashes, but rather slowdowns and unresponsiveness in the playgrounds.

I'm not saying you're lying about the crashes, I'm rather just curious on why some people experience so many of them and what the common denominator among those experiencing crashes is.

Wish I knew. Most of the crashes happen in Interface Builder, which can make it quite challenging at times. There's a swift-related subprocess which crashes a lot too, but it doesn't crash Xcode, just makes code completion among other things not work temporarily, until Xcode restarts the process. All in all, Xcode for me has been quite unstable. When its stability, performance and feature set are compared to IDEs such as PHPStorm and PyCharm, it is actually quite embarrassing for Apple. Sometimes I wonder if they're aware.

 

[Vjosullivan]

It's better just to use new, clean project. Error descriptions are better and buildtime diff is little to none.

Having to create a new project every time the playground crashes isn’t really a solution to anything.
[doublepost=1526193181][/doublepost]

Finally fixed playgrounds! They're so useful and it sucks not having them.
[doublepost=1526048728][/doublepost]

I go months between crashes and I use it for at least 8 hours a day....

I'm not saying you're lying about the crashes....

There can be very many reasons some people get regular crashes and others don’t. Hardware set ups, OS versions, clashes with other software, fragile software design, etc. Fortunately, Apple’s response has not been along the lines of “It works on my machine.”. They appear to have found some bugs of sufficient importance to warrant a bug fix release. Time will tell if they solve the widespread problems people are having with playgrounds.

 

[fairuz]

The Playgrounds are almost useless. Due to bugs and limitations, and I don't just mean the one they fixed, it's honestly faster in almost every case to use a fresh project.

Better yet, use React Native if you wanna quickly iterate with GUI. It's so much easier because you just write to the file, and it insta-updates so you can tweak things quickly instead of having to take forever rebuilding (Swift takes sooooo freaking long to build vs ObjC). That and the language and libraries are way easier to deal with for GUI. And I get to use Vim. Only thing is I feel dirty using Javascript.
[doublepost=1526196452][/doublepost]

Xcode really does crash a fair bit, doesn’t it.

No, mine crashes pretty rarely now. But... rant incoming... ever since the Swift update, it's been crappy in many other ways. Builds take forever. There are not-super-rare memory leaks. I used to get tons of segfaults IN THE COMPILER while compiling, and it still happens on rare occasions if I have a syntax error in some crazy thing involving generics. The debugger's variable inspection is broken af, like to the point where I can't expect anything to work, so I use print statements instead. The code completion used to also be broken, but now it works pretty reliably but often slowly.

Btw, Swift is a decent language and quite the engineering marvel, but there are some decisions they made that I can't fathom. String manipulation is unbelievably difficult, to the point where I've relied on custom solutions. Structs are very weird to work with, and pass-by-value arrays are a "wtf" kind of surprise to newbies. Syntax is weird and unintuitive in many places, especially code blocks.

 

[briloronmacrumo]

As of Xcode 9.3, Xcode support for macOS 32-bit support has been depreciated.

Spell check catches the writers once again. Apple "deprecates" not depreciates.

 

[tzm41]

The Playgrounds are almost useless. Due to bugs and limitations, and I don't just mean the one they fixed, it's honestly faster in almost every case to use a fresh project.

Better yet, use React Native if you wanna quickly iterate with GUI. It's so much easier because you just write to the file, and it insta-updates so you can tweak things quickly instead of having to take forever rebuilding (Swift takes sooooo freaking long to build vs ObjC). That and the language and libraries are way easier to deal with for GUI. And I get to use Vim. Only thing is I feel dirty using Javascript.
[doublepost=1526196452][/doublepost]
No, mine crashes pretty rarely now. But... rant incoming... ever since the Swift update, it's been crappy in many other ways. Builds take forever. There are not-super-rare memory leaks. I used to get tons of segfaults IN THE COMPILER while compiling, and it still happens on rare occasions if I have a syntax error in some crazy thing involving generics. The debugger's variable inspection is broken af, like to the point where I can't expect anything to work, so I use print statements instead. The code completion used to also be broken, but now it works pretty reliably but often slowly.

Btw, Swift is a decent language and quite the engineering marvel, but there are some decisions they made that I can't fathom. String manipulation is unbelievably difficult, to the point where I've relied on custom solutions. Structs are very weird to work with, and pass-by-value arrays are a "wtf" kind of surprise to newbies. Syntax is weird and unintuitive in many places, especially code blocks.

Second the part with debugger variable inspection. I never use that crap anymore.