“missing package product”

I have lost key for android project so decided change the package for android. As i have changed the package name for android, change it for Apple as well. But i now i cant change id now. And i have decided to add a account under compnay name and then add package to it. If i already have a old version in another account, will this affect my new account and new app approval.

In sandbox testing, I was able to get auto-renewing subscription to work, but decided to switch to one-time in-app purchase. I've read many how-to's, but I'm missing something. My app has Bundle ID com.myname.id1 and IAP capability added. The IAP has Product ID com.myname.id2. My agreements are up-to-date (auto-renewing subscription worked). The In-App Purchases screen lists my IAP under Drafts (1); is this expected? [SKPaymentQueue canMakePayments] returns true. [[SKProductsRequest alloc] initWithProductIdentifiers:set] (where set contains com.myname.id2) responds to [request start]. In the delegate, NSArray *product = response.products comes back empty. Does the IAP have its own Bundle ID? What am I doing wrong? What have I not told you that's important? I've been stuck for a few days on this. Thanks!

Hi, I'm writing a custom step to our installer using IntallerPlugins.framework and class InstallerPane. Is it possible to get path and name of the pkg file from InstallerPane object? I tried solution from this page but it seems right now the delegate is not set. http://s.sudre.free.fr/Stuff/Installer/Installer_Plugins/InstallerPlugins-FAQ002.html. Also there's no appropriate tag for this framework.

Hello, I have an Xcode project (not a workspace), that depends upon a swift package found on GitHub. You can find the PR here that demonstrates the problem. https://github.com/bolsinga/MissingArt/pull/2 My project has a Swift Package dependency. It's a macOS target. If I Cmd-B in Xcode it will build and run just fine (finding the package and building it too). If I xcodebuild -verbose from the command line in CI, it will fail. The problem is that when the application files compile and import the module found in the Swift Package, the module is not found. If this were ObjC, I'd know that the search path was not found. I do not see anything about my module on the link line. I have followed the instructions about adding a Swift Package Mgr dependency, and it works locally. I'm sure that I'm missing one small thing; I'm not sure if xcodebuild with no options (thus getting the default behavior) is the proper thing to do. Any ideas? Thank you, -- Greg

I've created an app for visionOS that uses a custom package that includes RealityKitContent as well (as a sub-package). I now want to turn this app into a multi-platform app that also supports iOS. When I try to compile the app for this platform, I get this error message: Building for 'iphoneos', but realitytool only supports [xros, xrsimulator] Thus, I want to exclude the RealityKitContent from my package for iOS, but I don't really know how. The Apple docs are pretty complicated, and ChatGPT did only give me solutions that did not work at all. I also tried to post this on the Swift forum, but no-one could help me there either - so I am trying my luck here. Here is my Package.swift file: // swift-tools-version: 5.10 import PackageDescription let package = Package( name: Overlays, platforms: [ .iOS(.v17), .visionOS(.v1) ], products: [ .library( name: Overlays, targets: [Overlays]), ], dependencies: [ .package( path: ../BackendServices ), .package

Hello, I'm Software Engineer and my work is developing SDK. I'm on developing 1 Swift Package for general logic and 1 SDK (Xcode Framework Project) for business logic. (SDK depends on Swift Package) Until now, I merge them with @_implementationOnly. And I want to migrate to MAKE_MERGEABLE. Can I mark Swift Package Dependency as MAKE_MERGEABLE on SDK Xcode Framework Project? Or can I mark Swift Package MAKE_MERGEABLE on Package.swift? Or I can't make Swift Package MAKE_MERGEABLE?

我创建了一个developer id instanller 证书，并且安装在自己电脑上，我使用productbuild --component xx.app /Applications --sign Developer ID Installer: --product xx.app/Contents/Info.plist ST.pkg签名并生成pkg，使用 spctl -a -v --type install ST.pkg 去验证签名的时候，出现rejected source=Unnotarized Developer ID，我不知道哪里有问题，将pkg安装到其他电脑也会出现pkg无法打开，apple无法检查是否包含恶意软件 提示信息，希望可以得到大家的帮助谢谢，

I need to figure out how to go about signing a package from a privileged helper. One of our products can create packages and can sign the packages. It's currently using AuthorizationExecuteWithPrivileges, which has been deprecated since 10.7, to obtain root access, and starting an external task to run the /usr/bin/productsign utility. We are changing it to use a privileged helper instead, however, I tried running the /usr/bin/productsign utility from the privileged helper, but since that prompts for credentials to access the keychain, it just hangs since the privileged helper doesn't seem to have access to the UI. Does anyone know of a way to sign a package using an API function instead of the productsign utility, or have any ideas how to prevent to prevent the productsign utility from prompting when run from the privilged helper, or know of a way that the privileged helper could allow the productsign utility to prompt the user for credentials?

Trying to utilize the new OpenAPI Generator, but after following all of the steps exactly as stated in the video, I get the following errors: - The package product 'SwiftSyntax' requires minimum platform version 13.0 for the iOS platform, but this target supports 12.0 - The package product 'SwiftSyntaxBuilder' requires minimum platform version 13.0 for the iOS platform, but this target supports 12.0 - The package product 'SwiftFormat' requires minimum platform version 13.0 for the iOS platform, but this target supports 12.0 - The package product 'SwiftFormatConfiguration' requires minimum platform version 13.0 for the iOS platform, but this target supports 12.0 under both _OpenAPIGeneratorCore and swift-openapi-generator I've seen other things online where people have had similar issues, but the fixes haven't been particularly relevant that I could tell.