I just came across this problem: Mac Mini 2020 (M1, macOS 12.6 for now), Xcode 14.2, iOS 13.5 simulator (iPhone SE 1G) I copy text (from a TextEdit text file) either with cmd+c or right-click "copy" but it won't paste into a text field in my app in the simulator: Cmd+v doesn't do anything, the right-click menu doesn't even open and Edit - Paste (menu) is greyed out. Copy and pasting from the simulator to the simulator works and if I copy something from the simulator, then copy something else from the text file and paste in the simulator, it only pastes the simulator text.

I didn't set the ratio myself but just dragged one element to the other (tried both ways), while holding down ctrl, then picked "Aspect Ratio" in the dropdown list - no idea how to do it any other way. The UIImageView is a child of the UIView and they both have their "spaces" set to their own superview in the size inspector. The most outer element is a UITableViewCell and I wanted to make IB (it was complaining about a missing constraint) happy by setting the full size like that. Even if there was a zero division, it shouldn't crash but give some type of error message. After the new OS version was done installing I ended up with around 35gb but it was still complaining about not enough free space. I deleted two old SDKs for versions I'd never been using (why is it even keeping/installing that stuff in the first place), which got me to around 43gb and it finally worked. If I'd stopped the download (took the whole day, downloads from Apple's servers are always so slow!), I probably wouldn't have been able to start it again because of the space problem, which happened to me before. I had to call Apple and they helped me clear some cached data. They really have to find a better way to do this, it's a problem every single time and this machine isn't even used for anything else apart from Xcode! When I started it up just now (oh yay, they changed a couple of icons, so worth it!) a new error showed up for 3 of my UIViewControllers: Failed to render and update auto layout status for ViewController.... (ID): Agent crashed Great, I got the same error before the storyboard broke but atm I'm using the old backup one.

Another question just came up: This link - https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/BPInternational/TestingYourInternationalApp/TestingYourInternationalApp.html#//apple_ref/doc/uid/10000171i-CH7-SW1 says that you can change the language that's displayed in the Interface Builder by choosing the language in the lower right of the Assistant Editor (infos written in 2015). This button doesn't exist in Xcode 12.5, no matter if the Assistant Editor is active or not. How do I change the language for it with the latest Xcode version?

@eskimo Sorry for the delayed reply. What I've done so far: I added the second language (French), which added a "strings" file for French for all storyboards. In the File Inspector of the storyboard I ticked "English", which added a "strings" file for English for that specific storyboard. Afterwards I set "developmentRegion = fr;" in the "project.pbxproj" file (set French as development language). This works: If the simulator in Xcode is set to French, the app is French. If the simulator is set to English, the app uses the English translation. If the simulator is set to a different language, e.g. Italian, the app uses French. The rest of the simulated iPhone SE2 was still set to English but that's probably because I only edited the "App Language" in the scheme and didn't set the actual language in the settings. I'm not sure what to do with the "Base" language now. If I change an e.g. button text directly in storyboard, the "strings" files aren't affected, so the changes aren't shown in a simulator of course. If I untick "French", it'll probably be the same as with English before again: I'll only be able to edit the French text directly in storyboard. Unticking "Base" (and moving its contents to "French") didn't work last time around, so not sure what that does. Is there a way to keep the French "strings" files and make it edit them automatically, whenever I edit something in storyboard?

@eskimo Thanks for the links! Sorry, I've got a couple more questions: So "Development Language" is the language used when the app doesn't support a language the user picked in his settings (as you said, the "fallback"), okay. If the "Base" language is active, the link says that they should be the same but what if the app is meant to be used in e.g. French but also supports English for everyone else? If a user's settings only list English, the app would be displayed in English but wouldn't that mean that the base language (French) and development language (English) are different? In my app, by editing the labels,... in the Interface Builder, I've apparently been writing everything into "Base" (2 files), while "English - Development Language" hasn't got any files connected to it. The second link also mentions specific regions and that if a user specificies e.g. Canadian French (fr_ca), which isn't supported by the app, it'll try to load regular French (fr) instead. But what if the app only supports "fr_ca" and the user uses Swiss French (fr_ch), does that still work (and load "fr_ca") because the app recognizes that they are based on the same language? Tbh, I'm still not sure how the "Base Localization" works exactly. In the images on the first website you linked (and in a lot of older screenshots I found on e.g. Stackexchange) there's always only "English - Development Language" in the list (even with the box below ticked) and, according to that link, base localization adds the files to it. But in my Xcode 12.5 project (and also older test ones) there are 2 different list items: 1. Base and 2. English. I can only get rid of "Base" by unticking the box and then it asks me if I want to move everything into "English", which I already tried yesterday but it gave me an UTF-16 error and didn't do anything. In what case scenario do you actually want to tick the "Base Internationalization" box in Xcode?

@Claude31 You're right, it's better to only reload the previous and the current row of course. Do you know of another way to do what I described? As I said, I haven't come across anyone doing anything like this before (or even anything similar, apart from the phone book apps), which does seem a bit weird.

I see, it just looks similar. Any reason why you don't "like" the "instantiate UIView" way? When would you recommend using a UIView over a UIViewController? When it's just a really small thing that's added, so filling less than half of the screen? Or does it depend on what it's added to, so if it's basically a stand-alone thing?

Thanks for your reply! Any reason why you don't "like" the "instantiate UIView" way? I know how to do it that way but I also know that you have to add that new view as a child and I'm not sure how that would work as a popup that's supposed to be displayed above everything. If this was the preferred way of doing it, then I'd have to look into that more, that's why I asked this quesiton. When would you recommend using a UIView over a UIViewController? When it's just a really small thing that's added, so filling less than half of the screen? Or does it depend on what it's added to, so if it's basically a stand-alone thing? I don't need any animations, it's fine if it just "pops" into existance, it's more important that it looks like a UIAlertController, which is going to be "fun" to replicate. so if you make your custom popup as a subclass of UIViewController, it may be easier to switch from UIAlertController to your custom popup Doing it that way I'd subclass UIViewController of course (and create a new scene in storyboard) but sorry, what do you mean exactly? The new popup is going to be called by a button that's created in a regular UIViewController.

You can still select wheels in iOS 14? That's good to know, thanks! If I select one of the pickers in storyboard, then there's a "Builds For" option in the inspector. Changing that from "Deployment Target (12.2)" to e.g. "iOS 14.0 and Later" doesn't change anything though, the pickers still look like the old wheels and if I then start an iOS 14 simulator (like the iPhone SE2), the pickers look like the new "click me" ones. I know that there was a way to make the UI elements in storyboard change their look according to the version you pick but I can't seem to find that setting anymore.

I just got the same error message while building an old (Xcode 11) project in Xcode 12. Cleaning the project with "shift - cmd - k" (as suggested by vladimir1983) fixed it, no need to change any settings or restart Xcode/the Mac.

Never mind, now all of sudden both updates complain and it won't let me start either of them!!! I even cleaned the damn Firefox cache to free some space!

Update: Yesterday I also downloaded the "Big Sur" update, which was about 13gb but apparently "only" uses 12gb according to "applications". After the download was done the app store let me start the Xcode update just fine (had to pause it, so not installed yet). But now the OS update complains that it needs more space! I emptied the trash cash (mostly small files) and now there are almost 32gb left but it's still complaining! There isn't anything else that I can delete! I've also got a Win 10 PC with a 128gb SSD and there's a ton more data/apps on it but I've never had a problem like this with it, not even while updating from Win 7 to Win 10! Wtf is going on with these updates?!

Same problem here! I've got a Mac Mini 2018 with 128gb, which had 17gb left but it still gave me that error message. I only use it for Xcode, so there isn't any random data, apart from a couple of images, which include a single wallpaper and small-ish test files. I deleted a bunch of pre-installed apps(like Garage Band and iMovie - these were at least 5gb) and also a lot of simulators (no idea why they even existed) and two old iOS versions. Now there are 40gb left but it still displays the same message! I even installed DaisyDisk but there's nothing more I can delete without deleting Xcode itself! The download for Xcode 12.4 is only 11.6gb! This is ridiculous!