Search results for

“file uri scheme”

81,724 results found

Post

Replies

Boosts

Views

Activity

Reply to Simulator was shutdown during an update

Hi, Sorry to hear you are having problems getting previews working. This kind of issue can often indicate a crash in a problem with the simulator infrastructure itself. If you look into the folder ~/Library/Logs/DiagnosticReports, do you see any crash reports for anything that corresponds with the timeframe where you reproduced the problem? If nothing stands out to you, the best next step will be to file a feedback with diagnostics so we can take a look. Install the logging profile using instructions available here: https://developer.apple.com/bug-reporting/profiles-and-logs/?name=swift On your mac running Xcode, and on your physical preview device (if you are using one). Install the logging profile using the following instructions on your mac running Xcode; and if you are using one, your physical preview device (iOS or visionOS): https://developer.apple.com/bug-reporting/profiles-and-logs/?name=swift Then when you reproduce the problem in Xcode: Either (a) an error banner will appear, click the Diag

Developer Tools & Services Xcode

Reference to [symbol] is ambiguous, but it's the same symbol...

I've got a Project with a bunch of frameworks, each of which has a static library version of itself (for compiling command-line tools that also use the code). Compiling the frameworks goes fine. Compiling one of the static libraries (A Mime-parsing framework) is giving me the rather odd message that a bunch of symbols are ambiguous, but the ambiguity resolves to the same symbol in the error-message... ~/src/E3Mail/Frameworks/E3Mime/E3Mime/Message/MIME/E3AppPkcs7Part.m:57:18: error: reference to 'E3_SMIME_ENVELOPED_DATA' is ambiguous 57 | case E3_SMIME_ENVELOPED_DATA: | ^ In file included from ~/src/E3Mail/Frameworks/E3Mime/E3Mime/Message/MIME/E3AppPkcs7Part.m:9: ~/src/E3Mail/Frameworks/E3Mime/E3Mime/Message/MIME/E3AppPkcs7Part.h:17:2: note: candidate found by name lookup is 'E3_SMIME_ENVELOPED_DATA' 17 | E3_SMIME_ENVELOPED_DATA, // Enveloped data | ^ In module 'E3Mime' imported from ~/src/E3Mail/Frameworks/E3Mime/E3Mime/Message/MIME/E3AppPkcs7Part.h:8: ~/src/E3Mail/Frameworks/E3Mime/E3Mime/Message/MI

Developer Tools & Services Xcode Xcode Static Analyzer

Reply to Icon composer icon contains alpha channel upload error

Following the documentation here also did not work for me. https://developer.apple.com/documentation/xcode/creating-your-app-icon-using-icon-composer#Add-your-Icon-Composer-file-to-an-Xcode-project What worked for me was the following: In Icon Composer, select File -> Export... For Appearance, select All, then click Export... Select a location and click Export to save Navigate to the location you saved, there should be 6 .png files. Select the three you will use for AppIcon from assets for Any Appearance, Dark, and Tinted options. Open those in Preview In Preview for each image, select File -> Export... Be sure to uncheck the Alpha setting and save the file. Use the newly exported images for your three AppIcon settings in Assets.

Developer Tools & Services Instruments

Reply to spctl --type install rejects notarized .pkg on macOS 26 Tahoe (26.3)

Thank you Quinn! Here's the direct download link to the installer package: https://github.com/Nakanokappei/window-resize/releases/download/v2.0/Window.Resize.pkg This is a Developer ID Installer–signed and notarized .pkg built with productbuild --sign. The .zip distribution of the same app passes Gatekeeper without issue. For reference, here's what I see: # Signature is valid pkgutil --check-signature Window Resize.pkg # → signed by Developer ID Installer certificate # Notarization succeeded xcrun stapler validate Window Resize.pkg # → The validate action worked! # But spctl rejects it spctl -a --type install Window Resize.pkg # → rejected # syspolicyd log shows # meetsDeveloperIDLegacyAllowedPolicy = 0 The productbuild --sign does emit Warning: unable to build chain to self-signed root but security verify-cert confirms the cert chain is valid. Happy to file a bug with the .pkg attached if that's easier for you.

Code Signing Notarization

Reply to FSKit passthrough sample fails to mount

I already unmounted it, but lsof would surely report unclosed file descriptors. Shouldn't unmount attempt to close it automatically, especially if it was created by the Finder/Preview and cached somewhere ?

App & System Services Core OS

Reply to Unlock with Touch ID suggested despite system.login.screensaver being configured with authenticate-session-owner rule

Thanks Quinn, I have filed a bug report: FB22289735.

Privacy & Security General

Reply to Unlock with Touch ID suggested despite system.login.screensaver being configured with authenticate-session-owner rule

[quote='819454021, oleksandr91, /thread/819454, /profile/oleksandr91'] Is this a known macOS bug? [/quote] I’m pretty sure I’ve seen this before. IIRC the problem was reported by a third-party developer and I found it super hard to reproduce, and thus I’m not sure if a bug got filed. Sorry to be vague about the details; I searched my records but was unable to track down the conversation. Anyway, it sounds like you can easily reproduce this. Given that, I think it make sense for you to file your own bug about it. Please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Privacy & Security General

Reply to Different transaction IDs for the same purchase between SKPaymentTransaction and receipt latest_receipt_info

Please submit a feedback assistant ticket (http://feedbackassistant.apple.com), and we can assist further. Please provide as much information as possible, ie a sysdiagnose, app apple ID, in-app apple IDs, sandbox account apple ID (if applicable), transactions IDs, steps to reproduce and other relevant details. File ticket under iOS & iPadOS, macOS, tvOS, watchOS, or visionOS and ensure you select “App Store” for the question “Which area are you seeing an issue with?” Categorize the type of feedback Please attach all available files needed to verify After submitting the feedback, please regularly check the ticket as we'll only communicate through it from then on. Once you open the Feedback Assistant Ticket report, please post the FB number here for reference. If you have any questions about filing a report, take a look at Bug Reporting: How and Why?

App & System Services StoreKit

Reply to Unusually Long "Waiting for Review" Times This Week - Anyone Else?

@App Review The issue is NOT resolved for all developers. I have two apps stuck in Waiting for Review with zero communication: OKIRIZO (Apple ID: 6757417197) - First submitted Jan 10, 2026. Current submission Feb 25. Over 2 months waiting. TidaKitchen (Apple ID: 6759185372) - Submitted ~Mar 11. Still waiting. I have filed THREE support cases with no response: Case 102824913561 (Feb 19) - no reply Follow-up (Mar 4) - no reply Case 102846444484 (Mar 17) - no reply Expedited review request also submitted with no response. Three support cases over one month, all ignored. This is unacceptable for paying Apple Developer Program members. Please investigate immediately.

App Store Distribution & Marketing App Review

Reply to App review process takes long time

I am experiencing the same issue with two of my apps. OKIRIZO (Apple ID: 6757417197) - First submitted January 10, 2026. Current submission from February 25, now waiting 23+ days. I have contacted Apple Developer Support on February 19 (case 102824913561), followed up on March 4, and again on March 17 (case 102846444484). No response to any of these inquiries. I have also submitted an expedited review request with no response. TidaKitchen (Apple ID: 6759185372) - Submitted approximately March 11, also stuck in Waiting for Review. Both are v1.0 initial submissions. No messages, no rejections, no feedback in App Store Connect. Three support cases filed over the past month with zero replies. This is severely impacting our business operations in Okinawa, Japan. Could the App Review team please investigate?

App Store Distribution & Marketing App Review

Reply to CallKit lock screen UI on iOS 26: “slide to answer” text is too faint / hard to read

I've noticed the same contrast issue on iOS 26 with dark wallpapers. This appears to be a Liquid Glass regression — the frosted material doesn't adapt well to certain background luminance levels. Since the slide to answer text is entirely system-managed through CallKit, there's no app-side workaround. I'd recommend filing a Feedback (if you haven't already) under UIKit > System UI with a screenshot showing the low contrast scenario. Referencing the WCAG 2.1 AA contrast ratio requirement (4.5:1 for normal text) in your report might help prioritize it, since this is a core accessibility concern for incoming calls.

Design General

Reply to File Export from iOS - eventually import too

When I rename a file I can't seem to change the extension. For example: when I select the file and change to MyFile.csv - it writes MyFile.csv.txt is there any way to get rid of that .txt extension other than make the user delete it? I mean they could edit from .txt to .csv and macOS asks if they are sure - but I'd like to remove that step. That might be worthy of a feedback...

UI Frameworks SwiftUI

Reply to copyfile Sometimes Fails to copy .DS_Store when Copying a Folder But Does Not Report Usable Error

Mystery (partially) solved. I just took a sneak peak at the extended attributes of the .DS_Store file and some have a resource fork (probably the ones that were failing to copy I BET!). So appears to be the same failure we are talking about here: https://developer.apple.com/forums/thread/814076 Can you upload a copy of the .DS_Store file to the bug you filed on this? Also, what's the bug number? Also, are you sure the Finder actually copied the file (it may very well be skipping these files). .DS_Stores on the NAS's with resource forks.. maybe that will help you figure out leaky compression Does the file have a data fork? My I suspect these files are actually just old/weird, but the presence of a data fork means it's unlikely the file was ever compressed. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

App & System Services Core OS

Reply to File Export from iOS - eventually import too

In some online tutorials there was a way to set the full filename (like Export.csv) In the case of sharing a file, you can give the file a name you choose. Here you are sharing a piece of data, and so the use casen is different. Could you clarify how DTS works now relative to these questions answered here on the forum? Since I did ask for a DTS - does this count as one? Apple's DTS has been providing our usual code level support in the forums as well as via email. We've also lifted the cap of 2 incidents per account per year so developers can ask questions as needed. As a result, other than the medium of communication, there’s really no difference in the support response we’ll provide. Best, —— Ziqiao Chen  Worldwide Developer Relations.

UI Frameworks SwiftUI

Metadata in Video stripped by Share Sheet / Airdrop

I have an application which records video along with some custom metadata and a chapter track. The resultant video is stored in the Camera Roll. When sharing the video via the Share Sheet or AirDrop, the metadata track is stripped entirely (the chapter markers are preserved) Sharing via AirDrop with the All Photos Data option does include the metadata track, as does copying from the device with Image Capture but this is a bad user experience as the user must remember to explicitly select this option, and the filename is lost when sending this way. I have also tried various other approaches (such as encoding my metadata in a subtitle track, which I didn't expect to be stripped as it's an accessibility concern) but it's also removed. Essentially I am looking for a definitive list of things that are not stripped or if there's a way to encode a track in some way to indicate it should be preserved. The metadata is added via AVTimedMetadataGroup containing one AVMutableMetadataItem which has its value as a JSON str