“xcode github”

Same issue here. It started about 24 hours ago and I haven’t found a solution yet. Things I have already tried: • Rebuilding the app multiple times via GitHub Actions • Regenerating certificates / Match secrets • Waiting 24 hours after upload • Deleting the app and reinstalling • Deleting and reinstalling TestFlight • Restarting the phone multiple times • Verified I’m assigned to the internal tester group in App Store Connect • Confirmed the build status is Complete in App Store Connect The build installs and runs on my phone, but when I open the app page in TestFlight it shows “Couldn’t Load App – TestFlight is currently unavailable.” Also noticing the Apple Watch companion app will not install (stuck installing).

Thank you for your post. If I’m not mistaken this means that at the time when Xcode 27 becomes mandatory, the app’s deployment target must be iOS 13 or higher since the UIScene class and Info.plist keys are iOS 13.

It sounds like you're encountering an issue with the ReLU activation function on the Mac M4 using TensorFlow-Metal. Let's go through a few steps to troubleshoot and potentially resolve this issue: Potential Causes and Solutions TensorFlow-Metal Version Compatibility: Ensure that you are using the latest compatible version of TensorFlow-Metal. Sometimes, bugs are fixed in newer releases. Check for updates via pip: pip install --upgrade tensorflow-macos tensorflow-metal ReLU Implementation in Metal: TensorFlow-Metal might have a different implementation of ReLU that doesn't handle edge cases like floating-point precision issues with exactly zero values. You could try a workaround by slightly offsetting zero values before applying ReLU: def custom_relu(x): return tf.maximum(x, 1e-10) model = tf.keras.Sequential([ tf.keras.layers.Input(shape=(10,)), tf.keras.layers.Dense(5, activation=custom_relu) ]) Environment and Configuration: Double-check that TensorFlow is correctly configured to use Metal. You can explicit

Based on the error messages you're encountering in Xcode, it seems like there are two main issues to address: nwprotocolinstancesetoutputhandler Not calling removeinput_handler: This error typically indicates a problem with how network connections are being managed using Apple's Network framework. Specifically, it suggests that an output handler was set on a network protocol instance without a corresponding removal of the input handler, which could lead to resource leaks or crashes. Steps to Resolve: Ensure that every call to nw_protocol_instance_set_output_handler is matched with a call to nw_protocol_instance_remove_input_handler when you're done with the connection or when the connection is closed. Review the lifecycle of your network connections to ensure handlers are properly managed, especially in asynchronous or error-prone paths. Check if there are any closures or network operations that might inadvertently leave handlers dangling. com.apple.modelcatalog.catalog sync: connection error: This e

Hi, To provide some context on how this view fits into the overall layout: the map is displayed inside an info box that can be swiped away. When no swipe gesture is in progress, the map should remain interactive and allow zoom gestures. While the info box is being swiped, interaction with the map should be disabled. The map always displays at least one marker. You can find a more complete code example and a screenshot here: import MapKit struct ContentView: View { @State private var offset = CGSize.zero let position = CLLocationCoordinate2D(latitude: 51.5074, longitude: -0.1278) let span = MKCoordinateSpan(latitudeDelta: 5.0, longitudeDelta: 5.0) var body: some View { ZStack { let drag = DragGesture() .onChanged { g in offset.width = g.translation.width offset.height = g.translation.height } .onEnded{ _ in withAnimation { offset = .zero } } VStack(spacing: 0){ Map(initialPosition: .region(MKCoordinateRegion(center: position, span: span)), interactionModes: [.zoom]){ Marker(London, coordinate: positio

The Prompt stream failed: Agent has been closed error can occur when your project is in a macOS privacy-protected directory like ~/Desktop, ~/Documents, or ~/Downloads. macOS should prompt you to grant Claude access to these locations, but if the prompt doesn't appear or was previously denied, the agent can fail with this error. Workaround: Move your project to a non-protected directory such as ~/src, then reopen it in Xcode.

We do not use CallKit. The call is handled entirely using a custom in-app call UI. This is a bad idea. It's going to significantly complicate your app’s audio logic and, most practically, it means that ANY other incoming call from ANY CallKit app will IMMEDIATELY interrupt your app’s audio. It's also going to allow a variety of other odd edge cases which will be similarly disruptive (for example, now playing activity can interrupt your calls). The PRIMARY reason CallKit was originally created was so the system could properly arbitrate and manage the audio of VoIP apps, preventing all those edge cases. However, the exact rules and thresholds for these violations are not clearly documented, so I’d like to ask a few questions to better understand the expected behavior. The basic policy rule is that your app is not required to report a call if it either: Is already on a call. Is in the foreground. However, in practice, both of those criteria are much harder to implement than they seem. The problem here is that yo

I Have the same issue. MacOS 26.3.1, Xcode 26.2, iOS 26.3.1 iPhone 17 Pro Max and WatchOS 26.3 Apple Watch S10.