Apple is asleep at the wheel when it comes to dev concerns. They aren't able to conjure that saving devs time and complexity is good for their business. People will JUMP at the chance to get rid of them as a monopoly, and Tim C00k oughtta figure this out bc it's not 4D chess to learn how to cater to devs complaints. This complaint is all over the place, and no solutions yet.

It's embarrassing for Apple who shows by their complexity to devs (like authorizing developer mode on an iPhone, or finding the UDID-- these simple actions take acts of God) that they really don't pay any attention to devs. It's PREPOSTEROUS how bad Apple is at this, and meanwhile they love incorporating changes and more complexity into Swift such that projects ALL. THE. TIME. and require massive amounts of maintenance. Apple will suffer eventually, book it.

It absolutely is NOT fixed @sdykae . Using 14.3.1 it's still RAMPANT, and it's not just one instance but many. Worse, MacOS won't even let you look up the files on Spotlight or Finder search without some sort of permission from the grave of Steve Jobs.

Yeah, no one at Apple cares about this. Everyone is complaining for years now, and they do nothing, and never respond on these forums (so why have them???).

Obviously no one at Apple cares. This is so annoying to every developer, yet Apple does nothing, not even responding to this other than to say "ignore it". How do you ignore the entire console being bogarted by this nonsense??? Really starting to despise Apple.

Enter your normal password you use to login to your device (like when you open the clamshell after a full shutdown), but this time press ALWAYS ALLOW instead of ALLOW so it can repeat itself a zillion times. Apple is so dang dumb, they should fix this or at least put more explanation down, so people don't have to look this up here, but they really ARE a bunch of dunderheaded engineers.

Apple Swift framework developers should be utterly embarrased that this is still happening in 2023. They have obviously been asleep at the wheel for ages now. None of the answers here works. URL(string: ) should contain allowance to correct for spaces; the fact that it doesn't is truly and utterly embarrassing and costs devs a LOT of f'g wasted time.

You shouldn't have to switch Rosetta on and off just to run a Playground to teach a kid how to code in Swift/XCode/Apple-environment! Most devs don't even understand what Rosetta is, but are forced to figure it out just to continue developing on M1/M2 machines. This is the type of stuff which will lead to Apple's demise.

It's incredibly disappointing Apple allows this type of error to persist almost 2 years after the launch of the M1 chip. It's a total disgrace for the company, as they obviously no longer care about bringing on new developers. Apple continues to persist problems with all XCode when it comes to running on M1/M2 machines. And they are totally asleep at the wheel when it comes to these forums. EXTREMELY disappointed in Apple.

Nice of Apple to respond to this one. These forums are truly as awful as Apple's Swift documentation.

I get this problem as soon as my app starts, no API call is even made. Depressing, as nothing is worse than consoleLog filling up with stuff and developer having zero clue if its leading to OTHER problems in the app.

It's been a year now, and Apple needs to address these M1 related errors. It's messy coding, and we also shouldn't have to do an extra enabling of Rosetta to get things to work in the first place.

Select the UICollectionView in the View Controller Scene menu (middle of Xcode, but left of Main Storyboard visual), and then in Size Inspector change the "Estimated Size" from AUTOMATIC to "NONE". If you have all your hookups done correctly, and constraints are correct in your main Storyboard scene, you should see approximately what you designed instead of small cells.

In 2020 this problem probably has to do with all the jiggering of Provisioning Profiles (whatever they are) Apple has recently done but didn't inform anyone.1) Go to developer account, sign in, and sign the new thing they want signed2). then follow this....To fix this, you need to transfer the Provisioning Profile's Certificate to YOUR own certificate. In developer.apple.com, login to your developer account. Then, in the Edit iOS Provisioning Profiles page in Certificates section, select the certificate you are using for your XCode. Then click Generate button.then you'll still have problems, but will be farther along.

Does anyone at Apple actually read these forums and help anyone?NEVER do I find a helpful answer on forums.dev so always have to either go to Stack Overflow or wait on a long phone call for help directdly from apple, probably wasting everyone's time.Can't login to simulator even using the exact same login as used to login here to forums. REALLY annoying. Even built a whole new AppleID and that didn't work either.So can't use simulator to develop anymore. ABSURD problem.