Search results for

build disappears

50,294 results found

Post

Replies

Boosts

Views

Activity

Reply to VideoPlayer crashes on Archive build
As a follow up, three further points: I tried this on someone else’s machine. Same issue. So it’s not a config issue with my Xcode / machine. Secondly, one doesn’t need to go thru the archive step, just run the executable produced for the Xcode run. Issue not seen if a debug build is used.
Topic: Media Technologies SubTopic: Video Tags:
3w
VideoPlayer crashes on Archive build
I have found that following code runs without issue from Xcode, either in Debug or Release mode, yet crashes when running from the binary produced by archiving - i.e. what will be sent to the app store. import SwiftUI import AVKit @main struct tcApp: App { var body: some Scene { WindowGroup { VideoPlayer(player: nil) } } } This is the most stripped down code that shows the issue. One can try and point the VideoPlayer at a file and the same issue will occur. I've attached the crash log: Crash log Please note that this was seen with Xcode 26.2 and MacOS 26.2.
Topic: Media Technologies SubTopic: Video Tags:
1
0
368
3w
Reply to Can't Edit Age Ratings in App Information Section of App Store Connect for released App Versions
Can confirm, based on what customer support said and my actions, it seems all I had to do was add a new version in App Store Connect to get the app in an editable state to edit the age ratings. After submitting the age ratings, the warning message at the top (about updating the age ratings) did not immediately disappear, but when I checked back maybe 20 minutes later, it had gone, so it seems it worked. Did not have to upload a new build, etc, although my current builds appear expired.
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
3w
App Clip Card Still Showing After Removal
Hi everyone, I’ve completely removed my App Clip: Deleted all Advanced App Clip Experiences Removed the App Clip target from my build Removed App Clip references from my apple-app-site-association file Deleted the meta tag from my website: However: When scanning the QR code, the App Clip card still appears with: This App Clip is not currently available in your country or region. This link still works for my App Clip, which is not what I expected: https://appclip.apple.com/id?p=com.example.appclip Does anyone know why the App Clip card is still showing and how to fully remove it? Thanks!
Topic: App Store Distribution & Marketing SubTopic: General Tags:
1
0
100
3w
Advanced App Clip Main App approved but Appclip Experience Stuck in “Received” State (No Publish Option)
I am requesting assistance with an issue involving my Advanced App Clip Experience, which has remained in the “Received” state for more than few months, preventing the App Clip from becoming available when invoked via QR code. App Details App Name: Yellow Label Verification App Store Bundle ID: com.acviss.demoindia App Clip Bundle ID: com.acviss.demoindia.Clip Team ID: F2RLQ4VV59 App Version (Live): 1.4 Domain: acviss.com Issue Summary My Advanced App Clip Experience is stuck in the “Received” status. The “Publish” and “Build Assignment” options never appear, even though: The updated AASA file is correctly published at: https://acviss.com/.well-known/apple-app-site-association It contains the correct appclips → appID and paths entries It is served with the correct application/json content type Domain validation in App Store Connect shows Validated The App Clip build is already approved and live on the App Store Safari-based App Clip invocation works as expected Despite this, the Advanced App
Topic: App & System Services SubTopic: General Tags:
5
0
184
3w
Where to find sample code for SB2420 compliance and questions
I'm struggling to implement required code for SB2420 compliance. I try to learn on a very simple use case. the app is UIKit Build in Xcode 26.2 it displays a single Hello view with a button that will simply show a Good day label. I assume the app will be rated 4+. I tried the following code, using available information in Xcode (limited): import UIKit import DeclaredAgeRange // other import needed ? class ViewController: UIViewController { @IBOutlet weak var welcomeLabel: UILabel! // initially hidden override func viewDidLoad() { super.viewDidLoad() // Do any additional setup after loading the view. } func testAgeRange() -> Bool { if !isEligibleForAgeFeatures { // Not found. Which import needed ? return true // Not called from Texas } // Following code from Xcode doc… do { let response = try await AgeRangeService.shared.requestAgeRange(ageGates: 13, 15, 18) // Compiler Error: Missing argument for parameter 'in' in call // Can I add the 4 gate ? guard let lowerBound = response.lowerBound else { //
Topic: UI Frameworks SubTopic: UIKit Tags:
2
0
242
3w
Issue: Plain Executables Do Not Appear Under “Screen & System Audio Recording” on macOS 26.1 (Tahoe)
Summary I am investigating a change in macOS 26.1 (Tahoe) where plain (non-bundled) executables that request screen recording access no longer appear under: System Settings → Privacy & Security → Screen & System Audio Recording This behavior differs from macOS Sequoia, where these executables did appear in the list and could be managed through the UI. Tahoe still prompts for permission and still allows the executable to capture the screen once permission is granted, but the executable never shows up in the UI list. This breaks user expectations and removes UI-based permission management. To confirm the behavior, I created a small reproduction project with both: a plain executable, and an identical executable packaged inside an .app bundle. Only the bundled version appears in System Settings. Observed Behaviour 1. Plain Executable (from my reproduction project) When running a plain executable that captures the screen: macOS displays the normal screen-recording permission prompt. Before granting permiss
Topic: Privacy & Security SubTopic: General Tags:
3
0
962
3w
DeclaredAgeRange framework new cases and properties cause runtime crash with missing symbol
I'm making a wrapper library to abstract away some of the 'missing platform support' of DeclaredAgeRange until hopefully it expands to additional platforms. When I'm trying to fully enumerate all of the cases of AgeRangeDeclaration, which they all state available starting 26.0 (mysteriously added in Xcode 26.2 beta), the app crashes due to a missing symbol at launch time. This happens both for Xcode 26.1, 26.2 beta 2, and matching Xcode Cloud builds. So I've isolated it beyond doesn't work on my machine. I just made a handful of crashes and attached a sysdiagnose to a fresh feedback. FB21121092 - DeclaredAgeRange: Eligibility property and new declaration cases unavailable on iOS 26.1 device contradicting documentation - causes runtime symbol not found crash If anyone is curious what these crashes look like I've attached the DiagnosticPayload.jsonRepresentation() generated from one of my favorite frameworks, MetricKit. Very clearly articulated in the diagnostic metadata you can see the symbol not foun
Topic: App Store Distribution & Marketing SubTopic: General Tags:
5
0
896
4w
Reply to Cannot submit apps with Xcode 26.2 RC
Hi @DTS Engineer Albert, can you please help to resolve issue with submitting build made with 26.2 for review to release TestFlight build to external testers? I'm always getting This build is using a beta version of Xcode and can’t be submitted. I tried everything from cleaning DerivedData to fully reinstalling xCode and tools to 26.2. Nothing helps and I can't share my first app with volunteers to test.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
4w
Gitlab CI: Unable to find a device matching the provided destination specifier
Gitlab runner on M4 Mac Mini 2024, XCode 26.2, supported platforms: iOS, native UIKit swift project. Cocoapods. Trying to run tests via fastlane: run_tests(workspace: 'Project.xcworkspace', destination: platform=macOS,id=#{deviceId}, scheme: Release, clean: true) And having an error: $ xcodebuild -showBuildSettings -workspace Project.xcworkspace -scheme Release -destination platform=macOS,id=01234567-0123456789B9001C 2>&1 [12:23:53]: Could not read the SUPPORTED_PLATFORMS build setting, assuming that the project supports iOS only. [12:23:54]: Found simulator iPhone 16 Pro (18.5) The tests runs just fine in xcode on My Mac (Designed for iPad) device on the very same machine. Compared the output of xcodebuild -showdestinations in terminal: $ xcodebuild -showdestinations -workspace Project.xcworkspace -scheme Release Available destinations for the Release scheme: { platform:macOS, arch:arm64, variant:Designed for [iPad,iPhone], id:01234567-0123456789B9001C, name:My Mac } { platform:iOS, id:dvtdev
Topic: Developer Tools & Services SubTopic: Xcode
1
0
80
4w
Crash (KERN_INVALID_ADDRESS) on IOS 26.2 GM when calling isEligibleForAgeFeatures
We recently released an update to our app to prepare for TX SB2420. Almost immediately on release, we started getting crash reports of crashes when calling isEligibleForAgeFeatures. Crashed: com.apple.root.user-initiated-qos.cooperative EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x0000000000000004 Is it possible that these are beta users that have IOS 26.2 RC or is there a bug in the release version of IOS 26.2? Note: The crash reports are coming from Crashlytics so we are not getting OS build identifiers other than version 26.2
Topic: App & System Services SubTopic: General Tags:
2
0
190
4w
ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it
We are getting the above mentioned error while uploading to TestFlight. We have used a Swift Class to request for the Age Range via DeclaredAgeRange Framework. We have exposed Swift class and a helper function to be available in Objective-C layer. We have enabled the following build settings SWIFT_OBJC_INTERFACE_HEADER_NAME = Common-Swift.h; SWIFT_OBJC_BRIDGING_HEADER = Common-Bridging-Header.h ; ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES = YES Also we are compiling the application using latest available Xcode release 17C52 Is there anything else we need to do to resolve the error?
Topic: App Store Distribution & Marketing SubTopic: TestFlight Tags:
2
0
156
4w
Reply to Local Network permission on macOS 15 macOS 26: multicast behaves inconsistently and regularly drops
Thank you for your detailed answer. I reproduced your steps and see different outcomes. Let me answer your first two questions and then describe how I reproduced your steps and where I see differences. Answers The first divergence I see is at this step. I don’t have your accessory on my network so no local traffic is generated, so there’s no local network alert Indeed that checkbox makes the app itself send similar data than our hardware, using multicast. I don’t understand how that’s possible if this is a “clean install” of macOS. Where could it possible get a different usage string? I should have been clearer. It shows the string This will allow the app to discover, connect to and collect data from devices on your network. which we did not set ourselves. I could not figure out if it comes from an other app, or if it's the default usage description. Reproduction steps Here's a Dropbox link to our app (zipped): https://www.dropbox.com/scl/fi/btnpz64u8rz7y7t0dicbu/FM-Mac-App-Test-5.1.zip?rlkey=8g43pvph7qrld12h
Topic: App & System Services SubTopic: Networking Tags:
4w