Posts

Post not yet marked as solved
1 Replies
In my original post I was mistaken regarding changing the bundle id – my original bundle id has the issue, but if I change it (and tab out of the field before building) then it will run with a different bundle id. With my original bundle id, In console, it logs: "Client com.apple.runningboardd trying to look up container 2:com.getkeyfree.keyfree.rental-test with ambiguous user identity" and attempts to read various files from the root home directory, e.g.: /private/var/root/Library/Containers/com.getkeyfree.keyfree.rental-test/.com.apple.containermanagerd.metadata.plist However, after deleting all provisioning profiles locally from ~/Library/MobileDevice/Provisioning Profiles/, deleting my certificate from the developer portal, and attempting to get Xcode to recreate the provisioning profile, it still doesn't work.
Post marked as solved
53 Replies
@paulr9773, I installed from a DMG. Once you have the Big Sur installer, you can create a DMG as follows: cd ~/Downloads/ sudo hdiutil create -o InstallMedia -size 20G -layout SPUD -fs HFS+J -type SPARSE sudo hdiutil attach InstallMedia.sparseimage -noverify -mountpoint /Volumes/install_build sudo /path/to/install.app/Contents/Resources/createinstallmedia --volume /Volumes/install_build The next step might fail. If so, manually eject using finder. sudo hdiutil detach /Volumes/Install\ macOS\ */ sudo hdiutil convert InstallMedia.sparseimage -format UDZO -o InstallMedia.dmg sudo rm InstallMedia.sparseimage In VMWare, create a new VM and customise, setting the hard drive to at least 60GB. Boot from the install DMG and run disk utility. Select the hard drive and erase as AFPS, then the drive should go from 40GB capacity to 60GB. Then quit disk utility and install.
Post marked as solved
53 Replies
It works in VMWare Fusion! You need to expand the default drive size of 40GB to 60GB and then use disk utility to erase it (as AFPS), then install as normal.
Post marked as solved
53 Replies
I created a bootable DMG to attempt to install from scratch, but the same problem occurs. I also tried erasing the disk and formatting as APFS, but still the same error. It seems it is an issue with Big Sur installer/parallels.