Hello, I also had difficulties with Disk Utility, the visibility of drives and the newer concept of containers. I usually go to the top-most drive/container entry and chose delete from the menu. I do not entirely trust their plus/minus buttons. You would have some security deleting options too, — unless for a SSD :-(which I learnt from this document) https://support.apple.com/guide/disk-utility/erase-and-reformat-a-storage-device-dskutl14079/mac I suppose, this is the one you have been following already, just in case… Good luck ;-)

Hello, Flo, Did you format your external SSD with Apple's most modern file system (which, if I am not mistaken, should be AFPS)? Kind regards ;-)

Hello, Did you check your Developer account? Sometimes, because of changes in the Developer agreement, you need to accept and agree to the new version first, before you can properly install any new Betas… Kind regards ;-)

Hello, Dragon, My FCPX is running normally under Big Sur 11.0 Beta, my FCPX is up to date. When installing this Neat Video v5 denoiser plug-in, which was only possible from the command line, it badly crashed my whole machine repeatedly, when trying to test for or run on the GPU. On CPU only it is working fine, but this is not really what I wanted. Since this plug-in is not distributed via the Apple Mac App Store, I just hope that these guys are trustworthy… See you ;-)

Hello, I is working now as intended, they fixed it in the following Beta ;-)

Hello, zmak, Oh, and I forgot about one thing. If you are desperate ;-) Deleting the watchOS Developer Profile on Watch, un- and then re-pairing your Watch, might bring up the dialogue asking you (on Watch) whether you trust your connected developer Mac. I was under the impression, once this question popped up and was successfully answered (again), the build and run process had less problems. Your trust in your Mac should be stored for Watch development anyway deep in their developer backyards, but I do not remember that I was asked whether I trusted my computer, only because I installed the last and current Beta of watchOS. I suppose, it should work properly out of the box, but since un-pairing and re-pairing is only a question of minutes on Watch Series 5, I think it is worth giving it a try in order to (re-)invoke this question of trusting your Mac. Kind regards ;-)

Hello, zmak, Unfortunately, yes. But it was already mentioned in the watchOS Release Notes. Good that you are already on Xcode 12 Beta. My own experience is, that being on the Big Sur Version 11.0 Beta is a MUST if you want to run watchOS 7.0 on-device. In the Release Notes, there are some nice euphemisms stating that you might consider running it under Big Sur… That is Apple jargon telling you, you should better do so ;-) In your Library on Mac, you could also delete the Derived Data directory under Developer that will be re-created when you compile new projects. I usually do that from time to time in order to have a clean start. When re-opening your project in Xcode 12 Beta, in Preferences go to your Account information and select your developer name and/or team information. I had the impression that clicking the Download Manual Profiles button resulted in better and quicker compilation of projects running on-device. It would usually start earlier deploying the app on-device… Under Product > Scheme > Manage Schemes, I usually delete any schemes and click onto the Autocreate Schemes now button. Last but not least, it seemed to be beneficial to have an iPhone app to be installed first on iPhone and only then switch to the watchOS target build when you have it run at least once. Even if you have set a Supports Running Without iOS App Installation check mark (Targets > …WatchKit Extension > General > Deployment Info), re-check on-device whether the app has been properly installed on Watch, — or the app of your compiling project already shows up in the iOS Watch app (being installed already or available for installation). Toggling these settings there (in the iOS Watch app) might influence how quickly apps start eventually off on-device. Yes, I know, it is a cumbersome long process to run builds on-device for the time being. I cannot even tell you, which part of my hints does the trick… Once you see the loading indicator on Watch already, only the device getting dark again might interrupt you for some more time. But it clearly indicates that it will work from this moment on. If it is getting stuck there (more than twenty seconds), I re-build for a second time. Normally, this will result in a much quicker build on-device. From that moment on, it usually builds properly several times in a row. I hope that this will help you a bit, please let me/us in the forum know about your progress and your own observations. Thank you, kind regards ;-)

Hello, Viktor, Apple is not really good at this moment to tell you that you should consider running Xcode 12 Beta under the macOS 11.0 Big Sur Beta… Please consider installing Big Sur Beta in another test partition of your SSD/Hard disk. https://support.apple.com/en-us/HT208891 My difficulties with on-device watchOS 7.0 beta development just magically disappeared after doing so ;-) Xcode 12 Beta is very much made for Big Sur — and it is not really helpful that the Big Sur Beta update comes in a ”Catalina 10.16 camouflage“… This ”You have macOS 10.15. The application requires macOS 10.15.4 or later.“ is almost crying for 10.16 (which is in fact Big Sur Beta)… Good luck ;-)

Bien venu(e) chez nous aux Developer Forums, mais ici c'est plutôt en anglais ;-) Le Français te manque où exactement ? Au Mac ? iPhone ? … ? Oh là là, ça fait déjà quatre ans que tu as posé(e) cette question…

@Albaluat, Low tech issue? Wrong keyboard layout? CAPS LOCK in place while typing? Do you already see the colored macOS 11.0 Big Sur Beta Wallpaper? Did you create a new specific partition of your SSD/Hard disk? Do you boot into the correct partition? How many drives do you see in Recovery mode? Restart your Mac Immediately hold down Command-R Release them as soon as you see the Apple logo Go to the Disc Utility and verify how many partitions you have ;-) Good luck…

@DebbieD, Please don't be confused, we all started like this ;-) Me actually, years ago with the Apple ”Hello World“ sample code and Objective-c. Today, Swift(UI) is your friend. Download Xcode from the App Store on your Mac. Go to this Apple page, they will walk you through: https://developer.apple.com/tutorials/swiftui/ Of course, the Simulators are a great start, but things are getting really cool if you run your very first ”own and self-written“ app on-device ;-) Have fun ;-)

Hello, me, A copy from my other post, please consider running watchOS 7.0 Beta IN Xcode 12 Beta ON macOS 11.0 Big Sur Beta… watchOS 7.0 Beta on-device Please be aware that Apple do not state clearly enough that you would actually need to install the macOS Big Sur Beta AND Xcode 12 Beta, if you are after on-device development for Apple Watch and watchOS 7.0 Beta. As a matter of fact, this is a MUST. Compiling and building watchOS 7.0 Beta on your Watch is working then as it should ;-) No more error messages and complaining about non-installed Watch symbols. By the way, this was also the reason for failing watchOS 6.2.8 Beta builds running still macOS Catalina several days ago (simply, because macOS Big Sur Beta was not out yet and running Xcode 12 Beta alone was not good enough for watchOS 6.2.8 Beta on-device…)

Hei, Morten, me again, A copy from my other post, please consider running watchOS 7.0 Beta IN Xcode 12 Beta ON macOS 11.0 Big Sur Beta… watchOS 7.0 Beta on-device Please be aware that Apple do not state clearly enough that you would actually need to install the macOS Big Sur Beta AND Xcode 12 Beta, if you are after on-device development for Apple Watch and watchOS 7.0 Beta. As a matter of fact, this is a MUST. Compiling and building watchOS 7.0 Beta on your Watch is working then as it should ;-) No more error messages and complaining about non-installed Watch symbols. By the way, this was also the reason for failing watchOS 6.2.8 Beta builds running still macOS Catalina several days ago (simply, because macOS Big Sur Beta was not out yet and running Xcode 12 Beta alone was not good enough for watchOS 6.2.8 Beta on-device…) Ha det bra ;-)

Oh, do you mean that one, with the code??? You need to be more specific, for which platform? Which beta? How are we supposed to help you like that? Did you delete the ”old“ beta 13.x and 6.x profiles before trying to install the new current beta profiles?

Hello, kpra, I usually delete the ”old“ xOS profiles first, before downloading and installing the new ones for the iOS/iPadOS 14 or watchOS 7 betas. The new profiles should download and install properly then ;-)