-
Re: Xcode 11 unresponsive when trying to create any new project, Catalina
klwn Jun 16, 2019 1:10 PM (in response to jendakub)same here, except I can't even open existing projects XCode crashes immediatly after creating / opening a new/existing project.
-
Re: Xcode 11 unresponsive when trying to create any new project, Catalina
jlagrone Jun 18, 2019 11:51 AM (in response to jendakub)Similar. Can't create anything new with Xcode 11 beta 2 using Catalina beta 2.
-
Re: Xcode 11 unresponsive when trying to create any new project, Catalina
rozzerh94 Jun 24, 2019 11:37 PM (in response to jlagrone)Yep, it wont even load any of my old projects, just get a "busy" icon as soon as it boots. i have no idea how everyone else is using it haha
-
-
Re: Xcode 11 unresponsive when trying to create any new project, Catalina
digit48 Jun 26, 2019 8:44 AM (in response to jendakub)I can open a new project using SwiftUI but the application hangs when trying to create a new project.
-
Re: Xcode 11 unresponsive when trying to create any new project, Catalina
dlbatescom Jun 30, 2019 12:11 PM (in response to jendakub)Same here I can open any previous project that was opened in 10 or beta 1 that is listed in the welcome screen. I cannot open a project from navigation (Open another project) or create a new project. It seems like any call out to the finder crashes the app.
-
Re: Xcode 11 unresponsive when trying to create any new project, Catalina
chrisco Jul 1, 2019 6:43 PM (in response to jendakub)Hah - first thing, trying to reply to this thread from Firefox, is unresponsive "retreiving data...".
I had this problem, I think it might be a (new) Catalina file system access permission issue.
Here is what I suggest:
0. note the default folder that where it is trying to create your project (In my case "development")
1. rename said default folder to a different name
2. restart Xcode, try to create new folder, if you see it default to "Documents" directory and prompt for permission, you are done
3. otherwise, delete the derived data folder, restart and re-attempt
I did both these steps at once, got the prompt and it worked, but I am not sure which one was the cause, but I am suspecting a bug in not prompting for file access permisssion. (It could further help it someone identified which of these factors fixed the problem)