Hello, TestFlight is completely blocked for my account. The beta contract appears to be missing or detached on Apple's backend. Symptoms: Internal testing: builds appear in TestFlight, but installation fails with "The requested app is not available or doesn't exist." External testing: submitting a build for beta review (via App Store Connect UI and the API) returns: { "errors" : [ { "status" : "422", "code" : "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title" : "Beta contract is missing for the app.", "detail" : "Beta Contract is missing." } ] } I am the Account Holder. All agreements are active with no pending items in App Store Connect, on developer.apple.com, or in the Apple Developer app. The build is VALID, Test Information is complete, export compliance is done, and fresh builds don't help. I have an open support case that's been in the queue for a while and this is blocking all beta testing. A nearly identical issue was recently resolved on these forums by a DTS engineer — could someone verify whether the beta contract for my account needs to be re-provisioned? Apple Support Case ID: 102925396507 Thank you!

Hi, I’m experiencing the 422 Beta error every time I try to install my TestFlight build. App information: App name: Stallkoll Bundle ID: se.stallkollapp.app Apple Developer Program: Individual Account Distribution: TestFlight Build uploaded using Codemagic Apple Support has already confirmed that my Apple Developer account verification is approved, and all required documents have been accepted. I have already tried: Creating multiple new builds. Removing and re-adding myself as a tester. Reinstalling TestFlight. Logging out and back into my Apple ID. Confirming Agreements, Tax and Banking are complete. Waiting over a week. Contacting Apple Support several times. In Codemagic, the upload finds my app correctly, but during App Store Connect distribution I repeatedly see: “Did not find build matching uploaded version yet, it might be still processing. Waiting to try again…” The build eventually appears in TestFlight, but it still cannot be installed and always results in the 422 Beta error. I’ve now been blocked for over a week and really need to release my app. Has anyone experienced this issue, or could someone from Apple please investigate whether there is something wrong with my App Store Connect account or TestFlight configuration? Thank you!

Has Apple ever offered the final public release of an OS to a limited group of Developer Beta users before the official public rollout? I've also heard claims that these early releases or invitations are only sent to owners of Pro models (for example, iPhone Pro models). Is there any official information confirming this, or is it just a rumor? I'd appreciate clarification from anyone familiar with Apple's release process.

Same here. I have exactly the same issue. App: Stallkoll (Apple ID: 6758069449). Codemagic returns: HTTP 422: Beta contract is missing for the app. Contract is missing. TestFlight shows the latest build as Approved and Ready to Test, but installation fails with: “The requested app is not available or does not exist.” A previous build installed successfully, but all newer builds fail. All agreements, banking, tax information and DSA verification are complete. The build is valid and assigned to the TestFlight testing group. Could an Apple engineer please verify that the Beta Contract is correctly attached to my App ID and re-provision/re-attach it if necessary? This appears to be the same backend issue affecting other developers. Thank you.

So my iPad 10 is on iPadOS 27 and if you go to Settings and click General, it says “View and manage settings for Device“ instead of saying what you are using.

While testing the watchOS 27 beta, I noticed that the standalone Walkie-Talkie app has been removed from the system. Walkie-Talkie has always been a great, lightweight way to stay connected. Much like Digital Touch, it’s one of those quick, low-friction features that makes the watch feel uniquely personal for communication throughout the day. I am really hoping its absence is just a temporary beta omission rather than a permanent retirement of the feature. I have already submitted a request via Feedback Assistant asking the engineering team to consider keeping it in the final release. If you also rely on this app for quick wrist-to-wrist updates, I highly recommend submitting your own feedback ticket to let the team know there is still an active user base for it. (FB23040695) Has anyone else ran into this or found an official note from Apple regarding its removal in the release notes? Hopefully, we will see it return before the public release this fall. Over and out!

On the IOS 27.0 on my IP 16PM, I see it reduce heat significantly and after the next update, I see many bugs like keyboard stuck on tiktok app and heat more than 27.0. May I know it is the tiktok app issue or bug?

Im unable to deploy Xcode 27 beta code to an iPhone 17 pro The build is successful but its not loading

Hi everyone, I'm encountering an issue with App Store Connect when using a beta version of Xcode and macos. Environment macOS: macOS Golden Gate Beta 27.0 Xcode: Version 27.0 beta 2 (27A5209h) Flutter: 3.41.9 App Store Connect: Production Issue I built my Flutter iOS application using the latest Xcode beta. The archive completed successfully. The build uploaded to App Store Connect without any errors. The build finished processing successfully. The build was available in TestFlight. However, when I tried to add the build to an App Store version and clicked "Submit for Review", App Store Connect displayed an error indicating that builds created with a beta version of Xcode cannot be submitted for review.

The release notes at https://developer.apple.com/documentation/xcode-release-notes/xcode-27-release-notes mention that the minimum deployment target is macOS 11.0, but Xcode itself says that only macOS 12.0 to 27.0 are supported. Which one is correct, Xcode or the release notes? I created FB23514411.

Hi, I have listed below the Feedbacks for Xcode 27, please have a look at it, considerable time was spent on filing these feedbacks, thanks! Environments All of them were tested on the environment: macOS 26.5.1 (25F80) Xcode 27.0 beta (27A5194q) Feedbacks FB23133706 (Git stage tab) FB23132869 (markdown - code block) FB23132403 (markdown - search) FB23078039 (stash - slow / unresponsive) FB23077930 (stash - allow multiselection) FB23055381 (Run destination - Clear recents) FB23041713 (SwiftUI preview - SwiftData) FB23033844 (Bundle ID) FB23033231 (Device Hub - sizes)

Hi, Feedback: FB23494579 Using StoreView / ProductView on iOS 27.0 simulator / device hub throws the following error: Error: Accessing State<ProductViewEventConfiguration>'s value without being installed on a View. This will create a new ProductViewEventConfiguration instance each time. Environment macOS 26.5.2 (25F84) Xcode 27.0 beta 2 (27A5209h) Simulator / Device Hub - iPhone 17 Pro (iOS 27.0) Screenshot

Hello, I updated my Apple Watch SE 3 (GPS + Cellular, 44 mm) to watchOS 27 Developer Beta (Build 24R5289n) and noticed what appears to be a change in the Digital Crown behavior. After the update: • A single press of the Digital Crown now shows fewer applications, which seems consistent with the changes announced for watchOS 27. • However, a double press of the Digital Crown no longer opens the App Switcher as it did previously. • As a result, I can no longer access the interface that allowed users to view recent apps and force-close applications by swiping them away. Before updating, double-pressing the Digital Crown opened the App Switcher and provided a way to close running apps. That functionality now appears to be missing. I would like to know whether: This is an intentional design change in watchOS 27. This is a known issue in the current Developer Beta. There is a new gesture or workflow for accessing recent apps and force-closing applications. Device: Apple Watch SE 3 (GPS + Cellular) 44 mm Aluminum Model: MEPJ4LW/A Software: watchOS 27.0 Developer Beta Build: 24R5289n The behavior is reproducible after restarting the watch. Thanks.

My iPhone 14 Pro (running iOS 27 beta 1) is not booting after discharge of battery (due to not being used for about 10 days). How to restart and update to beta 2 or use it otherwise? I have kept it connected to wall outlet charger for the past 2 hours, and have tried Forced restart (press and quickly release the Volume Up button, press and quickly release the Volume Down button, then press and hold the Side (Power) button until the screen goes black and the Apple logo appears). But nothing works, and the iPhone remains dead.

I was hoping this was fixed in Beta 2, but I am having the same issue. I run my app: on a simulator device Device Hub opens Begins installing the app I see the icon and it starts to fill in The launch screen loads and never finishes loading. I then stop running app in Xcode. Device Hub still shows launch screen I restart device in Device Hub I then can open the app and test Anyone else experiencing this? I would really like to solve this as it makes testing changes a frustrating experience. Because I then have to close Device Hub and Xcode to simulate again.

still no sign of the new siri no app no nothing im on the ios 27 beta 2 and iphone 15 pro max what is this apple

It's been over 2 weeks and I still don't have the option to download the Mac or iOS 27 betas. All I see is the option for the current public betas for Tahoe and iOS 26. I am a registered developer and thought I would get access to the betas. I've submitted 2 tickets through the feedback assistant and both were closed with the comment "investigation complete - working as designed". I don't know where else to go. Is it true that not every developer gets access to beta software or that developer betas are released in phases? I've never read that anywhere nor heard that once released that beta software isn't available to all developers in the Apple dev program (not the public beta program). Can anyone shed light on this? is this true? Are betas released in phases to developers? At this rate as a developer I will have to wait until the public beta. Help!

SUMMARY iOS16 Beta system local network permission pop-up alert does not display STEPS TO REPRODUCE Install My App for the first time on iOS16 Beta system devices Open the My App and you will first see the local network permissions introduction page On this page we will send UDP broadcast packets RESULTS The user should then see the local network permission authorization pop-up alert，but there is no actual popup in iOS16Beta，but it works fine on the previous version of iOS system NOTES On the previous version of iOS system, by sending UDP broadcast, the local network permission authorization pop-up alert can be triggered normally, but in iOS16Beta, the pop-up alert will not appear, and the local network permission switch will not appear in the App-related system settings. I don't know how to deal with this problem. I have tried many methods and it doesn't work. Can someone help me.

I’m seeing a regression in macOS 27 beta when using SwiftUI LocalAuthenticationView. When an LAContext is attached to LocalAuthenticationView, subsequent policy evaluation fails immediately with: Error Domain=com.apple.LocalAuthentication Code=-1007 NSDebugDescription="Caller is not Apple signed." NSLocalizedDescription="Authentication denied." The same policies work when evaluated on a plain LAContext that has not been attached to LocalAuthenticationView. Minimal shape of the failing path: @State private var context = LAContext() LocalAuthenticationView(context: context) { EmptyView() } context.evaluatePolicy(.deviceOwnerAuthenticationWithBiometrics, localizedReason: "Unlock") { success, error in print(success, error as Any) } This affects Touch ID unlock in our macOS app. We currently work around it by detecting LAErrorDomain / -1007, removing LocalAuthenticationView, and asking the user to manually start Touch ID with a fresh LAContext. Filed as Feedback: FB23262713 Could someone from the beta / LocalAuthentication team confirm whether this is an intended restriction for LocalAuthenticationView, or a macOS 27 beta regression?

With the 27 OSes using UserDefaults.standard.integer(forKey: ) can cause a crash with EXC_BAD_ACCESS (code=1, address=0x0) It has been seen on a Multiplatform app, up to now tested on iOS/iPadOS and visionOS 27 Beta 1. In our code we use UserDefaults.standard.integer(forKey: ) from a singleton called during the SwiftUI app init(), and we don't know yet if this is the only moment there is a crash as we can't go farther. The API should return 0 if it can't get a value. There is no reason the app should crash if the API conforms to its contract. Running the same code from Xcode on iOS 26 runs it without issue. FeedBack FB23310748