We've received logs and have spuriously reproduced the following behavior: calls to setTunnelNetworkSettings completing with NETunnelProviderError where the code is networkSettingsInvalid, and the error domain string is empty. After subsequent calls to setTunnelNetworkSettings, the tunnel is stopped via the userInitiated stop reason within around 1 second from the first failure. This happens after a number of successful calls to setTunnelNetworkSettings have been made in the lifetime of a given packet tunnel process. We can confirm that no user ever initiates the disconnection. We can confirm that the only significant changes between the different calls to setTunnelNetworkSettings are that the parameters contain different private IPs for the tunnel settings - the routes and DNS settings remain the same. In our limited testing, it seems that we can replicate the behavior we're observing by removing the VPN profile while the tunnel is up. However, we are certain the same behavior happens under other ci
Search results for
DTiPhoneSimulatorErrorDomain Code 2
158,659 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
I think you’re mixing up your terminology here. There’s no such thing as a “legacy Team ID”. Rather, I think you’re talking about a unique App ID prefix. I wrote up a detailed explanation of this stuff last year. I’ve been meaning to publish it officially, but ran out of time, so I’ve post a draft here on the forums as Code Signing Identifiers Explained. As explained in that post, it’s possible to migrate your app’s App ID prefix from a unique value to your Team ID, but there are some potential pitfalls. Please read it through and write back here if you have follow-up questions. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Tags:
Hello, I’m having trouble accessing the Tap to Pay on iPhone Marketing Toolkit for Canada. I’m trying to complete section 6 of the Tap to Pay checklist, which directs me to the Marketing Toolkit page. After visiting the link, I enter our Team ID and select Canada as the region. This takes me to a page with Box links and passwords for each region. However, the password for Canada doesn’t work. When I enter it I receive an error: “Wrong password.” I’m not sure how to proceed from here. I’ve contacted Developer Support twice over the past two weeks but haven’t received a response yet. I’m hoping someone here can help me get access. Thank you, Alex
@135_110 My guess is that the most important was finding the right idea for the app, that looks original and fun to use. Note it is required that it showcase Apple's platform capability through the wise use of API. For the coding, I would not be surprised they spent hundreds of hours to fine tune their app. But let's them say if they get the post. And go this year, at least to get your feet wet. You'll learn for seriously competing next year. Good luck.
Topic:
Community
SubTopic:
Swift Student Challenge
Tags:
My #1 crash report since iOS 26 is the following: 1 libobjc.A.dylib objc_exception_throw 2 Foundation -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] 3 UIKitCore -[UINavigationBar layoutSubviews] 4 UIKitCore UIView._layoutSubviewsWithObservationTracking() 5 UIKitCore @objc UIView._layoutSubviewsWithObservationTracking() Thread 0 9 libobjc.A.dylib objc_exception_throw 10 Foundation -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] 11 UIKitCore -[UINavigationBar layoutSubviews] 12 UIKitCore UIView._layoutSubviewsWithObservationTracking() 13 UIKitCore @objc UIView._layoutSubviewsWithObservationTracking() I tried many things, without success so far. It seemed related to the new view update with observation tracking: link to documentation Any lead on how I should investigate this? Many thanks in advance!!
Hi, We are facing the issue of commissioning our Matter device to google home through iOS device will be 100% failed. Here is our test summary regarding the issue: TestCase1 [OK]: Commissioning our Matter 1.4.0 device to Google Nest Hub 2 by Android device (see log DoorWindow_2.0.1_Google_Success.txt ) TestCase2 [NG]: Commissioning Matter 1.4.0 device to Google Nest Hub 2 by iPhone13 or iPhone16 (see log DoorWindow_2.0.1_Google_by_iOS_NG.txt ) TestCase3 [OK]: Commissioning our Matter 1.3.0 device to Google Nest Hub 2 by iPhone13 In TestCase2, we noticed that device was first commissioned to iOS(Apple keychain) then iOS opened a commissioning window again to commission it in Google’s ecosystem, and the device was failed at above step 2, so we also tried: Commissioning the device to Apple Home works as expected, next share the device to Google Home app on iOS, this also fails. Commissioning the device to Apple Home works as expected, next share the device to Google Home app o
Same happened to me, I think i sent two orders. i thought i forgot to complete payment, so i completed another order. confused as hell
Topic:
Developer Tools & Services
SubTopic:
Apple Developer Program
Tags:
In my application, I use CallKit and have supportsHolding = true set. During my phone call, another call comes in (e.g., GSM). I accept the incoming call and put the current call on hold. If I end the active call myself, everything is fine, and CallKit calls the method provider(_ provider: CXProvider, didActivate audioSession: AVAudioSession). However, if the other party ends the call, the second call remains on hold. In the application, the user clicks on unhold, and I notify CallKit that the hold has ended. But in this case, the didActivate method is not called at all. If I try to activate the audio myself after unhold, I receive the error: Domain=NSOSStatusErrorDomain Code=561017449 Session activation failed UserInfo={NSLocalizedDescription=Session activation failed} AVAudioSessionErrorInsufficientPriority == NSOSStatusErrorDomain Code: 561017449 What needs to be done for CallKit to activate my audio?
We have an app in Swift that uses push notifications. It has a deployment target of iOS 15.0 I originally audited our app for iOS 26 by building it with Xcode 26 beta 3. At that point, all was well. Our implementation of application:didRegisterForRemoteNotificationsWithDeviceToken was called. But when rebuilding the app with beta 4, 5 and now 6, that function is no longer being called. I created a simple test case by creating a default iOS app project, then performing these additional steps: Set bundle ID to our app's ID Add the Push Notifications capability Add in application:didRegisterForRemoteNotificationsWithDeviceToken: with a print(HERE) just to set a breakpoint. Added the following code inside application:didFinishLaunchingWithOptions: along with setting a breakpoint on the registerForRemoteNotifications line: UNUserNotificationCenter.current().requestAuthorization(options: [.badge, .alert, .sound]) { granted, _ in DispatchQueue.main.async { UIApplication.shared.registerForRemoteNotifications
I am not an Apple employee, but there's a good chance most of the Apple apps you mentioned use Mac Catalyst because they were originally written for iOS with UIKit. Porting a UIKit app using Mac Catalyst is going to be faster than writing a Mac version from scratch. I don't see the advantage of using Mac Catalyst for a new SwiftUI app project. SwiftUI supports both iOS and Mac so you can share a lot of the same code and provide a native Mac experience. If you don't want to provide a native Mac experience, you can avoid Mac Catalyst, make an iOS app, and let people with Apple Silicon Macs run the iPad version. I have never used Mac Catalyst so I can't tell you how mature it is.
Topic:
UI Frameworks
SubTopic:
General
Tags:
DisplayRepresentation.Image(systemName:tintColor:symbolConfiguration:) no longer applies the provided tintColor reliably since iOS 18. Observed behavior by OS version: iOS 17: SF Symbol tint is applied consistently as expected. iOS 18: SF Symbol tint is inconsistent and sometimes appears with incorrect or seemingly random colors instead of the provided tintColor. iOS 26: SF Symbol is rendered without any tint (default monochrome), completely ignoring the provided tintColor. This appears to be a regression in how App Intents renders DisplayRepresentation.Image with tinting across OS versions. iOS17.5: iOS 18.6: iOS26: Code: import AppIntents import UIKit struct CategoryEntity: AppEntity, Hashable { var id: Category.ID var name: String var icon: Int? var color: Int? var parentCategoryName: String? init(from category: Category) { self.id = category.id self.name = category.name self.icon = category.icon self.color = category.parent?.color ?? category.color self.parentCategoryName = category.parent?.name
It doesn't make much sense to make Statistics as an AppEntity as this is only computed as a result. You're spot on with that thought, which is why there's TransientAppEntity. There's even an example of generated statistics to show this API off in a sample code project — take a look at the ActivityStatisticsSummary structure in that project! — Ed Ford, DTS Engineer
Topic:
UI Frameworks
SubTopic:
SwiftUI
Tags:
Hi, I am developing IOS(Android App) with React Native. I am very confused about cocoapods and pod and how to correctly install it on my new Macbook Pro M4. I am not using bash but I am using zsh. Note, actuallywhich pod return nothing During the preparation of my environment, it say CocoaPods is one of the dependency management system available for iOS. CocoaPods is a Ruby gem. You can install CocoaPods using the version of Ruby that ships with the latest version of macOS. the web site show two commands gem install cocoapods sudo gem install cocoapods I saw another command as well brew install cocoapods During different processes, I experienced several time the following error (Command 'pod install failed) Command pod install failed. └─ Cause: pod install --repo-update --ansi exited with non-zero code: 1 Then I am confused about cocoapods and pod. Are both he same? With my previous MacBook pro, I spend time to install cocoapod on my profile because Ruby was not the latest version on the sys
Topic:
Developer Tools & Services
SubTopic:
General
Three letter prefixes are the recommendation here to avoid runtime name collisions with Apple's system frameworks for exactly this reason, and that advice is in the Objective-C Programming Guide: Two-letter prefixes like these are reserved by Apple for use in framework classes [...] Your own classes should use three letter prefixes. — Ed Ford, DTS Engineer
Topic:
Community
SubTopic:
Apple Developers
Out of curiosity, is it possible to set a cancellation handler for the class-based API using an NWPathMonitor instance? i.e. is there a way to derive a nw_path_monitor_t from such an instance? No, I don't think so. The development path from the original C library to the modern Swift syntax was a bit messy, and I don't think we really made any effort to provide a path between the two. They were intended to be direct replacements for each other, so there wasn't really any reason to switch between the two. A few other suggestions/notes that may be useful to be aware of: Some of the C APIs’ design has more to do with API symmetry than useful functionality. Case in point, I have a very difficult time thinking of any reason why you'd actually need a cancellation handler for NWPathMonitor. It's a lightweight object (notably, it doesn't do any actual networking”) and I can't really think of any reason why you'd care about when it ACTUALLY finished cancelling. The primary reason the C API exists is f
Topic:
App & System Services
SubTopic:
Networking
Tags: