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.

I'm building a Unity application and attempting sign, package, and notarize the app for distribution outside of the App Store. I've joined the Developer Program, and created both Application and Installer Developer Certificates and installed them to Keychain. Using a command line build pipeline, I am able to use productbuild, productsign, and xcrun altool to generate my pkg and notarize it. Notarization is successful, and I receive Status: success and Status Message: Package Approved. Then I staple the notarization ticket to my package. However, when running the installer, I'm met with an error saying MyPackage.pkg can't be installed because its digital signature is not trusted. If I generate the same installer without notarizing it, I have no problem running it and it installs successfully if I alter my security settings to allow apps from unknown developers. Does anyone here have experience packaging Unity apps for Mac? What am I missing here...? All the

I keep getting a Xcode Previews error in Xcode 12 from a package that imports other packages. As soon as I remove the dependency I'm able to see the SwiftUI preview. I'm only able to use previews in packages that have no dependencies The error I get is: LoadingError: failed to load library at path...Library not loaded then it point to the dependency that it could not load in the current package. How can I access Xcode Previews from a package that depends on other packages?

I am working on an iOS project using Xcode 16.0 that leverages multiple Swift packages. Among these, I have a Shared Package that contains reusable code and is linked to several top-level feature packages (e.g., VideoPlayer, VideoEditor, etc.). The Shared Package includes a Swift Package Manager plugin for linting code standards, which is designed to execute during its own build process. However, when building a top-level package (e.g., VideoPlayer), the Shared Package is also built as part of the dependency graph. During this process, the linting plugin in the Shared Package is executed unnecessarily, even though the intent is to only build the Shared Package's code. This behavior results in a significant increase in build times for the top-level packages, as the linting plugin is executed every time the Shared Package is built indirectly. Key Details: Xcode Version: 16.0 Swift Package Manager: Used fo

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?

May it be accomplished that an iMessage App may be packaged/integrated with a company's standard product in the Apple Store, such that on Product Version (X.Y.Z)+, the stickers are automatically installed with the mainstream offering?If the answer to the previous question is yes, would the combined package be subjected to new rules about the maximum bundle size?

I decided to add a package to my existing Xcode project. Unfortunately there is a lot of information how to create a package and just a few lines how to use/add one. So if anyone knows how to add it, what to do and not to destroy my current project, please share your experience.