We are still unable to create a new version for previously failed versions; it may be due to the initial bug, and our data may be corrupted, so the fix may work for new versions, as Apple Engineer posted today. We contacted Apple a week ago (102222678277) and still have no solution or response. I'm not sure if Apple understands the complexity and urgency of this situation. Please, guys, at this time, you know what is going on. Run a query to look for thousands of corrupted versions and make an effort to fix them. After all, you broke it badly.

Problem persist even after the planned maintenance, not sure what is going on. 6 days without a solution on a critical matter that is widely used.

Same issue here; Apple changed something. It looks like when you create a new version, the process is being scheduled now, so it may take a few seconds to appear; it never happened before. The problem that we are still facing is that some new versions were either stuck or had data inconsistencies, and we are still unable to create new versions for those apps that have already failed. If you attempt to create a new version with same version as failed, you will get version already exists, if you tried another one, you get an unknown error. Please avoid doing the schedule thing, makes no sense and cause a lot of problem. Please run a query and delete all those version for everyone and revert the last changes. I have contacted Apple already, but we need to deliver urgent fix. We tried to user API and see if the version exists, but it doesn't.

Do you get a solution? App could be opened from "Share" sheet, like open a file with the app, logic of moving file may be at the main thread which cause time elapsed out (10 seconds). I couldn't replicate it but it may be an iOS bug.

I just uploaded a new binary and now everything seems to works fine.

Same problem here with a widely used class to access the keychain (KeychainItemWrapper.m). iOS version passed without issue, but the MacOS version failed due to Non-public API usage, looks like a false alarm but it needs to be fixed by Apple. I sent an email about this problem on 19 Feb, I got a response asking for screenshots(?!!) and I responded back yesterday and waiting for a solution. Let me know if you find a workaround.ITMS-90338: Non-public API usage - The app references non-public symbols in Contents/MacOS/: _SecItemAdd, _SecItemCopyMatching, _SecItemDelete, _SecItemUpdate, _kSecAttrAccount, _kSecAttrDescription, _kSecAttrGeneric, _kSecAttrLabel, _kSecAttrProtocol, _kSecAttrServer, _kSecClass, _kSecClassInternetPassword, _kSecMatchLimit, _kSecMatchLimitOne, _kSecReturnAttributes, _kSecReturnData, _kSecValueData