missing package product

I have an iOS app that includes a local Swift package. This Swift package contains some .plist files added as resources. The package also depends on an XCFramework. I want to read these .plist files from within the XCFramework. What I’d like to know is: Is this a common or recommended approach—having resources in a Swift package and accessing them from an XCFramework? Previously, I had the .plist files added directly to the main app target, and accessing them from the XCFramework felt straightforward. With the new setup, I’m trying to determine whether this method (placing resources in a Swift package and accessing them from an XCFramework) is considered good practice. For context: I am currently able to read the .plist files from the XCFramework by passing Bundle.module through one of the APIs exposed by the XCFramework.

I want to statically link xcframework as binaryTarget in Swift Package, but it is copied into the product as dynamic when the Xcode build. How to use xcframework in SwiftPackage and statically link it into iOS product? The Package.swift content and the project are: The WebP.xcframework is static: The Xcode Build Product's WebP.framework is dynamic:

Hi, When I try to import the com.apple.unityplugin.core-1.0.3.tgz package into Unity from my Windows development machine I get lots of errors like : LibraryPackageCachecom.apple.unityplugin.core@077039b365c9EditorAppleBuildStep.cs(48,136): error CS0246: The type or namespace name 'PlistDocument' could not be found (are you missing a using directive or an assembly reference?) Is it possible to get around this so I can develop on Windows? Thanks

Apple Transporter.app report this issue: Asset validation failed (90237) The product archive package's signature is invalid. Ensure that it is signed with your 3rd Party Mac Developer Installer certificate. In the post https://developer.apple.com/forums/thread/680438 Quinn “The Eskimo!” reply: For the Mac App Store you need: Apple Development: TTT (or the older Mac Developer: TTT) for day-to-day development 3rd Party Mac Developer Installer: TTT for signing the installer package you submit to App Store Connect 3rd Party Mac Developer Application: TTT for signing the code inside that installer package In https://stackoverflow.com/questions/29039462/which-certificate-should-i-use-to-sign-my-mac-os-x-application Apple Codesigning Certificate Types Mac App Distribution 3rd Party Mac Developer Application: Team Name Used to sign a Mac app before submitting it to the Mac App Store. Mac Installer Distribution 3rd Party Mac Developer Installer: Team Name Used to sign and submit a M

The question about how to notarise an installer package (.pkg) containing a KEXT has come up on a number of threads [1] over the past few weeks. Unfortunately my answers have been less than clear, so I sat down with the notarisation team to fix that. The fundamental question here is the order in which you notarise things. Do you:Sign the KEXT, wrap the KEXT in a signed installer package, then notarise the package, then staple the ticket to the package (option A).Sign the KEXT, then notarise it, then staple the ticket to the KEXT, then wrap the KEXT in a signed installer package, then notarise the package, then staple the ticket to the package (option B).We generally recommend option A, because option B requires multiple round trips to the notarisation servers.For installer packages that don’t contain a KEXT, this is the end of the story. For installer packages that contain a KEXT, there is one extra gotcha. The gotcha, a

I created an IAP and created it as Consumable instead of Non-Consumable so removed it.Now I can't re-add it because of the Product ID being taken.How do I re-use the Product ID?

I've published my app on appstore severel hours ago.however, my app doesn't appear on the search result of appstore. and it doesn't show IAP product list. and also my app failed to fetch Iap product information.the same build worked on sandbox mode. but it doesn't work on store build.How do I solve this? I double checked that iap product is approved.Any advice?

Today when I went to add a package via SPM in Xcode 16.0, the Recently Used Loading... spinner ran and never stopped. I could not add any packages. The packages I am loading are remote and not from my own repo. I did a Refresh Account via the right-click which then shows items in my own hosted repo (for both Bitbucket Cloud and Github), but Recently Used just loads forever and there is no way to add a package. I tried all of the usual cache deleting to no positive outcome. I saw that others had to reinstall Xcode which I am loath to do. I wound up executing defaults delete com.apple.dt.Xcode which of course made me lose all of my settings, but that did correct the problem. At least I thought it did. However, after getting everything reset, it stopped working again with the above issue. In short, I found the issue is with Bitbucket Cloud. If I remove this account from Xcode, SPM works as normal. Add it back (all credentials are 100% fine) and I can no longer use SPM

I use spm manage swift package, now i want my macos app support arm64e,so i add arm64e in Build Srtting -> Architectures. but i got error Could not find module 'SwiftyJSON' for target 'arm64e-apple-macos'; found: arm64-apple-macos, x86_64-apple-macos Apparently, if no limit in Package.swift, SPM will only compile versions for x86 and ARM64 architectures by default. now, how should I configure SPM to compile the arm64e version? thanks

Hi everyone, I’m facing an issue where StoreKit is returning 0 products from the App Store, even though my auto-renewable subscriptions are approved in App Store Connect. When calling queryProductDetails using Flutter’s in_app_purchase package (which uses StoreKit under the hood), StoreKit reports success but returns an empty list. The logs show the following error: IAPError(code: storekit_no_response, source: app_store, message: StoreKit: Failed to get response from platform.) InAppPurchase.isAvailable() returns true, but no product details are received. Already verified: • Subscriptions are approved in App Store Connect • Product identifiers in the app match those in App Store Connect exactly • In-App Purchase capability is enabled in Xcode • Paid Applications Agreement, banking, and tax details are active and complete • Using the latest version of the Flutter in_app_purchase package StoreKit should normally return the list of available products in the production