@Toonetown the login loop is indeed a WindowServer error: WindowServer_2020-07-17-111658_-Mac.crash - https://developer.apple.com/forums/content/attachment/a365f528-79ba-434e-876f-97ba17d807db It's funny because I had a Parallels VM with Big Sur working properly. The one that worked was an updated Catalina, I only needed to replace the NVRAM.dat file with Catalina's VM one. But at some point (days) it was affected with the login loop. Since then I've tried multiple installations and always result in the login loop.

I noticed Big Sur default apps have the old icon (Catalina) in the resources. This icon is present both in the icns form and in the Assets.car. Also in this Assets.car file is present the new and rounded icon, that shows in Big Sur. If you copy/paste one of those apps to Catalina you'll see the old icon though. So it might be possible and makes sense they give us this possibility.

I'm not seeing this behaviour. In Big Sur the toolbar icons are centered in the new apps.

Thanks @dawn2dusk & @peterguy. Just implemented this in the create-dmg script: https://github.com/create-dmg/create-dmg/commit/f75cc032d77672adab60cebd49db000a8ff7446a

Facing this issue since Xcode 13 betas. Disabling Bluetooth in the iPhone temporarily fixes the issue for me. With the Control Center Bluetooth icon in grey, no need to fully disable it in the Settings app.

For what it's worth, the reported feedback ID is FB10006890.

Turns out it was a missing certificate (and private key) for signing the binaries, result of migrating from one Mac to another. Odd the distribution assistant did not warn about that.

Same issue here. Any update?

Seems like that. In my case I received various reports: iPad14,3 reached 4294.97 writes iPad7,2, iPad8,7 and iPhone13,4 all reached 1073.74 writes Nut sure if it is version dependant or maybe storage size dependant but the limit can change. I've just asked for code-level support to Apple, will update with the response.

For what is worth it started working after a few weeks with no further actions on my end. So maybe they review/activate those manually on their part? Not sure but my advice: patience.

I was welcomed with this issue today. Been publishing this app properly signed for years. It's even visible in the package review that the binaries have this flag enabled but the build is being blocked with this message: ITMS-90296: App sandbox not enabled The following executables must include the 'com.apple.security.app-sandbox' entitlement with a Boolean value of true in the entitlements property list: [[com.aone.keka.pkg/Payload/Keka.app/Contents/MacOS/keka7z ...

+1, feedback sent

Similar to https://developer.apple.com/forums/thread/705472, I had to create new certificates and resign all binaries. Probably this was caused by an expired certificate.

4 years later. I'm filling a feature request in the Feedback Assistant. Please consider doing the same if you want this to be fixed.

Same here, Xcode 15.0.1, macOS 13.6.1 🥲