Search results for

file uri scheme

79,830 results found

Post

Replies

Boosts

Views

Activity

Reply to NSScreen's maximumExtendedDynamicRangeColorComponentValue does not seem to provide the proper value after sleep/wake on third party HDR displays even when there is EDR content on screen in macOS Tahoe
Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports. Bug Reporting: How and Why? has tips on creating your bug report.
Topic: Graphics & Games SubTopic: Metal Tags:
1w
Reply to 关于 WKWebView 加载本地文件时 localStorage 数据丢失的情况
I am tracking some other issues related to localStorage. Please consider filing a bug report. Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports. Bug Reporting: How and Why? has tips on creating your bug report.
Topic: Safari & Web SubTopic: General Tags:
1w
关于 WKWebView 加载本地文件时 localStorage 数据丢失的情况
在 iOS 平台使用 WKWebView 通过file://协议加载本地 HTML 文件时，存储在localStorage中的数据会在 App 后台切换、进程重启后偶尔丢失；但相同代码在安卓 / 鸿蒙平台无此问题。 现在的文档 仅明确了「默认数据存储（defaultDataStore）可将网站数据持久化到磁盘，非持久化存储（nonPersistent）仅存内存」的基础规则； 未提及「file://协议内容即使使用默认持久化存储，也会被归为临时内存存储」这一关键场景限制； 仅在WKURLSchemeHandler关联说明中隐含「自定义 URL 协议可处理 WebKit 原生不支持的 URL 方案」，但未直接关联file://的存储问题。 我找不到如何处理这个问题的官方文档，仅仅有其他的博客说需要增加http/https加载就没有这个问题。 请提供给我官方文档或者官方回复 关于出现这种file:/加载html出现问题的处理办法
Topic: Safari & Web SubTopic: General Tags:
2
0
207
1w
Scanning Macintosh HD produces single .nofollow file since update to macOS 26.1
A user of one of my apps reported that since the update to macOS 26.1 they are no longer able to scan Macintosh HD: the app used to work, but now always reports that Macintosh HD contains a single empty file named .nofollow, or rather the path is resolved to /.nofollow. Initially I thought this could be related to resolving the file from the saved bookmark data, but even restarting the app and selecting Macintosh HD in an open panel (without resolving the bookmark data) produces the same result. The user tried another app of mine with the same issue, but said that they were able to scan Macintosh HD in other App Store apps. I never heard of this issue before and my apps have been on the App Store for many years, but it looks like I might be doing something wrong, or the APIs that I use are somehow broken. In all my apps I currently use getattrlistbulk because I need attributes that are not available as URLResourceKey in all supported operating system versions. What could be the issue? I'm on
Topic: App & System Services SubTopic: Core OS Tags:
6
0
167
1w
Reply to For receiving audio in PushtoTalk, channelManager(_:didActivate:) not called when app receives first push after backgrounding
No, I am not activating or changing anything in AudioSession. I have pretty straightforward setup; recording an audio using AVAudioEngine and sending to the server (which is running locally for now). And when PTT notification arrives saving url to audio file in incomingPushResult, then downloading and playing that sound using AVAudioPlayer when didActivate is executed. It's working fine on foreground, but when app goes to background incomingPushResult is called as expected but didActivate is not for some reason. Am I missing anything in my setup?
Topic: App & System Services SubTopic: General Tags:
1w
Reply to RealityKit / visionOS – Memory not released after dismissing ImmersiveSpace with USDZ models
Filed ticket number FB21327973 with sample test app demonstrating memory pressure with UnlitMaterial usage. Also seeing an Error on some images, although they are still being rendered on the device: IOSurface creation failed: e00002c2 parentID: 00000000 properties: { IOSurfaceAddress = 4380393472; IOSurfaceAllocSize = 20027995; IOSurfaceCacheMode = 0; IOSurfaceMapCacheAttribute = 1; IOSurfaceName = CMPhoto; IOSurfacePixelFormat = 1246774599; } IOSurface creation failed: e00002c2 parentID: 00000000 property: IOSurfaceCacheMode
Topic: Spatial Computing SubTopic: General Tags:
1w
[iOS 26 Beta] BGTaskScheduler.supportedResources incorrectly reports no GPU support for BGContinuedProcessingTask on capable hardware
Testing Environment: iOS: 26.0 Beta 7 Xcode: Beta 6 Description: We are implementing the new BGContinuedProcessingTask API introduced in iOS 26. We have followed the official documentation and WWDC session guidance to configure our project. The Background Modes (processing) and Background GPU Access capabilities have been added in Xcode. The com.apple.developer.background-tasks.continued-processing.gpu entitlement is present and set to in the .entitlements file. The provisioning profile details viewed within Xcode explicitly show that the Background GPU Access capability and the corresponding entitlement are included. Despite this correct configuration, when running the app on supported hardware (iPhone 16 Pro), a call to BGTaskScheduler.supportedResources.contains(.gpu) consistently returns false. This prevents us from setting request.requiredResources = .gpu. As a result, when the BGContinuedProcessingTask starts without the GPU resource flag, our internal Metal-based exporter attempts to access th
Topic: App & System Services SubTopic: Processes & Concurrency Tags:
6
0
318
1w
Reply to [iOS 26 Beta] BGTaskScheduler.supportedResources incorrectly reports no GPU support for BGContinuedProcessingTask on capable hardware
I'd like to +1 the need for an official compatibility list. If you haven't already, you're welcome to file a bug on this and please send me the bug number if you do. However, I'm not sure that's something that’s likely to happen, as the main reason we use runtime checks like BGContinuedProcessingTaskRequest.Resources.gpu is that it gives the engineer team the flexibility to change what devices are supported (generally by expanding) without needing to worry about keeping the documentation in sync, particularly if the supported device set varies with OS version. Most of our APIs use this approach and don't explicitly describe what hardware they support. Case in point, the form here: (something like this, for example). ...is a specific exception because UIRequiredDeviceCapabilities is used for an install-time check of the entire app, not just a specific app feature. It's also tied to functionality that was inconsistently implemented across our product lines and system versions, which makes it much more
Topic: App & System Services SubTopic: Processes & Concurrency Tags:
1w
Reply to We attempted to run a burn-in test while connected to our MacBook Pro M4 Max, but this crashed about 10 minutes into testing.
We attempted to run a burn-in test while connected to our MacBook Pro M4 Max, but this crashed about 10 minutes into testing. We tried to run a 2-hour burn-in on the M4 Max host while charging the battery from below 5%, running six bus-powered drives (via ATTO/Black Magic/IOmeter), hitting the RJ45 port for 2.5Gbps (via JPerf), and streaming at least 4K60Hz video content to two displays; however, the M4 Max crashed in 20minutes. If you haven't already, please file a bug on this and post the bug number back here. In the bug, please attach full panic logs as well as a sysdiagnose from the machine that panic-ed. One comment on the log picture you posted. That particular panic message (Halt/Restart Timed Out) comes from a very specific point, which you can actually see here: xnu/iokit/Kernel/IOPlatformExpert.cpp: ... IOShutdownNotificationsTimedOut( thread_call_param_t p0, thread_call_param_t p1) { #if !defined(__x86_64__) /* 30 seconds has elapsed - panic */ panic(Halt/Restart Timed Out); ... Critically
Topic: App & System Services SubTopic: Core OS
1w
Reply to Cannot submit apps with Xcode 26.2 RC
Even with the new Xcode (not release candidate), I get error when uploading from Xcode: Validation Failed: This bundle is invalid. Apple is not currently accepting applications built with this version of Xcode. This is with Xcode 26.2 which has Released December 12, 2025 and Build 17C52. Also, the file name is Xcode_26.2_Apple_silicon.xip.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
1w
Reply to SaaS app rejected by Guideline 5.1.1
Thank you for your post. If you disagree with the outcome of the review, we recommend submitting an appeal to the App Review Board. When filing your appeal, make sure to: Provide specific reasons why you believe your app complies with the App Review Guidelines. Submit only one appeal per rejection. Respond to any requests for additional information before submitting an appeal. Once you have submitted the appeal we can escalate it to the App Review Board for review. The App Review Board will contact you directly as soon as they've completed their investigation.
Topic: App Store Distribution & Marketing SubTopic: App Review Tags:
1w
Reply to Zsh kills Python process with plenty of available VM
Is there a guide for macOS on the steps you describe at the end, that is on how to allocate a swapfile, Just to be clear, you're not actually creating a swapfile as such. Your mapping a file into memory which means, assuming the mapping MAP_SHARED, the VM system will then use that file as the backing store for that memory range. That gives you basically the same behavior as swap backed system memory, but it isn't ACTUALLY the same as using true swap (for example, you'll be writing the data directly back to file, so there won't be any compression or VM level encryption). mmap that swapfile into memory, mmap is a standard Unix API, which means we don't really provide specific documentation for it, however, there is an old code snippet here showing how it works. One note I will note is that some of the recommendations there aren't really relevant anymore, particularly any recommendation about limiting mapping size. Those concerns where driven by the limited 32-bit address space, but th
Topic: App & System Services SubTopic: Core OS
1w