A Summary of the WWDC25 Group Lab

Hi all, We can’t install our app from TestFlight. The app is visible in TestFlight for invited internal testers, but tapping Install fails immediately with: “The requested app is not available or doesn’t exist.” --Setup-- Distribution: TestFlight – Internal Testing Internal group created and testers added (invite accepted) Build processing status in App Store Connect: Complete TestFlight build status shows: Ready to Submit / Prepare for Submission Minimum iOS deployment target: iOS 15.0 Version/Build: 1.0.0 (1) What we tried Confirmed tester is signed into TestFlight with the same Apple ID email that was invited Removed/added testers to the internal group and resent invites Reinstalled TestFlight, signed out/in Verified build is assigned to the internal group Set and saved Monetization → Pricing and Availability → App Availability (All Countries/Regions) Question Has anyone resolved this issue? Is there a known TestFlight/App Store Connect stuck state that causes this error even for

Hi everyone, I'm experiencing an issue with TestFlight where internal testers are not receiving build invitations, even though the builds have successfully completed processing in App Store Connect. Builds Status: • Multiple builds (Build 10, 11, 12) show Ready to Submit status in App Store Connect • Build 9 is in Waiting for Review status • All builds show 2 Invites sent • However, the new builds (9, 10, 11, 12) are not appearing in TestFlight for the internal testing group Internal Testing Group: • Group name: Test (Internal Group) • 2 Testers configured • 7 Builds total in the group • The group shows builds 1.0 (2) through 1.0 (8) as Testing status • New builds (9, 10, 11, 12) are missing from TestFlight What I've Tried: Manually adding the internal group to the new builds using the Add Group dialog(the Add button is inactive) The system shows 2 Invites sent in App Store Connect Checked TestFlight app on testers' devices - no new build

Have had issues all day with the delayed Processing times as seen by other posts on this forum. But after my app has completed Processing (took 4 hours, usually takes 10 minutes), the build doesn't show up for Internal Tester. Internal tester usually gets all app updates, but when I try to add Group to build, the internal tester group is greyed out. If I try to add individual tester to build I get An error has occurred. Try again later.

Hi everyone, I'm working on an app that stores multiple secrets in the Keychain, each protected with .userPresence. My goal is to authenticate the user once via FaceID/TouchID and then read multiple Keychain items without triggering subsequent prompts. I am reusing the same LAContext instance for these operations, and I have set: context.touchIDAuthenticationAllowableReuseDuration = LATouchIDAuthenticationMaximumAllowableReuseDuration However, I'm observing that every single SecItemCopyMatching call triggers a new FaceID/TouchID prompt, even if they happen within seconds of each other using the exact same context. Here is a simplified flow of what I'm doing: Create a LAContext. Set touchIDAuthenticationAllowableReuseDuration to max. Perform a query (SecItemCopyMatching) for Item A, passing [kSecUseAuthenticationContext: context]. Result: System prompts for FaceID. Success. Immediately perform a query (SecItemCopyMatching) for Item B, passing the same [kSecUseAuthenticationContext: context]. Result: System pro

I have been waiting for several months now for my enrollment to finish processing. I have reached out several times and was told that a new group is handling enrollment and there is no way to reach them. How can this issue be escalated??

It’s the small things that make a difference, and the three dots at the top of the screen in Safari and Chrome are such examples. I’ve already accidentally deleted several tab groups by accident and try to relearn browsing is harder than it should be.