Search results for

file uri scheme

79,854 results found

Post

Replies

Boosts

Views

Activity

Xcode can't view code generated by Swift Package Plugins
When using a Swift Build Plugin, the generated code definitions are available through autocomplete, but it is currently not possible to view them directly in Xcode using Option+click. An example of such a plugin is swift-openapi-generator. According to information from Meet Swift Package plugins from WWDC22 the generated code is stored with other build artifacts. It would be immensely helpful if there was support for viewing these intermediate files in read-only mode using Option+click. Currently, I have to resort to opening these files through Finder, or opening the project in VS Code where viewing the generated files using Cmd+click works without a problem. Am I missing something? If not, it seems like a big oversight that this is not supported to the same extent in Apple's own tools.
1
0
57
4w
How to disable Finder "Move to Bin" action for non materialised files
In the context of a NSFileProviderReplicatedExtension I would like to only see the Move to Bin Finder action when files have been materlialised ( isDownloaded fileprovider attribute ) I thought it might be possible to get the isDownloaded attribute in my NSFileProviderItemProtocol class capabilities method but that doesn't seem to be the case. Possible ?
2
0
658
Nov ’25
Reply to iOS fails to fetch AASA file for IDNs
The redirect is used to work around the problem described above. Actually, the presence of the file at /.well-known/apple-app-site-association is irrelevant. The core issue described in the previous message is that the system does not even attempt to fetch the AASA from Apple's server, even though it exists here: https://app-site-association.cdn-apple.com/a/v1/xn--montral-fya.ca. But this is also irrelevant because the system blocks AASA requests for domains in Punycode. What I want to say is that the expected behavior is this: I specify Associated Domains. When the app is installed, a request for the AASA is made to Apple's CDN. This request might result in an error or return a valid file. For us, this is unimportant because the request is not being made at all. Another small clarification: when I specify non-existent domains like xnmontral-fya.ca, I can see via proxying that the system does try to fetch the AASA. However, if I specify any string containing the xn-- prefix (denoting a Punyc
Topic: App & System Services SubTopic: General Tags:
Nov ’25
iOS Speech Error on Mobile Simulator (Error fetching voices)
I'm writing a simple app for iOS and I'd like to be able to do some text to speech in it. I have a basic audio manager class with a speak function: import Foundation import AVFoundation class AudioManager { static let shared = AudioManager() var audioPlayer: AVAudioPlayer? var isPlaying: Bool { return audioPlayer?.isPlaying ?? false } var playbackPosition: TimeInterval = 0 func playSound(named name: String) { guard let url = Bundle.main.url(forResource: name, withExtension: mp3) else { print(Sound file not found) return } do { if audioPlayer == nil || !isPlaying { audioPlayer = try AVAudioPlayer(contentsOf: url) audioPlayer?.currentTime = playbackPosition audioPlayer?.prepareToPlay() audioPlayer?.play() } else { print(Sound is already playing) } } catch { print(Error playing sound: (error.localizedDescription)) } } func stopSound() { if let player = audioPlayer { playbackPosition = player.currentTime player.stop() } } func speak(text: String) { let synthesizer = AVSpeechSynthesizer() let utterance =
1
0
245
Nov ’25
SwiftUI Slider onEditingChanged is unreliable on iOS 26
For information I stumbled upon a regression with SwiftUI Slider on iOS 26. Its onEditingChanged closure might be called twice when interaction ends, with a final Boolean incorrect value of true provided to the closure. As a result apps cannot reliably rely on this closure to detect when an interaction with the slider starts or ends. I filed a feedback under FB20283439 (iOS 26.0 regression: Slider onEditingChanged closure is unreliable).
7
0
441
Nov ’25
Reply to Unexpected system confirmation dialog when opening a Universal Link
We did follow the debugging guide. The issue here is to understand why it works correctly the first time, meaning that the Apple-app-site-association files and associated domains are configured correctly, and not the second time while remaining on the same tab. We need help understanding what the security difference is between the first invocation and second knowing that it is the exact same website executed and javascript code executed on both attempts.
Topic: Safari & Web SubTopic: General Tags:
Nov ’25
Reply to Wakes (CalendarDate), although related UI settings are off
UPDATE: I finally found the solution. Looks like there is a so-called CoreSmartPowerNap feature that keeps waking the system up for Maintenance despite the user having turned off Power nap in Setting. Disabling this feature stoped the hourly dark wakes. The problem is, there is no user setting to disable it (for whatever weird reason), so it needs to be disabled using a user preference file that overrides the system preferences. Find the file powerd.plist under /System/Library/FeatureFlags/Domain and copy its contents Create a powerd.plist under /Library/Preferences/FeatureFlags/Domain with the contents above, but change the Enabled key for CoreSmartPowerNap to false Voilá... no more hourly dark wakes and your Mac will sleep like a baby until you wake it up manually :)
Topic: App & System Services SubTopic: Core OS Tags:
Nov ’25
Reply to Find IDR in AVAsset
I'm assuming you want the IDR info in decode order rather than presentation order. This makes a difference if your movie contains bidirectionally predicted frames. If your H.264 video file is a QuickTime movie, you can do something like this: func getSyncInfo(url: URL) -> [Bool] { var idrInfo = [Bool]() let asset = AVURLAsset(url: url) guard let reader = try? AVAssetReader(asset: asset) else { return idrInfo } let videoTrack = asset.tracks(withMediaType: AVMediaType.video).first! guard let cursor = videoTrack.makeSampleCursorAtFirstSampleInDecodeOrder() else { return idrInfo } repeat { let syncInfo = cursor.currentSampleSyncInfo idrInfo.append(syncInfo.sampleIsFullSync.boolValue ? true : false) } while cursor.stepInDecodeOrder(byCount: 1) == 1 return idrInfo } This is unlikely, but if the CMSampleBuffer contains an access unit of a raw Annex B bitstream, then you have to: Get the raw data bytes from the CMBlockBuffers Remove encapsulation prevention bytes Search for start codes the look like 0x00
Topic: Media Technologies SubTopic: Audio Tags:
Nov ’25
Static library produced by Xcode 26 causes link error on Xcode 16
When a static library is built with Xcode 26 (with deployment target set to iOS 13) and then linked into an app project compiled with Xcode 16, the build process fails with the following linker error: Undefined symbols for architecture arm64: _swift_coroFrameAlloc This occurs even though both the static library and the app project have their deployment targets set to iOS 13.0. The static library works on Xcode 26, but fails to link on Xcode 16. This issue shows up with certain Swift syntax. For example, in my case, using a property getter and setter caused the compiler to emit a reference to _swift_coroFrameAlloc, which in turn triggered the issue. This issue prevents us from distributing pre-built static libraries compiled with Xcode 26 to teammates who are still using Xcode 16. I’ve filed feedback for this issue (FB21130604). Is there any way to work around it? For example, by adding specific Build Settings or something similar? A demo project is available here: https://github.com/Naituw/SwiftLibra
2
0
267
Nov ’25
Reply to Persistent font registration crashes when fonts are delivered via Apple-Hosted Background Assets
[quote='867195022, Sandya, /thread/808036?answerId=867195022#867195022, /profile/Sandya'] This does prevent the crash. [/quote] Cool. [quote='867195022, Sandya, /thread/808036?answerId=867195022#867195022, /profile/Sandya'] the fonts still do not install system-wide [/quote] Bummer. [quote='867195022, Sandya, /thread/808036?answerId=867195022#867195022, /profile/Sandya'] Is .persistent font registration intended to work with fonts delivered through Apple-Hosted Background Assets? [/quote] I don’t know, but I’m not sure that matters. You want this to work, and that’s a pretty reasonable request. So either this as a bug or an enhancement request, and the path forward is the same in both cases: File a report in Feedback Assistant. However, looking at FB21109320 it seems like we’ve decided to use it to drive that investigation, rather than use it to track the CT annotation issue. So I don’t think there’s anything else for you to do here, other than to keep on eye on FB21109320 in Feedback Assistant. Shar
Nov ’25