Hi, are those issues fixed in 11.4.1?
Post
Replies
Boosts
Views
Activity
I get why it tries to build for arm64 simulator. Because we will have soon Arm64 mac, that is good. But I don't have such mac yet. I do have intel based mac. so this I think is an error that guys on xcode team need to fix. -> clang++ -target arm64-apple-ios14.0-simulator. On intel based mac this can not be correct target.
This works:
Check if in your project for compiled target ->build settings -> user defined section (at the very bottom) you have defined VALID_ARCHS=arm64, if yes, delete it.
try this:
Check if in your project for compiled target ->build settings -> user defined section (at the very bottom) you have defined VALID_ARCHS=arm64, if yes, delete it.
I have same issue. Xcode Version 12.4 (12D4e), no devices connected, just closing an open file from IDE takes few seconds, and beachball is shown. Xcode 11.7 had no such issue, nor Xcode 12.3. I have 32GB ram so it is not caused with swap or anything like that. Running on Bir Sur 11.1.
That port number might be a problem.
http://localhost:5000/ios/hola?hola=hola -> http://localhost/ios/hola?hola=hola
it is still happening in 14.3.1 and also 15 beta 2.
Resolving package graph on slower internet is full of errors about unresolved dependencies.
But yes, it works on 1GB fiber optic connection.. :(
This part of package resolving process is clearly not ideal/finished.
Well, checking on Xcode Version 15.0 (15A240d), and behavior is like this:
I see this in the log:
#FactoryInstall Unable to query results, error: 5
Unable to list voice folder
Unable to list voice folder
Unable to list voice folder
Unable to list voice folder
Unable to list voice folder
Unable to list voice folder
Unable to list voice folder
Unable to list voice folder
Unable to list voice folder
Unable to list voice folder
-you have to have patience if you have enabled breakpoints and active debug session, because you need to pass 12 exceptions
-if you are lucky and xcode does not freeze, you will eventually hear the sound.
So the best at the moment is to switch off breakpoints for "Swift Error" (delete it from list of breakpoints)
Not ideal, but it works for now. I filled the bug report.
The hack with .plist file I saw in one of the apple's examples. I was wondering how they did it.
Unfortunately it is not usable for any other md files. It is good for readme.md only.
After last fiasco in Windows world (CrowdStrike) I would say that adding anything "Anti virus" is just adding another vector of attack to your system.
Install apps from trusted sources only and you should be fine.
Only properties that are referenced in view and "registered" are accessed. From my experience it makes sense to add ObservationIgnored when you as a programmer really don't want that property to be tracked by view by error.
for iOS..use it..it is mostly fine, but for macOS...not so much. constant performance problems. New OS release == new problems.
from macOS Sequoia 15.1 RC Release Notes
Resolved Issues
Fixed: Back-deploying apps that link QuickLookUI to macOS 11 or earlier might crash. (133213738) (FB14667312)
So re-compile with Xcode 16 + macOS 15.1..and it should work