missing package product

If Apple is hosting the content they will only download a particular package for a particular IAP product that is purchased. Therefore you will need 100 products and the user will pick the product and buy a productIdentifier. If you host the content you can let the user buy a consumable IAP and then swap that IAP for a particular package to download.

I was able to fix it by separating the xcframework to its own Swift Package let package = Package( name: TheLibrary, products: [ .library(name: TheLibrary, targets: [TheLibrary]), ], dependencies: [], targets: [ .binaryTarget(name: TheLibrary, path: Sources/TheLibrary.xcframework) ] ) and then including as a dependency in main project. let package = Package( name: MainProject, platforms: [.iOS(.v11), .macOS(.v10_15)], products: [ .library(name: MainProject, targets: [MainProject]) ], dependencies: [ .package(url: ../TheLibrary, from: 1.0.0) ], targets: [ .target( name: MainProject, dependencies: [ TheLibrary ] ) ] ) I hope it helps!

Add platforms information in Package.swift under Packages/RealityKitContent folder may help. let package = Package( name: RealityKitContent, platforms: [ .visionOS(2.0) ], products: [ ....

I have had the same problem with displaying previews in Swift packages. My project architecture is: UIComponents (local package) - AppPackage (local package) - App What I did was to add .dynamic parameter to .library declaration in both packages. Now I can see previews for all SwiftUI files, both in UIComponents and AppPackage. swift products: [ .library( name: UIComponents, type: .dynamic, /* added parameter */ targets: [UIComponents]) ], swift products: [ .library( name: AppPackage, type: .dynamic, /* added parameter */ targets: [AppPackage]) ], dependencies: [ .package(path: ../UIComponents) ],

Create a local SPM in your project Add all your dependency packages into the Package file e.x. import PackageDescription let package = Package( name: Dependencies, products: [ .library( name: Dependencies, targets: [Dependencies]), ], dependencies: [ .package(url: https://package_url.git, exact: 0.0.1), ], targets: [ .target( name: Dependencies, dependencies: [ .product(name: package_name, package: package_name), ] ), .testTarget( name: DependenciesTests, dependencies: [Dependencies]), ] ) Go to target -> General -> Frameworks, Libraries, and Embedded Content add Dependencies close Xcode and apply this commit to all branches reopen Xcode

Hi, They have provided us some scripts and templates, which performs code sign and product sign, just we have to provide all the binaries and executables to them. since I don't have certificates so can't sign project from Xcode. As per my understanding we have to sign .pkg, .app and all the library executables (.dylib ). when i verify my signed .app it shows me message app: a sealed resource is missing or invalid Used some third party framework in project and there are some symlink in that, is that causing the issue ? do I need to sign framework as well if yes then how ? or is there any step I am missing in signing process

Ok, so I managed to fix this by adding dependency to my target. Here's the update Package.swift // swift-tools-version: 5.10 // The swift-tools-version declares the minimum version of Swift required to build this package. let package = Package( name: MyPackage, platforms: [.iOS(.v16), .macCatalyst(.v16), .macOS(.v14)], products: [.library(name: MyPackage, targets: [MyPackage]),], dependencies: [ .package(path: ../external-package) ], targets: [ .target( name: MyPackage, dependencies: [ 👉❗️ .product(name: ExternalPackageName, package: external-package) ], path: Sources ), .testTarget(name: MyPackageTests, dependencies: [MyPackage]), ] )

I'm still not sure about the reason of the issue, but I discovered that you can't include binaries in a Swift Package.This is the correct Package.swift:// swift-tools-version:5.1 // The swift-tools-version declares the minimum version of Swift required to build this package. import PackageDescription let package = Package( name: MyLibrary, products: [ // Products define the executables and libraries produced by a package, and make them visible to other packages. .library( name: MyLibrary, targets: [MyLibrary]), ], dependencies: [], targets: [ // Targets are the basic building blocks of a package. A target can define a module or a test suite. // Targets can depend on other targets in this package, and on products in packages which this package depends on. .target( name: MyLibrary, dependencies: [], path: Sources/MyLibrary, linkerSettings: [ .linkedFramework(Security), .linkedLibrary(pthread), .linkedLibr

I have notarised my app in this way Product > Archive > Distribute App > Deverloper ID > Upload then after some time I got a notification saying your app got notarised and ready to distribute. I then exported app and double clicked it and it works really well. But when I generate .pkg file then trying to install, it says unidentified developer What should I do now? is there any step I am missing. Your help is much appreciated. Many Thanks, Vishwanath

Hi, They have provided us some scripts and templates, which performs code sign and product sign, just we have to provide all the binaries and executables to them. since I don't have certificates so can't sign project from Xcode. As per my understanding we have to sign .pkg, .app and all the library executables (.dylib ). when i verify my signed .app it shows me message app: a sealed resource is missing or invalid Used some third party framework in project and there are some symlink in that, is that causing the issue ? do I need to sign framework as well if yes then how ? or is there any step I am missing in signing process.

Same here with beta 6 I delete the package in Product -> Package dependencies to run the preview (and add again when building).. Does anyone have update regarding this issue ?

The Xcode 9.x is required for compiling becuase it still offers the option to bundle the 32-bit version of the app, that is required by some of the customers.You have customers that still support 10.6? Wow.Our customers will embed this application in their product, and when there is a need to run a diagnostic on the device, will simply run automically this app.OK, that complicates matters. What you’re hitting here is a Gatekeeper check. One fundamental feature of Gatekeeper is that it applies to the thing that the user downloads. If your product is embedded within another product, the Gatekeeper check will be applied to that product, and thus it’s the structure of that product that matters.For example, let’s say your customers create an installer package that embeds your product. They’ll want to notarise and staple that package before shipping it to their customers. When one of their users installs that package, the Gatekeeper ch