build disappears

You can edit the questions by creating a new release without submitting the release for formal review. But I am not sure if that is enough to be considered as fulfilling the requirement. Anyone knows? In addition, for one of my apps, apple has auto computed the age rating and I found it to be accurate. So do I even need to add a new build and re-update age ratings?

So, I got some more time to look at this today and need to change my answer a bit. Let me actually jump back to here: All the documentation I was able to consult says that macOS is designed to use up to all available storage on the startup disk (which is the one I am using since I have only one disk and the available space aforementioned reflects this) for swapping, when physical RAM is not enough. Did you actually see this in our documentation and, if so, where? If any of our modern documentation actually says that we do this, then that's something I'd like to clean up and correct. So, let me go back to the idea here: macOS is designed to use up to all available storage on the startup disk That's the classic” UNIX system machine swap and, historically, it's how Mac OS X originally worked. However, the downside of this approach is swap death in one of two forms: Soft, meaning the system has slowed down to the point that the user is now no longer willing to use the machine, even though it technically still wor

Same concerns here. I have over a dozen apps and it's not practical to submit new builds for every one just to update rating metadata on AppStoreConnect. This has got to be a serious goof on Apple's part.

So, just to confirm: Apple sent an email to developers with the subject: Final reminder: Answer the updated age ratings questions. That email says: We’re reaching out because you have not provided responses to the updated age ratings questions in the App Information section of your app in App Store Connect. If you don’t answer these questions by January 31, 2026, you won’t be able to submit app updates in App Store Connect. Right, so if we don't submit these new age ratings we cannot submit new app updates after January 31st 2026, but in order for us to change those age ratings we have to submit new versions of our apps? Am I really being told to build and archive a new version of each of my apps just to update the age ratings? This is what I currently see on one of my apps: so this is great... And, just to make it even more complex than it needs to be, the email also says this: Please also note that the Texas SB2420 legislation goes into effect January 1, 2026. Under this law, making an age rating c

In my case the crash was caused indirectly by animating the viewcontrollers change inside splitViewController(_:collapseSecondary:onto:). Not sure if that's allowed by UIKit, but similarly to your case this code has worked for more than a decade without problems until 26.1. Anyway, after removing the animation the issue disappears.

Thanks for your post, looks like a certificate issue with flutter by looking at the error? You should check with the support resources provided by the 3rd party to get assistance with their software as I am sure they'll know the issue. Unless another developer in the forums has experience with the third-party and can provide assistance. I would recommend to get into the Flutter support channel as you are using a windows pc as their 3rd party tool to see how to configure it to submit your build. Albert Pascual
  Worldwide Developer Relations.