Search results for

“missing package product”

52,426 results found

Post

Replies

Boosts

Views

Activity

Validation error with Network Extension due to square brackets in Product Name
Hello, I am facing a validation error when uploading a macOS app with a Network Extension. The Error: Invalid system extension. The system extension at “[T] TEXT.app/Contents/Library/SystemExtensions/company_name.network-extension.systemextension” resides in an unexpected location. The Problem: Validation fails only when the app's Product Name contains square brackets: [T] TEXT. If I remove the brackets from the Product Name, validation passes. What I've tried: Setting Product Name to TEXT (without brackets) and CFBundleDisplayName to [T] TEXT. Cleaning Derived Data and rebuilding the archive. Verified that the extension is physically located at Contents/Library/SystemExtensions/. It seems the Apple validation tool fails to parse the bundle path correctly when it contains characters like [ or ]. Question: How can I keep the app name with brackets for the user (in System Settings and Menu Bar) while ensuring the Network Extension passes validation? Is there a way to escape these char
1
0
125
4w
Reply to Frequent providerDidReset Callbacks in Production
We're seeing a high rate of providerDidReset callbacks in production across a large user base (iOS 16, 17, 18, and 26). How frequent is frequent? The documentation states that providerDidReset signals the provider has been reset and all calls should be considered terminated. Should we be calling CXProvider.invalidate() on the old instance before creating a new one? Or is assigning a new CXProvider to cxProvider (which releases the old instance) sufficient? My recommendation would be that you destroy all existing call infrastructure (both CXProvider and all other CallKit crashes), call invalidate as well, then recreate a new CXProvider and recreate all other call infrastructure. Having said that, the EXACT details of that process generally don't matter all that much. All existing CallKit objects will be non-functional; most VoIP apps don't persist long enough that issues like small amounts of leaked memory actually become relevant. What could be causing providerDidReset to fire so frequently, and how
Topic: App & System Services SubTopic: Core OS Tags:
Mar ’26
App Stuck in “Waiting for Review” for Over 2 Weeks (Since Feb 20)
Hello everyone, I am an iOS developer based in South Korea, and I’m currently experiencing an unusual App Store review delay that I have not been able to resolve through the normal support channels. My app has been stuck in “Waiting for Review” for more than two weeks, and there has been no progress at all during this time. It has not moved to “In Review”, and I have not received any rejection message or request for additional information from the App Review team. App Information Platform: iOS App Name: WOOTA Apple ID: 6759412826 Status: Waiting for Review Submission Date: February 20, 2026 Developer Account Region: South Korea What I Have Already Tried: I have already attempted the following steps: Submitted an inquiry via App Store Connect → Contact Us → App Review Received a response from Developer Support saying they understand my concern and that they contacted the review team However, since then there have been no updates at all. The app status remains “Waiting for Review”, and there are no messages in
2
0
142
Mar ’26
Reply to Driver Activation failure error code 9. Maybe Entitlements? Please help
Hello again, Kevin, and thank you again for your help. I notice that you commented 18 hrs ago, but I could have sworn I checked yesterday and there wasn't anything here. I ended up getting matching working by also specifying version number, which increased my probe score. And... you should also be aware of the version number limitation described here, which is another arbitrary restriction the kernel enforces. you definitely predicted my next issue. I prefer date-based build and version numbers, and this one was problematic, but your link helped me fit a date based number into that parsing code. If anyone else wants to try that, I used BUILD_NUMBER=$(date '+%Y.%m%d.%H%Mf%S') in my update script, which yields a version number e.g. 2026.0303.1749f09. The arbitrary f enables me to get past that 4[letter]3 format. I picked f only because it looks similar to an s. Before I move onto my current problem... Can you do that, perhaps by operating at the device instead of interface level? Could you explain what you mean
Topic: App & System Services SubTopic: Drivers Tags:
Mar ’26
Reply to Is calling different SBApplication objects from different threads bad?
Hooboy, knowing if we've seen it on Intel machines will take some digging. The M1 Studios we have are 2022. Our ScriptingBridge code was added in June 2023. The first internal mention of errOSAInternalTableOverflow is December 2023. The M1 Studios weren't put into production until March 2024 (that's how slow our IT department moves). By this timeline, it appears we were seeing errOSAInternalTableOverflow on Intel. As for the actual crash described in this thread and bug, that I'm not sure about. I'm assuming that getting errOSAInternalTableOverflow and this crash are caused by the same underlying bug. No PowerPC Macs have been in use during my tenure at this job. Naturally, I figured it would be a very long time until a possible Apple fix would reach our production machines. Time to diagnose + time to fix & test + time to release + time for our IT department to OK the user of that version of macOS. I just might be retired by then. Moving the bulk of the job code to a separate helper app
Mar ’26
Reply to FileManager.replaceItemAt(_:withItemAt:) fails sporadically on ubiquitous items
Thanks again for the reply, and especially for such a thorough and helpful one! For example, I suspect this doesn't happen if you start with a security-scoped bookmark, which you resolve to a bookmark before each save. Out of curiosity I just tested this, and I still see the bug. To see it yourself, just use the code from my first post but change the savingURL accessor to use a security-scoped bookmark, as follows: private var bookmarkData: Data? // Ask user to choose this via a save panel. var savingURL: URL? { get { var isStale = false if let bookmarkData, let url = try? URL(resolvingBookmarkData: bookmarkData, options: .withSecurityScope, relativeTo: nil, bookmarkDataIsStale: &isStale) { if isStale { // Should really update the bookmark data here... } return url } else { return nil } } set(newURL) { bookmarkData = try? newURL?.bookmarkData(options: .withSecurityScope) setUpSpamSave() } } Then add the following to the top of spamSave() after checking savingURL is non-nil: let didAccess = savingURL.start
Topic: App & System Services SubTopic: Core OS Tags:
Mar ’26
Live Caller ID Lookup: does iOS call /queries even when the number is in Contacts?
Hi! We’ve had Live Caller ID Lookup in production for a while. We’re seeing backend RPS on our /queries endpoint much higher than our expected incoming call volume. While testing with Console.app during an incoming call, it looks like iOS may still hit our service even when the caller number is already in the user’s Contacts - but I’m not 100% sure from logs alone. Can you confirm: Does iOS invoke Live Caller ID Lookup (i.e. call /queries) for every incoming call, including calls from saved Contacts? If yes, is this simply expected framework behavior? Thanks!
0
0
97
Mar ’26
Account Holder locked out of developer.apple.com since January 18 - 9 support requests ignored
I am the Account Holder (Team ID: KCRXG75U7S). Since January 18, 2026, I cannot access developer.apple.com — it redirects to the Need assistance contact form. App Store Connect works fine. I have live apps on the App Store. On January 18, I received unexpected Welcome to the Apple Developer Program and You're invited to join a development team emails, even though I was already a member. After that, all access to the developer portal was lost. I have submitted 9+ support requests since February 11. Not a single one has received a response. Chat support disconnects. Phone support only creates new cases. Case IDs: 102835281938, 102824841068, 102819959750, 20000111583405, 20000111568823 Can any Apple engineer please look into this?
1
0
124
Mar ’26
Frequent providerDidReset Callbacks in Production
Hello, We're seeing a high rate of providerDidReset callbacks in production across a large user base (iOS 16, 17, 18, and 26). I'd like to understand both the correct way to handle this delegate method and strategies to reduce its frequency. Background The callback occurs across all iOS versions we support and is not isolated to a specific device or region. The callback can occur in any app state (foreground, background, inactive), however it is most dominant in the background state — particularly during VoIP push notification handling. The callback is more prevalent during long app sessions — for example, when the app has been running continuously for a day or overnight. We do not call CXProvider.invalidate() anywhere in our codebase explicitly. After providerDidReset fires, subsequent transactions fail with CXErrorCodeRequestTransactionErrorUnknownCallUUID (error code 4). Re-initializing the provider via initializeProvider() resolves this error. Our Implementation We use a singleton proxy class (Ca
1
0
147
Mar ’26
Reply to Push notifications not delivered over Wi-Fi with includeAllNetworks = true regardless of excludeAPNS setting
[quote='877954022, pawanquantum, /thread/817434?answerId=877954022#877954022, /profile/pawanquantum'] The sample code I shared reproduces this exact state — it's a loopback tunnel that never forwards packets. [/quote] Sure, but that’s not how packet tunnel providers products usually work. In most cases the provider won’t bring up the tunnel, by calling setTunnelNetworkSettings(…), until it’s ready to actually forward packets. You have a couple of choices here: You can file a bug requesting that we change iOS to make this work. You can change your packet tunnel provider so that it works in the standard way. Or you could do both (-: If you do file a bug: Make sure that your bug report explains why you packet tunnel provider has to bring up the tunnel before it’s ready to forward packets. Without that, your bug is likely to get bounced back saying ‘stop doing that’. Enable additional NE debugging on your test device, via the VPN (Network Extension) for iOS/iPadOS profile on our Bug Reporting > Profil
Mar ’26
Reply to Random global network outage triggered by NEFilterDataProvider extension – only reboot helps, reinstall doesn't
[quote='878094022, WangZiYuan, /thread/817264?answerId=878094022#878094022, /profile/WangZiYuan'] I’m not quite sure what you mean by the 'sysex process.' [/quote] OK, lemme clarify. On macOS, content filters must be packaged as a system extension [1], aka a sysex. A sysex is much like a launchd daemon, in that it can potentially run for the entire boot cycle, that is, start when you boot the Mac and not stop until you shut down [2]. Your Network Extension provider instances are created within that sysex process. So, consider this sequence: You boot your Mac. Your sysex starts. NE instantiates your content file provider within that sysex process. You stop the filter. NE stops the content filter provider. At this point the system may or may not stop your sysex process. But let’s consider what happens if it doesn’t… You start the filter again. NE instantiates your content file provider again, still within the same sysex process. So, my questions are: Are you seeing the sysex process stop at step 6? If
Mar ’26
Reply to NEPacketTunnelFlow: large UDP DNS responses (~893 bytes) silently dropped despite writePacketObjects() returning success
[quote='817442021, miekari, /thread/817442, /profile/miekari'] I'm using NEPacketTunnelProvider to intercept DNS queries, forward them upstream [/quote] What does “upstream” mean in this context? Most VPN products don’t need to mess with DNS. Rather, the packet tunnel provider forwards DNS packets to the VPN server which forwards them to their destination, just like any other packet. And the same process works in reverse. If you want to intercept just DNS traffic, a DNS proxy is a much better option. DNS proxies receive flows rather than packets. And in the case of DNS over UDP, the flow works in terms of datagrams rather than packets. I see a lot of folks try to use a packet tunnel provider for things other than VPN, for example, as an ersatz DNS proxy. This isn’t something that DTS supports. See TN3120 Expected use cases for Network Extension packet tunnel providers. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Mar ’26
Xcode 26 fails to load SPM packages
For me it looks like Xcode 26 has problems reading SPM packages from a locally hosted BitBucket git solution. While Xcode 16 work perfectly fine, Xcode 26 fails to load and gives Server SSH Fingerprint Failed to Verify as error description. Cleaning build data and DerivedData sometimes makes loading work. Any change in Package dependencies will break it again. Anyone having same problems? How do you handle it?
9
0
939
Mar ’26
Validation error with Network Extension due to square brackets in Product Name
Hello, I am facing a validation error when uploading a macOS app with a Network Extension. The Error: Invalid system extension. The system extension at “[T] TEXT.app/Contents/Library/SystemExtensions/company_name.network-extension.systemextension” resides in an unexpected location. The Problem: Validation fails only when the app's Product Name contains square brackets: [T] TEXT. If I remove the brackets from the Product Name, validation passes. What I've tried: Setting Product Name to TEXT (without brackets) and CFBundleDisplayName to [T] TEXT. Cleaning Derived Data and rebuilding the archive. Verified that the extension is physically located at Contents/Library/SystemExtensions/. It seems the Apple validation tool fails to parse the bundle path correctly when it contains characters like [ or ]. Question: How can I keep the app name with brackets for the user (in System Settings and Menu Bar) while ensuring the Network Extension passes validation? Is there a way to escape these char
Replies
1
Boosts
0
Views
125
Activity
4w
Reply to Frequent providerDidReset Callbacks in Production
We're seeing a high rate of providerDidReset callbacks in production across a large user base (iOS 16, 17, 18, and 26). How frequent is frequent? The documentation states that providerDidReset signals the provider has been reset and all calls should be considered terminated. Should we be calling CXProvider.invalidate() on the old instance before creating a new one? Or is assigning a new CXProvider to cxProvider (which releases the old instance) sufficient? My recommendation would be that you destroy all existing call infrastructure (both CXProvider and all other CallKit crashes), call invalidate as well, then recreate a new CXProvider and recreate all other call infrastructure. Having said that, the EXACT details of that process generally don't matter all that much. All existing CallKit objects will be non-functional; most VoIP apps don't persist long enough that issues like small amounts of leaked memory actually become relevant. What could be causing providerDidReset to fire so frequently, and how
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Mar ’26
App Stuck in “Waiting for Review” for Over 2 Weeks (Since Feb 20)
Hello everyone, I am an iOS developer based in South Korea, and I’m currently experiencing an unusual App Store review delay that I have not been able to resolve through the normal support channels. My app has been stuck in “Waiting for Review” for more than two weeks, and there has been no progress at all during this time. It has not moved to “In Review”, and I have not received any rejection message or request for additional information from the App Review team. App Information Platform: iOS App Name: WOOTA Apple ID: 6759412826 Status: Waiting for Review Submission Date: February 20, 2026 Developer Account Region: South Korea What I Have Already Tried: I have already attempted the following steps: Submitted an inquiry via App Store Connect → Contact Us → App Review Received a response from Developer Support saying they understand my concern and that they contacted the review team However, since then there have been no updates at all. The app status remains “Waiting for Review”, and there are no messages in
Replies
2
Boosts
0
Views
142
Activity
Mar ’26
Reply to Driver Activation failure error code 9. Maybe Entitlements? Please help
Hello again, Kevin, and thank you again for your help. I notice that you commented 18 hrs ago, but I could have sworn I checked yesterday and there wasn't anything here. I ended up getting matching working by also specifying version number, which increased my probe score. And... you should also be aware of the version number limitation described here, which is another arbitrary restriction the kernel enforces. you definitely predicted my next issue. I prefer date-based build and version numbers, and this one was problematic, but your link helped me fit a date based number into that parsing code. If anyone else wants to try that, I used BUILD_NUMBER=$(date '+%Y.%m%d.%H%Mf%S') in my update script, which yields a version number e.g. 2026.0303.1749f09. The arbitrary f enables me to get past that 4[letter]3 format. I picked f only because it looks similar to an s. Before I move onto my current problem... Can you do that, perhaps by operating at the device instead of interface level? Could you explain what you mean
Topic: App & System Services SubTopic: Drivers Tags:
Replies
Boosts
Views
Activity
Mar ’26
Reply to Is calling different SBApplication objects from different threads bad?
Hooboy, knowing if we've seen it on Intel machines will take some digging. The M1 Studios we have are 2022. Our ScriptingBridge code was added in June 2023. The first internal mention of errOSAInternalTableOverflow is December 2023. The M1 Studios weren't put into production until March 2024 (that's how slow our IT department moves). By this timeline, it appears we were seeing errOSAInternalTableOverflow on Intel. As for the actual crash described in this thread and bug, that I'm not sure about. I'm assuming that getting errOSAInternalTableOverflow and this crash are caused by the same underlying bug. No PowerPC Macs have been in use during my tenure at this job. Naturally, I figured it would be a very long time until a possible Apple fix would reach our production machines. Time to diagnose + time to fix & test + time to release + time for our IT department to OK the user of that version of macOS. I just might be retired by then. Moving the bulk of the job code to a separate helper app
Replies
Boosts
Views
Activity
Mar ’26
Reply to FileManager.replaceItemAt(_:withItemAt:) fails sporadically on ubiquitous items
Thanks again for the reply, and especially for such a thorough and helpful one! For example, I suspect this doesn't happen if you start with a security-scoped bookmark, which you resolve to a bookmark before each save. Out of curiosity I just tested this, and I still see the bug. To see it yourself, just use the code from my first post but change the savingURL accessor to use a security-scoped bookmark, as follows: private var bookmarkData: Data? // Ask user to choose this via a save panel. var savingURL: URL? { get { var isStale = false if let bookmarkData, let url = try? URL(resolvingBookmarkData: bookmarkData, options: .withSecurityScope, relativeTo: nil, bookmarkDataIsStale: &isStale) { if isStale { // Should really update the bookmark data here... } return url } else { return nil } } set(newURL) { bookmarkData = try? newURL?.bookmarkData(options: .withSecurityScope) setUpSpamSave() } } Then add the following to the top of spamSave() after checking savingURL is non-nil: let didAccess = savingURL.start
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Mar ’26
Live Caller ID Lookup: does iOS call /queries even when the number is in Contacts?
Hi! We’ve had Live Caller ID Lookup in production for a while. We’re seeing backend RPS on our /queries endpoint much higher than our expected incoming call volume. While testing with Console.app during an incoming call, it looks like iOS may still hit our service even when the caller number is already in the user’s Contacts - but I’m not 100% sure from logs alone. Can you confirm: Does iOS invoke Live Caller ID Lookup (i.e. call /queries) for every incoming call, including calls from saved Contacts? If yes, is this simply expected framework behavior? Thanks!
Replies
0
Boosts
0
Views
97
Activity
Mar ’26
Account Holder locked out of developer.apple.com since January 18 - 9 support requests ignored
I am the Account Holder (Team ID: KCRXG75U7S). Since January 18, 2026, I cannot access developer.apple.com — it redirects to the Need assistance contact form. App Store Connect works fine. I have live apps on the App Store. On January 18, I received unexpected Welcome to the Apple Developer Program and You're invited to join a development team emails, even though I was already a member. After that, all access to the developer portal was lost. I have submitted 9+ support requests since February 11. Not a single one has received a response. Chat support disconnects. Phone support only creates new cases. Case IDs: 102835281938, 102824841068, 102819959750, 20000111583405, 20000111568823 Can any Apple engineer please look into this?
Replies
1
Boosts
0
Views
124
Activity
Mar ’26
Reply to stuck in “Waiting for Review” since February 7
yeah, defiantly BS from @apple on this. My clients are waiting, opportunities are being missed. I understand things happen, but be transparent and let us plan accordingly. i submitted apps in the begining of feb and they were approved in a day or two. I submittted one for a new client on feb 12th and its still waiting for review
Replies
Boosts
Views
Activity
Mar ’26
Frequent providerDidReset Callbacks in Production
Hello, We're seeing a high rate of providerDidReset callbacks in production across a large user base (iOS 16, 17, 18, and 26). I'd like to understand both the correct way to handle this delegate method and strategies to reduce its frequency. Background The callback occurs across all iOS versions we support and is not isolated to a specific device or region. The callback can occur in any app state (foreground, background, inactive), however it is most dominant in the background state — particularly during VoIP push notification handling. The callback is more prevalent during long app sessions — for example, when the app has been running continuously for a day or overnight. We do not call CXProvider.invalidate() anywhere in our codebase explicitly. After providerDidReset fires, subsequent transactions fail with CXErrorCodeRequestTransactionErrorUnknownCallUUID (error code 4). Re-initializing the provider via initializeProvider() resolves this error. Our Implementation We use a singleton proxy class (Ca
Replies
1
Boosts
0
Views
147
Activity
Mar ’26
Reply to Push notifications not delivered over Wi-Fi with includeAllNetworks = true regardless of excludeAPNS setting
[quote='877954022, pawanquantum, /thread/817434?answerId=877954022#877954022, /profile/pawanquantum'] The sample code I shared reproduces this exact state — it's a loopback tunnel that never forwards packets. [/quote] Sure, but that’s not how packet tunnel providers products usually work. In most cases the provider won’t bring up the tunnel, by calling setTunnelNetworkSettings(…), until it’s ready to actually forward packets. You have a couple of choices here: You can file a bug requesting that we change iOS to make this work. You can change your packet tunnel provider so that it works in the standard way. Or you could do both (-: If you do file a bug: Make sure that your bug report explains why you packet tunnel provider has to bring up the tunnel before it’s ready to forward packets. Without that, your bug is likely to get bounced back saying ‘stop doing that’. Enable additional NE debugging on your test device, via the VPN (Network Extension) for iOS/iPadOS profile on our Bug Reporting > Profil
Replies
Boosts
Views
Activity
Mar ’26
Reply to Random global network outage triggered by NEFilterDataProvider extension – only reboot helps, reinstall doesn't
[quote='878094022, WangZiYuan, /thread/817264?answerId=878094022#878094022, /profile/WangZiYuan'] I’m not quite sure what you mean by the 'sysex process.' [/quote] OK, lemme clarify. On macOS, content filters must be packaged as a system extension [1], aka a sysex. A sysex is much like a launchd daemon, in that it can potentially run for the entire boot cycle, that is, start when you boot the Mac and not stop until you shut down [2]. Your Network Extension provider instances are created within that sysex process. So, consider this sequence: You boot your Mac. Your sysex starts. NE instantiates your content file provider within that sysex process. You stop the filter. NE stops the content filter provider. At this point the system may or may not stop your sysex process. But let’s consider what happens if it doesn’t… You start the filter again. NE instantiates your content file provider again, still within the same sysex process. So, my questions are: Are you seeing the sysex process stop at step 6? If
Replies
Boosts
Views
Activity
Mar ’26
Reply to NEPacketTunnelFlow: large UDP DNS responses (~893 bytes) silently dropped despite writePacketObjects() returning success
[quote='817442021, miekari, /thread/817442, /profile/miekari'] I'm using NEPacketTunnelProvider to intercept DNS queries, forward them upstream [/quote] What does “upstream” mean in this context? Most VPN products don’t need to mess with DNS. Rather, the packet tunnel provider forwards DNS packets to the VPN server which forwards them to their destination, just like any other packet. And the same process works in reverse. If you want to intercept just DNS traffic, a DNS proxy is a much better option. DNS proxies receive flows rather than packets. And in the case of DNS over UDP, the flow works in terms of datagrams rather than packets. I see a lot of folks try to use a packet tunnel provider for things other than VPN, for example, as an ersatz DNS proxy. This isn’t something that DTS supports. See TN3120 Expected use cases for Network Extension packet tunnel providers. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Replies
Boosts
Views
Activity
Mar ’26
Xcode 26 fails to load SPM packages
For me it looks like Xcode 26 has problems reading SPM packages from a locally hosted BitBucket git solution. While Xcode 16 work perfectly fine, Xcode 26 fails to load and gives Server SSH Fingerprint Failed to Verify as error description. Cleaning build data and DerivedData sometimes makes loading work. Any change in Package dependencies will break it again. Anyone having same problems? How do you handle it?
Replies
9
Boosts
0
Views
939
Activity
Mar ’26
Reply to Sharing all container content
I feel like all entities are not routed to my shared zone. Maybe something missing in my xcdatamodeld file.
Replies
Boosts
Views
Activity
Mar ’26