I’m doing some testing with iOS and found out that, at least on my machine (MacBook Air with Monterey), Fire is running at a quite high CPU load (200%) when debugging. Is this normal?
Also, using the iOS Simple template, trying to edit the Main.Storyboard results in an unresponsive Xcode running at 100%+ without loading it. Opening the LaunchScreen.xib file works ok. Opening a Main.storyboard, in Xcode, from a project created in Xcode loads almost immediately.
This I cant reproduce here. Can I see the exact project, including the /obj folder with the generated .xcproj that shows this for you?
This I haven’t been able to test yet, because Simulator debugging is broken for me for unrelated reasons right now; I’m investigating.
The Simulator is a fickle beast.
I just gte
simctl launch: 2021-10-04 09:09:44.105634-0400 simctl[33988:6280860] +[MTLIOAccelDevice registerDevices]: Zero Metal services found
simctl launch: An error was encountered processing the command (domain=FBSOpenApplicationServiceErrorDomain, code=4):
simctl launch: The request to open "org.me.Multiple Views" failed.
simctl launch: Underlying error (domain=FBSOpenApplicationErrorDomain, code=4):
simctl launch: The operation couldn’t be completed. Application info provider (FBSApplicationLibrary) returned nil for "org.me.Multiple Views"
simctl launch: Application info provider (FBSApplicationLibrary) returned nil for "org.me.Multiple Views"
simctl launch: org.me.Multiple Views: -1
simctl launch: exit code 4
no clue why (the apples installed and can be launched manually, fine)
the .xcodeproj opens fine for me, but it seems it cant find the actual files (which is expected, as the Xcode projnhas hardcoded full names, eg /Users/marcvanbreemen/Lokaal/App11/Resources/Main.storyboard):
BTW: In the screenshot I see that you’ve opened the LaunchScreen. I don’t have a problem with that one. Did you also tested the Main.storyboard? That’s the one I’m having problems with.
Hmm. that one indeed hangs, shows a spinner that just keeps going. Since this reproduces by opening Xcode standalone, not from Fire, this has to be an Apple bug — I suggest filling a radar, and I will too.