Search results for

missing package product

51,078 results found

Post

Replies

Boosts

Views

Activity

App Encryption Documentation (France) approval + first iOS review - average release time
Hello, my first app for macOS got approved within 72 hours which was nice + updates were approved fast. But my other submission for iOS got rejected (Moderation tools and content filtering was missing), then I provided an update (fixing these guideline issues) and waited but nothing happened. With the fixed update my app supports also encryption which means I can only distribute in France if I upload the App Encryption Documentation for France, which I of course did. Now before resubmitting the app, I have to wait until this document for France is getting reviewed. I wonder how long this is going to take. Do you think I can expect a release until Friday? Can't wait to start my advertisement campaign. :)
0
0
60
Nov ’25
VPP License Management - How to Handle When [clientUserIdStr] is Not Included in the Response
We are managing VPP license switching operations using Apple's VPP Manage Licenses API. License information is managed by matching the “clientUserIdStr” data with the VPP account ID information managed on the server side. We received an inquiry stating that a VPP license did not activate despite the activation process being performed. Upon checking the API results, the update API returned a success status during execution. However, the “clientUserIdStr” information was missing from the license information field in the response of the information retrieval API. We kindly request your guidance on the reason why the “clientUserIdStr” information is missing when retrieving license information, and the steps to ensure this information is reliably returned. VPPAccoountId:0123456789abcdef0123456789abcdef adamIdStr:521974902 *Some details have been altered from the actual data to protect personal information.
0
0
299
Nov ’25
Reply to Module dependency cycle errors in Xcode 26
Do you have a reduced version of your Swift package that maintains the overall structure and imports that we could look at? Or if there's nothing proprietary in the package and you're willing to share it, that would be helpful too. In either case, please do so in a bug report, and then post the FB number here so I can follow up on it. — Ed Ford,  DTS Engineer
Nov ’25
Unable to find identity (but have private key and certificate)
I'm unable to sign the an example application using xcode and automatically manage signing. The error I'm getting is: CodeSign [...] (in target 'foobar' from project 'foobar') Signing Identity: Apple Development: [xxxx] /usr/bin/codesign --force --sign 4ABB258102FF656E9F597546A49274C28D2B8B3E -o runtime --timestamp=none --generate-entitlement-der [filename] 4ABB258102FF656E9F597546A49274C28D2B8B3E: no identity found Command CodeSign failed with a nonzero exit code However, I am able to see a certificate and a private identity on my keychain: % security find-certificate -aZ | grep -i 4ABB258102FF656E9F597546A49274C28D2B8B3E SHA-1 hash: 4ABB258102FF656E9F597546A49274C28D2B8B3E and % security find-key -s | grep -q 'Apple Development' && echo YES YES what is puzzling is that security does not find an identity: % security find-identity -p codesigning Policy: Code Signing Matching identities 0 identities found Valid identities only 0 valid identities found but XCode claims that everything is working fine.
13
0
1.1k
Nov ’25
Reply to .glassEffect(_in:) crushing on iOS 26 public beta.
Thanks for the detailed feedback. I get it that it's not practical to target pre-release betas. With #available checks, i use that, i even have this package which has various backwards compatible modifiers for new APIs. It follows same concept as your Additional struct. My question on how to handle crashes is not limited to just iOS version variations issues. I was refering to general exceptions and runtime errors that can cause app termination. Thanks.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Nov ’25
Reply to macOS 26.1 Tahoe on ARM: FinderSync extension does not work
When running the currently latest version of macOS (26.1) on a machine with an ARM CPU (I could not reproduce the issue with Intel-based machines), Finder Sync extensions do not work anymore in general. Have you filed a bug on this and, if so, what is the number? Any ideas what I could be missing here? Have you reproduced this on dedicated test machines (where nothing else is installed) or is this only happening on end-user machines? I have a post here that talks about this in more detail. What typically causes this is nesting FinderSync extensions. Also, are you specifically placing contents in /Users/Shared, or was that just a convenient location you selected for testing purposes? That particular directory is not one I'd recommend any developer really use, as the combination of open permission (so everyone can modify it) and a known location (so all sorts of random apps could be interacting with it) means that it isn't really a location you can trust. __ Kevin Elliott DTS Engineer, CoreOS/Hardware
Topic: App & System Services SubTopic: Core OS Tags:
Nov ’25
Reply to Provider entitlements check failed
Here is my mydrv.entitlements file: I don't think that configuration is correct. I describe the correct configuration here, but the key detail is that the entitlement value is an array with a dictionary inside: com.apple.developer.driverkit.transport.pci IOPCIPrimaryMatch 0xFFFFFFFF&0x00000000 That's more complicated than our other development entitlements, but it's the only configuration that would work without requiring any changes to the system. If you're sure the entitlement is correct, then please file a bug on this and post the bug number back here. In the bug, please include: A copy of the full app and embedded DEXT that you're trying to install*. If possible, the sample project you're building with. *Note that, unusually, the build here is actually MORE important than the sample project. For most of these issues all I really need to look at is the signing data of the final product, so starting with a sample project means I have to get the project building in order to test anything. __
Topic: App & System Services SubTopic: Drivers Tags:
Nov ’25
Module dependency cycle errors in Xcode 26
I just updated to Xcode 26 and some of my Swift Packages have been getting strange build errors that I have not been able to resolve. When I try to build my Swift Package in Xcode I get the following error Module dependency cycle: 'UIKit.swiftmodule -> .swiftmodule -> SafariServices.swiftmodule -> UIKit.swiftmodule' It seems like it is related to the change in Xcode 26 that states Swift explicit modules will be the default mode for building all Swift targets. I see that you can disable this with the build setting SWIFT_ENABLE_EXPLICIT_MODULES=NO, but I don't see a way to do this in Package.swift, as you can't include value assignments like this .define(SWIFT_ENABLE_EXPLICIT_MODULES=NO). Our private SPM repos use CI/CD and so we need to be able to build them independently of any use in a project. I would appreciate any help on fixing our Swift Package builds in Xcode 26, thanks!
4
0
317
Nov ’25
Reply to Seeking clarification on macOS URLs with security scope
What is the scope of this new construct? System-wide. This is actually happening in the kernel when in-process incoming paths. The critical syscall is open (and its variants), but the entire kernel will accept these paths. Is this going to be applied to all URLs? Only URLs decoded from a security-scoped bookmark? Only URLs to root directories? What about non-security-scoped bookmarks? What about external drives? What about non-APFS volumes? What about network volumes? Nothing really limits the scope here, but I expect them to be increasingly common. Indeed, I suspect that they're missing in some context is actually a misunderstanding of what's going on. For example, you probably won't see them with fileReferenceURLs, but that's actually because the fileReferenceURL isn't storing a path at all. I'm deploying to the Mac App Store with a sandboxed launch agent. Virtually every system-level API I've encountered behaves differently in this environment. I cannot test in Terminal. I suggested testing in Ter
Topic: App & System Services SubTopic: Core OS Tags:
Nov ’25
Reply to What happens after BGContinuedProcessingTask "expires"?
If I create a BGContinuedProcessingTaskRequest, register it, and then do work within it appropriately reporting progress, and before my task has finished doing all the work it had to do, its expirationHandler triggers... As a small side comment, you don't actually need to do any of the work inside your launchHandler. If you choose, you can just capture the task object (for progress, completion, etc.) and immediately return. See this forum thread for a longer discussion of these issues. does the task later try again? No. The idea is that the API is specifically extending foreground time, so it wouldn't really make sense to resume it later. Or does it lose the execution opportunity until the app is next re-launched to the foreground? In my testing, I never saw my task execute again once expired (which suggests the latter?). Yes, both of points those are correct. I was able to easily force this expiry by starting my task, backgrounding my app, then launching the iOS Camera App. That's actually a little
Nov ’25
Reply to App Extension Network Extension - failed to start, signature check failed
[quote='865186022, deteam444, /thread/805996?answerId=865186022#865186022, /profile/deteam444'] Is it really necessary to disable SIP … [/quote] Not for NE sysexen. See Debugging a Network Extension Provider. [quote='865186022, deteam444, /thread/805996?answerId=865186022#865186022, /profile/deteam444'] Entitlement names for Release build vs Debug would differ if we're planning to re-sign Release build with Developer ID [/quote] Probably not. In Xcode, I recommend that you use automatic code signing for both your Debug and Release build configurations. Things are just easier that way. When you choose Product > Archive to generate an Xcode archive, that’ll be a Release build with Apple Developer signing. The Xcode organiser then re-signs when you export that archive. That works for all situations except Developer ID. Xcode has not yet been educated to about the -systemextension edge case. So, you have to fix the entitlements when you export from your archive. [quote='865186022, deteam444, /thread/8
Nov ’25
Localization not working for App Intents defined inside Swift Package and used in Widget Extension
Hi there, I’m having trouble with localization for App Intents used in a configurable widget when the intents are defined inside a Swift Package. The intents appear correctly in the widget configuration UI and function as expected, but the localized strings are not displayed. Instead, the widget shows the localization keys themselves. Setup Xcode: 26.1 iOS: 26 The App Intents are used for a configurable widget Intent is located in a Swift Package The Widget Extension depends on the package AppIntentsPackage setup: // In the package public struct MySharedIntentsPackage: AppIntentsPackage {} // In the widget extension import AppIntents import SharedAppIntents struct WidgetIntentsPackage: AppIntentsPackage { static var includedPackages: [any AppIntentsPackage.Type] { [MySharedIntentsPackage.self] } } What I’ve tried I tested several configurations separately to see which setup allows localization to work: Localizing inside the Swift Package Placed a Localizable.xcstri
1
0
138
Nov ’25
Reply to XCFramework with Common Third-Party Dependencies Causing Duplicate Symbol Conflicts
What’s the format of ABC? A framework? A mergeable framework? A static framework? A static library? Or something else? If it’s packaged as an XCFramework, you’ll have to look inside that to determine the actual format, because an XCFramework can wrap all of the above. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Nov ’25
StoreKit sandbox purchase and product fetch not working (IAPError: storekit_no_response)
💬 Post Content Hello everyone, I’m currently testing In-App Purchases (auto-renewable subscriptions) for my iOS app, and I’m experiencing an issue where the product information cannot be fetched from StoreKit. ❓ Questions For sandbox testing, is it absolutely necessary to submit a new app version for review (with the in-app purchase included)? Or can I test subscriptions without submitting a new build to App Review? Under what conditions does the error IAPError(code: storekit_no_response, source: app_store, message: StoreKit: Failed to get response from platform.) 🧪 What I’ve Tried • Confirmed that the bundle identifier matches the App Store Connect record • Verified that In-App Purchase capability is enabled in Xcode • Ensured the sandbox tester account is logged in (Settings → App Store) • Removed the StoreKit configuration file to use the sandbox environment • Tried both real device and simulator (same error) • Accepted the Paid Apps Agreement in App Store Connect • Products are created
0
0
120
Nov ’25