Since macOS 26.1, creating bookmark data based on a NSOpenPanel URL, does not return the expected bookmark data when the selected source concerns a Windows NTFS fileshare. When the returned data is being resolved, the returned URL points to the local drive of the current Mac. Which is of course super confusing for the user. This issue did not occur in macOS 26.0 and older. In essence, the following code line with 'url' based on an URL from a NSOpenPanel after selecting the root of a Windows NTFS share, creates an incorrect bookmark in macOS 26.1: let bookmark = try url.bookmarkData(options: .withSecurityScope, includingResourceValuesForKeys: nil, relativeTo: nil) I have tested this on two different Macs with macOS 26.1 with two different Windows PC both hosting NTFS files shares via SMB. My questions: Have anyone else encountered this issue in macOS 26? Perhaps even with other fileshare types? Is there a workaround or some new project configuration needed in Xcode to get this working?
Search results for
İOS 26 beta battery %1
253,802 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Hello Apple Developer Community, I'm experiencing an issue with PDF link interaction in WKWebView that appears to be specific to iOS 26. Problem Description: I'm loading a PDF in WKWebView.The links may vary widely and are not necessarily DPF, so I need to load them using WKWebView. On iOS versions prior to 26, links within the PDF are clickable and work correctly. On iOS 26, the same links are not clickable (no response when tapped). Expected Behavior: PDF links should remain clickable and functional across all iOS versions. What I've Tried: Tested opening the PDF directly in Safari on iOS 26 - links still not clickable This suggests the issue might be related to changes in the system's PDF rendering engine Reproduction Steps: Load the PDF URL in WKWebView Navigate to page 12 Attempt to tap the link Environment: Test Devices: iPhone 15(26.0 ) / iPhone 16 Pro Max(18.0.1 ) Xcode: 16.2 Questions: Is this an intentional change in iOS
The way you sign your app does not, in general, affect how it does HTTPS server trust evaluation. It’s hard to say exactly what’s going on here because you neck deep in third-party tools and libraries, but my best guess is that this is a build issue. That is, your code tries to get access to this root certificate but fails, either because the code is doing that incorrectly or because it’s not in the right place. If you were using Apple APIs I’d be able to suggest more specific paths for debugging this. I can’t do that here because I’m not familiar with the libraries you’re using. That leaves me with a couple of suggestions: You could dump the contents of your built app’s bundle to see if the certificate is where you expect it to be. You could track down the code that uses this root certificate and see how it’s failing. Is it using the right path to access it? Is the file actually there? Or is it failing to load it? You might have more luck asking this via the support channel for your third-party tooling. Shar
Topic:
App & System Services
SubTopic:
Networking
Tags:
Is there no solution for this? I checked your other thread as well. Is there a way for me to remove the third party libraries from my SDK? I run the below commands to generate the SDK. xcodebuild archive -project Abc.xcodeproj -scheme AbcSDK -configuration Release -destination generic/platform=iOS Simulator -archivePath BuildArtifacts/iossim.xcarchive | tee build.log xcodebuild archive -project Abc.xcodeproj -scheme AbcSDK -configuration Release -destination generic/platform=iOS -archivePath BuildArtifacts/ios.xcarchive | tee build.log xcodebuild -create-xcframework -framework BuildArtifacts/iossim.xcarchive/Products/Library/Frameworks/AbcSDK.framework -framework BuildArtifacts/ios.xcarchive/Products/Library/Frameworks/AbcSDK.framework -output Frameworks/AbcSDK.xcframework As soon as I run, it gives me the list of resolved source packages that includes all the third party libraries. If I try removing the libraries, it gives error at all the import statements in my code. I even
Topic:
Developer Tools & Services
SubTopic:
General
Tags:
I’m not sure I understand the concern here: Are you asking about how to interact with this FIDO2 USB device? Or whether that code will work in an authorisation plug-in? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
Privacy & Security
SubTopic:
General
Tags:
This script from man hdiutil no longer works: devnode=$(hdiutil attach -nomount ram://102400) newfs_hfs “$devnode” mount -t hfs “$devnode” /path/to/ramdisk because $devnode contains spaces and tabs!! $ hdiutil attach -nomount ram://1 | xxd 00000000: 2f64 6576 2f64 6973 6b34 2020 2020 2020 /dev/disk4 00000010: 2020 2020 0920 2020 2020 2020 2020 2020 . 00000020: 2020 2020 2020 2020 2020 2020 2020 2020 00000030: 2020 2020 090a # remember to clean up afterwards $ hdiutil detach /dev/disk4 Please properly quote your variables in CI test scripts to catch such regression. It could pass because unquoted expansion of $devnode undergoes word splitting after the variable is substituted, removing the trailing whitespaces. FB20303191
Thanks for filing FB20303191. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
App & System Services
SubTopic:
Core OS
Tags:
This is eminently bugworthy. I’d appreciate one of you [1] filing a bug about it, and then posting the bug number here, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Well, at least one of you. Multiple bugs are fine (-:
Topic:
Privacy & Security
SubTopic:
General
Tags:
The other thread discussing this issue has a bit more traction, so I’m gonna reply over there. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
Privacy & Security
SubTopic:
General
Tags:
The issue seems to have been resolved in iOS 26.1 (tested on simulator) Thank you!
Topic:
UI Frameworks
SubTopic:
SwiftUI
In iOS 26, the Slider control no longer respects the step parameter. For example, import SwiftUI struct ContentView: View { @State private var sliderValue: CGFloat = 16 var body: some View { Slider( value: $sliderValue, in: 0...100, step: 5, onEditingChanged: { editing in print(sliderValue) } ) } } In iOS 18, this prints values like 5, 35, 60, 95, etc. In iOS 26.0 (release version), this prints floats that are not rounded to the nearest 5, and the slider does not snap to values ending in 5. Feedback report number: FB20320542
Topic:
UI Frameworks
SubTopic:
SwiftUI
I just tried to upload the app to App Store Connect, but the upload failed with this error: Unsupported Platform. The extension bundle myApp.app/PlugIns/myApp iOS QuickLook.appex is not supported for this platform. Please refer to the App Extension Programming Guide at http://developer.apple.com. (ID: 5df7bb8c-0216-4845-af78-c83d9a94de21) So I ended up creating a completely separate target for visionOS without the QuickLook extension.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
I have an iOS app with a QuickLook extension. I also added Apple Vision Pro in the target's General > Supported Destinations section. About one year ago, I was able to run the app on iPhone, iPad and Apple Vision Pro Simulators. Today I tried running it again on Apple Vision Pro with Xcode 26.0.1, but Xcode shows this error: Try again later. Appex bundle at ~/Library/Developer/CoreSimulator/Devices/F6B3CCA8-82FA-485F-A306-CF85FF589096/data/Library/Caches/com.apple.mobile.installd.staging/temp.PWLT59/extracted/problem.app/PlugIns/problemQuickLook.appex with id org.example.problem.problemQuickLook specifies a value (com.apple.quicklook.preview) for the NSExtensionPointIdentifier key in the NSExtension dictionary in its Info.plist that does not correspond to a known extension point. I tried again later a couple times, even after running Clean Build Folder Immediately, without any change. I can reproduce this with a fresh Xcode project to which I add a Quick Look Preview Extension and Apple V
The Files app in the iOS 18 beta simulator appears to be read-only. I am unable to: create folders copy files into it by dragging them from macOS safe files from safari I have been unsuccessful at finding a way to popular any file or folder in the Files app which is preventing me from testing some scenarios in my app where I import files using the files sheet. The earliest I tried was beta 3 and it still persists in beta 7. The iOS 17 simulator works fine in comparison. My mac is a 2019 macbook pro running Sonoma 14.5. To reproduce: New folder Launch Files app in iOS simulator Tap into On my phone From the top menu tap New Folder (nothing happens) Download a file Launch safari Find a file like a PDF to download Tap on the down arrow in the toolbar Files opens up with the filename in the textfield at the bottom The Save button is grayed out. Copy from macOS Open the Files app in iOS and browse to a local folder drag a file from the macbook onto the
On iOS 18.0+ simulators, tap any share link button from any app, select Save to Files, the Save button is disabled. In all previous simulator versions this works. This behavior even happens with default Apple apps like Photos. Simulator: Version 16.0 (1037) XCode: Version 16.1 beta (16B5001e) macOS: 14.6.1 (23G93)