I had also tried quitting the App Store and starting again, but the same kept happening - going to 61%, then spinning away with no progress indication. I tried leaving it overnight, but in the morning it was in the same state: neither appstoreagent nor installd doing anything, but then seeming to wake up and grind away again, but making no progress. This cycle continued, but with no progress.
After waking up again, the appstoreagent would run at 95% CPU (one core) for a while, followed by installd running again, at around 300% CPU. It seemed that the App Store app would stop, and a couple of times I checked Activity Monitor and saw that it was in "App Nap" mode. However, after a while it would stop doing so. The installd process was still using a lot of CPU. Filtering for ASDAppQuery in the Console, as suggested in other answers, showed progress for a while, but then also stopped. This time though, the install would progress to 61% (seen by hovering the mouse over the spinning circle in App Store), then stay there. As with previous versions, I had trouble installing it.
It downloaded (about 7 GB in 20 minutes) and completed the install in less than an hour on my M1 Mac mini.Īfter updating to Ventura, there was an update to Xcode 14.1 in the App Store. (Move to trash)Īfter trying to update to Xcode 14.1 on Ventura for nearly 24 hours, I eventually trashed the Xcode application, rebooted, started only the App Store, and did a new install, leaving the App Store in the foreground. When the command completes the prompt should return and a file would be created.Hit Enter, It will take some time to complete the process (depends on the file size) Now use command mkfile G your-file-name.ext ( example: mkfile 4G mymovie.mov => will create a movie file with name mymovie of size 4GB).Move to the location where you want to create your file using cd.(Has to do with containers, read here for more info: ) This allows you to trick your computer that you actually have enough space. To solve the "space" problem you can create a dummy file and directly remove it. What I found to be the problem is that App Store didn't think I had enough space when in fact I had enough space for Xcode. I had the same problem, and for me, the tips in this thread did not work.
0 kommentar(er)
