This seems to be an ongoing issue. I have 1 app and one TestFlight submission waiting for almost a month.

Yes, I have had an app in review for almost a month too. It's frustrating as its a resubmission to address some issues with an In App purchase. I am sure this won't be the last go around, so if it finally does get reviewed as I have to wait another month to fix some issue. General Information Bundle ID com.ellin.SessionTracker SKU 1234 Apple ID 6757566209 I also have another test flight app that has been waiting for review for quite some time as well. I dunno why those seem to be so delayed as well since they aren't supposed to get the same level of review.

I have had an app in waiting for review for almost 10 days. I also have a TestFlight build of another app that’s been in review for 4 days. the test flight delay is nuts.

Our SSH certificates are in OpenSSH format (RFC 4253), not X.509. These use a custom binary encoding that SecCertificate doesn't understand. Since kSecClassCertificate expects X.509 DER format: Should we store OpenSSH certificates as kSecClassGenericPassword with descriptive metadata? Is there any Keychain support for non-X.509 certificate formats? Or is the recommendation to keep them as files and only move X.509 TLS certs to Keychain? Example OpenSSH Certificate (text format): ssh-ed25519-cert-v01@openssh.com AAAAIHNzaC1lZDI1NTE5LWNlcnQt... Our current thinking is to store these as generic passwords: let query: [String: Any] = [ kSecClass: kSecClassGenericPassword, kSecAttrService: "com.teleport.ssh.cert", kSecAttrAccount: "\(cluster).\(user)", kSecAttrLabel: "Teleport SSH Certificate", kSecValueData: sshCertData, kSecAttrAccessible: kSecAttrAccessibleWhenUnlockedThisDeviceOnly ] Is this an acceptable approach for non-X.509 certificates?

So in this context an app distributed by test flight would be the same an app distributed in xcode?