Search results for

DTiPhoneSimulatorErrorDomain Code 2

158,492 results found

Post

Replies

Boosts

Views

Activity

Reply to Inability to Communicate via APDU on iOS Despite NFC Tag Detection
No I am using TagReaderSession only but its failing silently Did detect is not getting called for the tag mentioned above in screenshot this is how i am intiating the NFC Session is this correct way or anything is Missed public class NfcServiceIos : INfcServiceIos { private SessionDelegate _currentDelegate; private bool _sessionActive = false; private NFCTagReaderSession _currentSession; public async Task SendAsync(byte[] bytes) { var isNfcAvailable = UIDevice.CurrentDevice.CheckSystemVersion(11, 0); if (isNfcAvailable && NFCTagReaderSession.ReadingAvailable) { if (_sessionActive) { await Application.Current.MainPage.DisplayAlert(Error, NFC session is still active. Please wait., Ok); return; } _sessionActive = true; _currentDelegate = new SessionDelegate(bytes, OnSessionInvalidated); // All CoreNFC session code must be on the main thread! await Microsoft.Maui.ApplicationModel.MainThread.InvokeOnMainThreadAsync(() => { // create NFCTagReaderSession instead of NFCNdefReaderSession _currentSe
Topic: App & System Services SubTopic: Core OS Tags:
3d
Issue Retrieving Bound Cards in Wallet Extension Non-UI Extension
Hi, I’m encountering an issue in my app’s Wallet Extension, specifically within the Non-UI Extension, where we are unable to retrieve payment passes bound to a user’s account. The same code that successfully retrieves these bound cards in the main app does not work when used in the Non-UI Extension. Case-ID: 8932090 Steps to Reproduce: Set up In-App Provisioning: Ensure that the app has the necessary In-App Provisioning permissions. This functionality works correctly in the main app, confirming that the permissions are properly configured. Configure Wallet Extensions: Follow the Wallet Extensions documentation to configure the app, including all required settings for the Non-UI Extension. Add Code to Retrieve Payment Passes: In the main app’s LoginView, implement the following code in the handleLogin() method to retrieve payment passes: // Get the identifiers of payment passes that already exist in Apple Pay. paymentPassLibrary = self.passLibrary.passes(of: .secureElement) for pass
5
0
1.1k
3d
Unexpected system confirmation dialog when opening a Universal Link
Subject: Unexpected system confirmation dialog when opening a Universal Link Description of the issue: We’re implementing a login flow using Native iOS apps, Universal Links, and OpenID Connect authentication. Our domain is correctly configured with the apple-app-site-association file, and Universal Links work as expected. However, under certain circumstances, the behavior differs on the same login page: The user connects to the OIDC provider in their mobile browser. Instead of automatically switching to the Native application, a popup asks the user to open the app. The behavior depends on how the login page is opened: When opened in a new browser tab, the Universal Link opens the app immediately without showing any system confirmation dialog. When the same tab is reused without a page refresh, iOS displays a system confirmation dialog asking the user to open the link in the app. This confirmation dialog doesn’t appear in the first scenario. This additional system dialog impacts the user experience, as we aim
5
0
1.4k
3d
Reply to Unexpected system confirmation dialog when opening a Universal Link
@DTS Engineer Thank for your answer. In summary, our issue is not straightforward. On the application site, everything functions correctly. The problem lies on the client (browser) side. I am uncertain whether a race condition or a similar condition may be the cause of this issue. All of our JavaScript code executed for this purpose is synchronous, resulting in no concurrency. The problem occurs precisely at the moment when this code executes: “window.location.assign” Therefore, there is nothing complex about it. We are simply redirecting the current page to the Universal Link. This operation works fine in most conditions but doesn't when the same Safari tab is being used. We do not see any errors in the Browser javascript console. Our flow will not function without JavaScript, as it is the only option to automatically redirect to the Universal Link without user interaction. Perhaps the issue is not with the Universal Link itself, but rather with the browser, which is unable to properly hand
Topic: Safari & Web SubTopic: General Tags:
3d
Guideline 5.2.5 - Legal - Intellectual Property
Your app still contains features that mimic the iOS interface or behavior. I have a simple app that uses a NavigationSplitView 3 panels I have a section for Filters and User created Categories in Panel 1 A list of Requests from the selected Filters/Categories in Panel 2 and details of a request in Panel 3 It's designed to be simple and easy to use. How can it NOT mimic the iOS interface if I am using their own APIs? What should I do to get around this
Topic: Design SubTopic: General
3
0
1.5k
3d
Reply to Tahoe 26.2 breaks printing with PaperCut
Hi Kevin, Thank you for the clarification. However, we want to emphasize that the decision to have cupsd ignore one of its main configuration files is a major breaking change. This is not just a tightening of the sandbox but a major departure from documented CUPS behavior (https://www.cups.org/doc/man-cups-files.conf.html). By ignoring cups-files.conf, macOS disables essential administrative controls required for non-standard printing environments. As such, we hope the team will reconsider this approach. If a fixed configuration is necessary for the default security posture, there should still be an alternative that allows legitimate, authorized software to operate in “relaxed” mode. In terms of supporting CUPSD_SANDBOXING_STRICT, am I correct that these two points are the real issues here, not the path limitations? As we mentioned earlier, it is a combination of all three (file/folder access, sub-process handling, and network calls). We are actively working on modifying our backend/filter to accommo
Topic: App & System Services SubTopic: General Tags:
4d
Tahoe 26.2 breaks printing with PaperCut
Issue After upgrading to Tahoe 26.2, print queues monitored by PaperCut no longer work. The print queue gets paused, and the jobs fail to print. This issue was discovered during our internal testing prior to the Tahoe 26.2 public release, and a growing number of our mutual customers have also reported it since then. Root cause This appears to be due to changes in the behavior of CUPS Sandbox restrictions, which prevent the backend (and filter) from reading/writing to the PaperCut install folder. Error messages From syslog. 2025-12-22 16:41:59.283761+1100 0x1daf61 Error 0x0 0 0 kernel: (Sandbox) Sandbox: papercut(5783) deny(1) file-write-data /Library/Printers/PaperCut/Print Provider/print-provider.log When trying to create a TCP socket from the PaperCut filter. 2025-12-15 19:50:08,403 ERROR: os_tcp_socket_create: getaddrinfo failed: nodename nor servname provided, or not known Technical details PaperCut implements print queue monitoring using a CUPS backend (and filter). CUPS backends and filters run in a sec
4
0
502
4d
Reply to Detecting marked range in UI/NSTextViews at the time of shouldChangeTextIn
It seems that iOS does update markedTextRange for me. I tried the following code: func textView(_ textView: UITextView, shouldChangeTextIn range: NSRange, replacementText text: String) -> Bool { if let markedTextRange = textView.markedTextRange { let markedText = textView.text(in: markedTextRange) ?? print(markedText = (markedText), replacementText = (text)) } else { print(replacementText = (text)) } return true } And get the following result when inputting あ and then か with Japanese Kana input method: replacementText = あ markedText = あ, replacementText = か Do you see the same thing? is markedText + replacementText not enough for you to determine whether the input is valid? I tested with iPhone + iOS 26.1(23B85), if that matters. Best, —— Ziqiao Chen  Worldwide Developer Relations.
Topic: UI Frameworks SubTopic: UIKit Tags:
4d
I'm developing a macOS File Provider Extension and encountering a `-2014` (Extension not registered) error when using Testing Mode only.
File Provider Extension Testing Mode -2014 Error Issue I'm developing a macOS File Provider Extension and encountering a -2014 (Extension not registered) error when using Testing Mode only. Environment macOS: 13.0+ Xcode: Latest version Developer Account: Paid Developer Account Extension Type: NSFileProviderReplicatedExtension Current Status App ID Configuration App ID: kr.it.flux.FluxDrive2.FileProvider Capabilities: ✅ com.apple.developer.fileprovider.testing-mode (enabled) ❌ General com.apple.developer.fileprovider (not visible) Extension Configuration NSExtensionPointIdentifier: com.apple.fileprovider NSExtensionPrincipalClass: FluxDrive2FileProvider.FileProviderExtension Code Signing: Valid (Team Identifier verified) Info.plist: Valid Error Message Error Domain=NSFileProviderErrorDomain Code=-2014 The operation couldn't be completed. (NSFileProviderErrorDomain error -2014.) Underlying error: Error Domain=NSFileProviderErrorDomain Code=-2001 Extension cannot be used Attempted Sol
1
0
90
4d
Reply to I'm developing a macOS File Provider Extension and encountering a `-2014` (Extension not registered) error when using Testing Mode only.
I don't have the answer yet, but the explanation of the error code -2001 and -2014, as shown in the following, basically says your app bundle doesn't have a launchable file provider extension, which is pretty strange if your file provier works when the testing mode isn't used. /** Returned by NSFileProviderManager if no provider could be found in the application */ NSFileProviderErrorProviderNotFound FILEPROVIDER_API_AVAILABILITY_V3_IOS = -2001, /* Returned by the system to indicate that the system does not have any launchable `com.apple.fileprovider-nonui` application extension for this domain's app bundle. */ NSFileProviderErrorApplicationExtensionNotFound FILEPROVIDER_API_AVAILABILITY_V6_0_IOS = -2014, You mentioned the general com.apple.developer.fileprovider capability is not visible in Developer Portal and asked how to enable it, which confuses me a bit, because com.apple.developer.fileprovider is never a capability. Would you mind to share where you found the capability and why you believe it
Topic: App & System Services SubTopic: Core OS Tags:
4d
I'm developing a macOS File Provider Extension and encountering a `-2014` (Extension not registered) error when using Testing Mode only.
File Provider Extension Testing Mode -2014 Error Issue I'm developing a macOS File Provider Extension and encountering a -2014 (Extension not registered) error when using Testing Mode only. Environment macOS: 13.0+ Xcode: Latest version Developer Account: Paid Developer Account Extension Type: NSFileProviderReplicatedExtension Current Status App ID Configuration App ID: kr.it.flux.FluxDrive2.FileProvider Capabilities: ✅ com.apple.developer.fileprovider.testing-mode (enabled) ❌ General com.apple.developer.fileprovider (not visible) Extension Configuration NSExtensionPointIdentifier: com.apple.fileprovider NSExtensionPrincipalClass: FluxDrive2FileProvider.FileProviderExtension Code Signing: Valid (Team Identifier verified) Info.plist: Valid Error Message Error Domain=NSFileProviderErrorDomain Code=-2014 The operation couldn't be completed. (NSFileProviderErrorDomain error -2014.) Underlying error: Error Domain=NSFileProviderErrorDomain Code=-2001 Extension cannot be used Attempted Sol
1
0
49
4d
Tahoe sidebar - icon sizing is wrong
Hi there. I am trying to figure out how to make a macOS Tahoe app in SwiftUI with a sidebar. The problem I’m having is that the icons are the wrong size. If you visually compare the resulting sidebar with any built-in macOS app (Finder, Notes, Mail, Music, etc.) the built-in apps all have larger icons and the spacing is different from my SwiftUI app, which has too small icons and (I think) wrong spacing. I am trying to figure out what SwiftUI code I need to write to get a sidebar that looks the same as the other built-in macOS Tahoe apps. It’s also important to note that Tahoe sidebars have larger icons at the top level, and in cases where the items have a disclosure triangle with additional items nested within, the nested icons have smaller icons. I have not figured out how to properly replicate this effect either. I have spent quite a lot of time on trial-and-error with various combinations of .frame() and .font() modifiers. However, none of the results look quite right to me, and besides that, I t
Topic: UI Frameworks SubTopic: SwiftUI Tags:
1
0
64
4d
Reply to Tahoe sidebar - icon sizing is wrong
Thanks for your post. Extremely detailed and interesting. You're right that manually adjusting sizes with and isn't ideal for achieving consistency with native macOS apps, especially across different macOS versions. In previous macOS, I think, SwiftUI provided a way to automatically adjust sidebar icon sizes to match system standards by using modifiers and appropriate view hierarchies. Unfortunately, we are unable to provide any details regarding the design or code for Apple macOS apps. Additionally, the icon sizes may differ from the default icons provided by SwiftUI as you already point it out. Cannot even provide you a way to achieve a sidebar similar to built-in macOS apps, I would recommend for you can leverage the documentation at https://developer.apple.com/documentation/technologyoverviews/adopting-liquid-glass that automatically configures the list to adopt macOS sidebar conventions, including icon sizing and spacing. That Tech Note also provides many different tips to work with the new UI f
Topic: UI Frameworks SubTopic: SwiftUI Tags:
4d
Xcode 26 swiftmodules are incompatible with Xcode 16
I am developing a binary SDK for consumption by others. When we updated to Xcode 26, any builds which are generated cannot be consumed by Xcode 16. The specifics lie in the optionals. The following Swift code generate a .swiftmodule func affectedApi() -> Int? { return 1 } In Xcode 16 it generated the following .swiftmodule in the framework. public func affectedIntApi() -> Swift.Int? In Xcode 26 it adds an if statement. #if compiler(>=5.3) && $NonescapableTypes public func affectedIntApi() -> Swift.Int? #endif That if statement prevents Xcode16 from seeing the API, and it causes compile failures. This happens regardless of which Swift version is used, and it only affects functions which use Optionals. Is there a way to prevent the compiler from wrapping the API in that statement?
2
0
60
4d
How does one get the locale-specific character set encoding on a Cocoa App
If (in terminal) I type 'env', I'll see a line that looks like: LANG=en_GB.UTF-8 And I can parse that to get the 2-char 'en' locale-code, the sub-domain 'GB' and the character-set encoding of UTF-8. All well and good. However in a Cocoa app, I can't seem to find the equivalent for the UTF-8 part. This is a cross-platform app, but at this point I'll go with any solution... I've tried: NSLocale *loc = NSLocale.currentLocale; NSString *lang = loc.localeIdentifier; setlocale(LC_ALL, NULL); char *text = nl_langinfo(CODESET); if (text) NSString *charset = [NSString stringWithUTF8String:text]; NSLog(@lang:%@nchar:%@n,lang, charset); which displays: lang:en-GB char:US-ASCII Also tried: // Search for locale info by preferred environment variable NSProcessInfo *pi = NSProcessInfo.processInfo; NSDictionary *env = pi.environment; NSString *spec = env[@LC_ALL]; if (spec == nil) spec = env[@LC_CTYPE]; if (spec == nil) spec = env[@LANG]; NSLog(@spec:%@n, spec); which displays: spec:(null) Also tried: CFStr
3
0
63
4d