Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Xcode 13.2 Update Downloaded From Mac App Store Causing Errors for Developers

MacRumors

MacRumors

macrumors bot
Original poster
Apr 12, 2001
67,701
38,169


Alongside iOS 15.2, iPadOS 15.2, macOS Monterey 12.1, and watchOS 8.3, Apple yesterday introduced an updated version of Xcode, Xcode 13.2. Developers who are updating should be aware that there's a bug with the Mac App Store version of the software at this time, and it should be avoided.

iu-2-1.jpeg

According to a thread on the Developer forums, updating to Xcode 13.2 from the Mac App Store results in projects that will no longer compile and package errors. Many developers are seeing the following message: "Internal error: missingPackageDescriptionModule," and there appears to be no fix at this time.

Other developers have received errors related to Github certificate validation and when attempting to add packages from Github.

Apple says that it is investigating the issue, and that in the meantime, Xcode 13.2 should be downloaded directly from the Releases section of the Apple Developer website.

Article Link: Xcode 13.2 Update Downloaded From Mac App Store Causing Errors for Developers
 
Article Link
https://www.macrumors.com/2021/12/14/xcode-13-2-bug/
  • Like
Reactions: sydneysider88 and kalsta
I am surprised that devs are installing updates on day one. they should know better given apple's recent history..
 
New M1 Max MacBook Pro and I guess I forgot to turn off automatic updates... lost about an hour downloading from the developer site, but I'm back up and running now. A friend summed it up pretty nicely: "I don't f wit automatic updates."
 
  • Like
Reactions: amartinez1660
briloronmacrumo said:
Xcode 13.x launch times are much slower than Xcode 12 on my Intel iMac. I'm hoping an Apple Silicon iMac will be faster.
Click to expand...
Xcode and the Simulator run amazingly fast on Apple Silicon. Build times are so quick. You can run the Simulator + debugger, with all your other apps running, yet not stress the system and have plenty of resources left over. Big upgrade. I got the M1 Max w/ 64 GB RAM, but you might be able to get away with M1 Pro or 32 GB RAM. I routinely exceed 32 GB, but rarely break 40 with my workload. Still it's a nice feeling to have the headroom.
 
  • Like
Reactions: amartinez1660, Argoduck and AxiomaticRubric
I don’t know why Apple have Xcode on the App Store, considering how new versions can sometimes require quite a lot of work to get a project building again it seems a bit crazy for that to be an app that can update automatically overnight.
 
  • Like
Reactions: amartinez1660
I have always avoided the Mac App Store versions. Instead, downloading them from the "More" downloads section on one's developer account.

When 13.0 first came out, I kept my 12.x downloads in case I needed to re-install those versions. Once 13 proved itself (and all projects updated), I then deleted the 12.x downloads.
 
  • Like
Reactions: BulkSlash and AxiomaticRubric
ghostface147 said:
Interesting. It was downloading and installing, then just went to a spinning icon.
Click to expand...
Same for me on the new MBP. Appeared to have downloaded and then just sat there spinning, rather than installing. Quit the App Store and relaunched and it instantly went back to the same. Checked Activity Monitor and no process using more than about 2%, so it's clearly not working to install Xcode.

Edit: Appears it did eventually install.
 
4743913 said:
I am surprised that devs are installing updates on day one. they should know better given apple's recent history..
Click to expand...
This is not a new problem. It's been present in the betas. Seems pulling Xcode for a fresh install and having it re-download components will fix it for *some* users. Some are not encountering the problem to begin with. I'm not having issues on my M1 Max, but had them on my iMac Pro...

Most devs are installing and working with betas where they can do that, but a lot depends on what each has at their disposal for dev/testing use. So it's not a complete surprise when an official release still has the problem. But some just stick with official release builds and don't follow the beta releases. IMO that's a big mistake... If that's the game plan, they should wait a week or two after a release to see what people say then install it. With Mac OS / iOS it makes a lot more sense to stay on top of the latest updates and pay attention to the betas, even if just to see what the discussion is within developer forums. It's not like Windows where I still have clients wanting things built for 32bit Win 7 or earlier because that's good enough and what they're still running.

Unless you're just a casual tinkerer, best to download/install Xcode via the developer portal. And it's usually possible to keep release and beta builds on the same system.
 
masterleep said:
The amazing thing is how long it takes to install Xcode upgrades even on an M1 Max. What on Earth is it doing??
Click to expand...
Well it is 34GB in size, 100,000+ files.
And one suspects (though who knows?) that Apple applies some of the OS sealing and crypto technology to many of the installed files, because an outsider taking control of XCode is as bad as an exploit against MacOS/iOS...

So in a way it's like an OS install (we all know how slow those are!) only with an even larger volume of data and number of files.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back