Search results | Apple Developer Forums

Reply to Error while AppStore Connect Upload

So one of the following must be true: You want to use the Background Tasks framework to run long-running tasks via BGProcessingTask. Or you don’t. If you do, add the BGTaskSchedulerPermittedIdentifiers property to your Info.plist and populate it with the list of background task identifiers you use. If you don’t: Remove the processing value from the UIBackgroundModes property in your Info.plist. Remove any code that uses BGProcessingTask. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

App Store Distribution & Marketing App Store Connect

6d

Нow to set default values for string array intent field provided dynamically?

Hello everybody! Does anybody know how to set default values for string array intent field provided dynamically? I want to have preset array field values just after widget added I have a simple accessory widget with circular and rectangular representation (the first one is for 1 currency value and the second one is for 3 values). I created CurrencyWidgets.intentdefinition and added AccessoryCurrency custom intent. Here I added string parameter field currencyCode. For this parameter I set the following options: Supports Multiple Values Fixed Size (AccessoryCircular = 1, AccessoryRectangular = 3) User can edit value in Shortcuts Options are provided dynamically Then I created CurrencyTypeIntent extension and added IntentHandler for my custom intent AccessoryCurrency. The code is below class IntentHandler: INExtension, AccessoryCurrencyIntentHandling { override func handler(for intent: INIntent) -> Any { self } func provideCurrencyCodeOptionsCollection(for intent: AccessoryCurrencyIntent) async throw

App & System Services Widgets & Live Activities WidgetKit Intents App Intents

0

29

6d

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

App & System Services Core OS

6d

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

Safari & Web General

6d

TapGesture stops responding on ViewAttachmentComponent after disabling or removing and re-adding the Entity (visionOS 26)

Issue When an Entity with a ViewAttachmentComponent is: disabled using isEnabled = false removed using removeFromParent() and then enabled or added back again, the attached SwiftUI view is rendered correctly, but tap interactions stop working. Specifically: Button actions inside the attached view do not fire TapGesture closures on child views do not respond Expected Behavior Tap interactions inside the attached view should continue to work after the Entity is re-enabled or re-added. Actual Behavior After being disabled or removed once, all tap interactions stop responding. Comparison When displaying the same SwiftUI view using RealityViewAttachments, this issue does not occur. Removing and re-displaying the attachment still allows taps to work correctly. Reproduction Attached sample code reproduces the issue: A RealityView with an Entity that has a ViewAttachmentComponent The attached SwiftUI view contains a Toggle The toggle updates isEnabled on the Entity After toggling off and on, tap interactions

Graphics & Games RealityKit RealityKit Reality Composer Pro visionOS

2

0

273

6d

Guideline 4.3(a) - Design - Spam

Hello everyone, When I submit the game I developed with Unity, it's constantly being rejected due to Guideline 4.3(a) - Design - Spam. Unfortunately, I haven't received any detailed information. I've changed almost all the assets in the code. I'm not using any code other than my own. But I can't overcome this problem. How can I find out where this problem occurs? Thank you very much in advance for your support.

App Store Distribution & Marketing App Review

1

0

95

6d

macOS Tahoe: IPMonitor incorrectly re-ranks interfaces causing VPN DNS leaks

Description Enterprise users are experiencing VPN resource access failures after upgrading to macOS Tahoe. Investigation indicates that configd (specifically IPMonitor) is incorrectly re-ranking network interfaces after a connectivity failure with probe server. This results in DNS queries routing through the physical network adapter (en0) instead of the VPN virtual adapter, even while the tunnel is active. This behaviour is not seen in previous macOS versions. Steps to Reproduce: Connect to an enterprise VPN (e.g., Ivanti Secure Access). Trigger a transient network condition where the Apple probe server is unreachable. For example make the DNS server down for 30 sec. Observe the system routing DNS queries for internal resources to the physical adapter. Expected Results The: VPN virtual interface should maintain its primary rank for enterprise DNS queries regardless of the physical adapter's probe status. Actual Results: IPMonitor detects an UplinkIssue, deprioritizes the VPN interface, and elevates the physic

App & System Services Networking

5

0

236

6d

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

App & System Services General

6d

HTTP 400 status code

Recently, we completed a merger with our parent company. We are currently integrated with Apple Pay in accordance with the “Apple Pay Payment Processing on the Web” guidelines. Due to the change in the legal entity, we proceeded with the account migration process as outlined below: Creation of a new Apple Developer account and a new Apple Pay Identifier Removal of the Merchant Domain (dc2-web.happy.co.kr) from the existing Identifier Registration of the Merchant Domain (dc2-web.happy.co.kr) under the new Identifier Using the Merchant Domain registered under the new Identifier and the Apple Pay Merchant Identity Certificate issued from the new Identifier, we attempted to obtain an Apple Pay session by sending requests to the following endpoint: https://apple-pay-gateway.apple.com/paymentservices/startSession However, we are intermittently receiving failure responses with an HTTP 400 status code. With regard to these intermittent failures, we would like to inquire whether there is any propagation delay

App & System Services Apple Pay

0

87

6d

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.

UI Frameworks UIKit

6d

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

App & System Services Core OS

6d

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

UI Frameworks SwiftUI

6d

UIButtonConfiguration and button disabled state

I am trying to use the UIButtonConfiguration to set the UI state for the button.isEnabled status. I do see the ConfigurationUpdateHandler code below being executed but when the button.isEnabled is set to false, the UI does not reflect the updated backgroundColor. Instead it is a very light gray but the foregroundColor/text is being updated. It seems that the default disabled button treatment is being used despite being set to a different color. Is there a better way to suppress the default UIButton disabled state so I can customize? [newButton setConfigurationUpdateHandler:^(__kindof UIButton * _Nonnull button) { UIButtonConfiguration *updatedConfiguration; if (newButton.configuration != nil) { updatedConfiguration = newButton.configuration; if (button.isEnabled) { updatedConfiguration.baseBackgroundColor = [UIColor darkGrayColor]; updatedConfiguration.baseForegroundColor = [UIColor whiteColor]; } else { updatedConfiguration.baseBackgroundColor = [UIColor greenColor]; updatedConfiguration.baseForegro

UI Frameworks UIKit

1

0

127

6d

Reply to Setting alternate app icon fails with "Ressource temporarily not available"

I've encountered this exact same problem. I follow this guide to a tee: https://developer.apple.com/documentation/xcode/configuring-your-app-to-use-alternate-app-icons And yet I am consistently hit with: Failed: Error Domain=NSPOSIXErrorDomain Code=35 Resource temporarily unavailable UserInfo={_LSFile=LSIconAlertManager.m, _LSLine=113, _LSFunction=-[LSIconAlertManager iconChangeAlertTokenForIdentity:error:]} My app targets iPads and iPhones, has a minimum version for iOS of 18, and I am not using a simulator, I am running on my own device (iPhone 17 on iOS 26.2). This has been driving me insane. The example project Apple provides works, so I cannot see what possibly could be different.

UI Frameworks UIKit

6d

Reply to Tahoe 26.2 breaks printing with PaperCut

The sandbox-relaxed mode works up to 26.1 and stopped working in 26.2. So, with a bit more digging, I was able to figure out what's going on here. Basically, as part of a security fix (r.157744252) in macOS 26.2, CUPS was changed to use a fixed configuration, by its config file (/etc/cups/cups-files.conf). That's actually what explains this: As an alternative to the relaxed mode, we also tried Sandboxing off, but that doesn't help either (from CUPS scheduler/conf.h). ...as CUPS was actually always running at CUPSD_SANDBOXING_STRICT, regardless of how you configured it. Is there anything we can configure or modify in the system to achieve the old behaviour of sandbox-relaxed mode? If for some reason, we can’t get back to the previous sandbox-relaxed behaviour, is there a way for us to switch off the sandbox? No, I don't think so. The core problem here is that the sandbox configuration itself hasn't actually changed; cupsd is just ignoring any configuration file. I think you can see this directly if you try pas

App & System Services General

6d

DTiPhoneSimulatorErrorDomain Code 2

Post

Replies

Boosts

Views

Activity