Search results for

“file uri scheme”

81,708 results found

Post

Replies

Boosts

Views

Activity

Xcode 26.4 cannot run app-hosted unit tests on physical iOS 16 devices ("Logic Testing Unavailable")

Summary: After upgrading to Xcode 26.4, app-hosted XCTest execution on physical devices running iOS 16 fails at test-planning time with Logic Testing Unavailable. The same project and same device work under Xcode 26.2. The failure reproduces with a standalone minimal Xcode project, which suggests this is an Xcode regression rather than a project-configuration issue. Environment: Xcode: 26.4 (17E192) macOS: Tahoe 26.4 Failing device: iPhone 11 (iPhone12,1), iOS 16.0.3 Working comparisons: Xcode 26.2 + same iPhone 11 (iOS 16.0.3): works Xcode 26.4 + iPad Pro 11-inch (4th generation) on iOS 26.3: works Regression: Yes. Works on Xcode 26.2. Fails on Xcode 26.4. Same project, same signing setup, same physical iOS 16 device. Minimal reproduction: A minimal sample project with: one iOS app target one app-hosted unit-test target one UI-test target (for comparison; not required to reproduce) Steps for the unit-test repro on a physical device running iOS 16: Build for testing: xcodebuild -project TestProject.xcodeproj

Developer Tools & Services Xcode Xcode Testing

248

Reply to CoreML regression between macOS 26.0.1 and macOS 26.1 Beta causing scrambled tensor outputs

I've been working with CoreML extensively across macOS 26.x betas and can confirm this regression. After investigating with MPS shader profiling, it appears to be a stride alignment issue in the MLMultiArray backing store when the compute unit dispatches to GPU/ANE. Workarounds I've found: Force CPU-only as temporary fix: let config = MLModelConfiguration() config.computeUnits = .cpuOnly If you need GPU performance, pin to CPU+GPU (excludes ANE): config.computeUnits = .cpuAndGPU In my testing, the corruption is most severe on the ANE path. CPU+GPU gives ~70% of the full .all performance without the scrambled outputs. I'd encourage everyone affected to file duplicate Feedbacks referencing the stride/alignment hypothesis to help Apple prioritize.

Machine Learning & AI Core ML

Reply to iOS 18 new RecognizedTextRequest DEADLOCKS if more than 2 are run in parallel

I've been working with the new Swift Vision API's RecognizeTextRequest on iOS 18 and hit this exact deadlock. After profiling with Instruments, I found that the Vision framework internally uses a limited thread pool for its neural engine requests — on most devices this caps at 2 concurrent ANE inference sessions. The workaround I'm using is a semaphore-based concurrency limiter that queues requests: actor OCRPipeline { private let maxConcurrent = 2 private var running = 0 private var pending: [CheckedContinuation] = [] func recognizeText(in image: CGImage) async throws -> [String] { await acquireSlot() defer { Task { await releaseSlot() } } let request = RecognizeTextRequest() let handler = ImageRequestHandler(image) let observations = try await handler.perform(request) return observations.compactMap { $0.topCandidates(1).first?.string } } } This keeps throughput high while never exceeding the 2-concurrent-request limit. In my testing across iPhone 15 Pro and iPad Air M2, this processes ~40 images per seco

Machine Learning & AI General

Reply to Advanced App Clip Experiences stuck in "Received" — never transition to "Published"

Thanks Albert, we'll file the bug report. One more ask: we have a live event tonight with printed QR codes and we're seeing very inconsistent behavior across fresh devices. Some devices load the App Clip perfectly via the Safari Smart App Banner fallback, while others show App Clip not available. Same URL, same network, all fresh devices that have never had our app installed. Is there anything else we can try on our end to improve reliability tonight? Any headers, cache settings, or meta tag adjustments that might help the Safari fallback path work more consistently? Or is the inconsistency entirely on the ASC publishing side? We're running out of ideas and have fans arriving soon. I'm attaching the QR code and the result when it fails. Thanks!

App Store Distribution & Marketing App Store Connect

Reply to Advanced App Clip Experiences stuck in "Received" — never transition to "Published"

@fanarchy Thank you for the post. It appears that the file is syncing to the servers without any issues. This is excellent news, and I appreciate you providing additional information regarding the problem. Your discovery of removing the “/next-game” from the AASA file, which causes it to fall back to Safari, is brilliant. This effectively isolates the issue, but still we have the issue in the App Store App Clip publishing. Safari Smart App Banners do not rely on the App Store Connect Advanced Experience database. When Safari loads your page, it reads the tag and cross-references your AASA file locally. Because your AASA and meta tags are perfect, this works flawlessly. In any case I see the issue is in the configuration on the App Store and you should file a bug for them to take a look at the process with your App Clip. The issue here is the status of the App Clip should eventually become published. Once you open the bug report, please post the FB number here for my referen

App Store Distribution & Marketing App Store Connect

90919: Invalid entitlement error in ASC

I have an existing app in App Store Connect. I added the SharedWithYou functionality to the app code and tested it on several devices. Everything is working as expected. One of the first steps was to add the com.apple.developer.shared-with-you entitlement to the Entitlements.plist file. This required a round of updates for app identifiers and provisioning profiles. When I upload the production build for testing in TestFlight I receive the following error: 90919: Invalid entitlement. The “” bundle has the com.apple.developer.shared-with-you entitlement, but it doesn’t use the Shared with You framework. Please remove the entitlement and upload a new build. I'm using SWHighlight, SWHighlightCenter, and SWAttributionView in several places throughout my app... I filed an issue in the Feedback Assistant but so far, have not received any response.

Code Signing Entitlements Entitlements App Store Connect TestFlight Shared with You

352

Reply to Xcode 26.4 breaks compilation

Hitting the same issue. Filed FB22336025

Developer Tools & Services Xcode

xcodebuild fails if build tool plugins are installed

After having built the SwiftUI project numerous times from Xcode and allowing the plugins after the first build post install using xcodebuild -scheme build fails with: The following build commands failed: Validate plug-in “SwiftLintBuildToolPlugin” in package “swiftlintplugins” Validate plug-in “OpenAPIGenerator” in package “swift-openapi-generator” How are we supposed to grant the plugins permission to run in the CLI? Everything I'm getting from Gemini is for packages, not apps.

Developer Tools & Services Xcode Command Line Tools

Reply to Xcode 26.4 Editor Tab Bar is low density

I filed feedback FB22335783, Regression: reduced editor tab density in Xcode 26.

Developer Tools & Services Xcode

Reply to System-wide deadlock in removexattr from revisiond / APFS

Sorry, it was a TSI, not a bug report. I replied to the DTS email yesterday with the full spin dump. Ahh, I see it now. So, the first thing I actually did was search for /usr/lib/libEndpointSecurity.dylib (the library link path), which is a convenient way to find all ES clients. What you'll find is that there are two clients— yours and a (presumably unrelated) 3rd party client. That's a critical factor here because it means that there are now two independent entities with veto power over each other's activities, particularly activity that's coming from helper components (not just the direct ES client). That leads to here: There are only 2 other threads in the logs that appear relevant, both from our helper process and both down in APFS. One of them is also stuck inside decmpfs_read_compressed: That's the deadlock. More specifically, looking at your thread's stack when you enter decmpfs_read_compressed, the first thing it does is call decmpfs_lock_compressed_data: (1) *940 decmpfs_read_compressed + 300 (kernel

App & System Services Core OS

Reply to Advanced App Clip Experiences stuck in "Received" — never transition to "Published"

Thanks for the post, interesting that's something in the process. TN3168: Making your App Clip available in the App Store | Apple Developer Documentation https://developer.apple.com/forums/thread/804858 There is something I always like to check when deploying AASA files. When the full app is installed, iOS handles the URL invocation locally via your apple-app-site-association (AASA) file and entitlements, bypassing the need to query Apple's App Clip CDN. The fact that this works proves your code, AASA file, and associated domains are configured correctly. The failure for fresh devices is happening because Apple's CDN has not yet been updated with your App Clip's metadata? Can you provide me a link to your AASA file in your server so we can see why is not syncing into the Apple servers? Is your server preventing or blocking IP address or user agents from requesting the AASA file? Sometimes, the job queue in App Store Connect simply drops the task. You can often forc

App Store Distribution & Marketing App Store Connect

Reply to Immersive API

Hey @THeberlein, This is an issue we're aware of in r.172784612. Until this is fixed, you can find the Website environment Feature Flag in the Webkit Feature Flags section. The Immersive API feature flag is non functional, there is no documentation for this. Even though we're aware of this issue, we still encourage you to open a bug report, and post the FB number here once you do. Filing the bug report allows you to get notified when it is resolved. Bug Reporting: How and Why? explains how you can open a bug report. Thanks, Michael

Spatial Computing General

Reply to Xcode 26.4 breaks compilation

Since this is a change in behavior between Xcode versions, you absolutely should file this as a bug report. The expression on the line that you cited is really quite something! Make sure to post the FB number here for our reference. Since this is a library you depend on, you should talk to the maintainers to look at breaking that up into smaller statements so that you're able to compile it with Xcode 26.4. If you're using Swift Package Manager to import a library, there is a way you can make local modifications to a package you depend on, which might also be helpful to you here. — Ed Ford,  DTS Engineer

Developer Tools & Services Xcode

Reply to Xcode 26.4 and 26.3: Swift compiler crashes during archive with iOS 17 deployment target

Thank you for filing FB22331090 with the info required to easily reproduce, that's very helpful! — Ed Ford,  DTS Engineer

Developer Tools & Services Xcode

Reply to Upgrading Python that ships with Xcode from 3.9.6

You have the right information: You cannot update the version of Python included with Xcode yourself. If you have a concern to report with the version Xcode is including for its needs, you can file an Xcode bug report through Feedback Assistant. For recent macOS versions, Python is not included with macOS, so any installation you may find in locations like /usr and /opt were installed through other means. — Ed Ford,  DTS Engineer

Developer Tools & Services Xcode