missing package product

Hi. I was wondering if anyone else has the same issue with Swift packages that include binary targets. Let's say that some static frameworks or resources are stored in git lfs, and they are a part of the Swift Package (binary targets). On the other side, in a project, you would like to add that package (or resolve it) through Xcode. By normal add swift package flow from the URL, a process fails with terminated(128). I did some digging, and here is what I get: Downloading X.a (715 KB) Error downloading object: X.a (2f7ae21): Smudge error: Error downloading X.a (2f7ae213e49b8b079b584b007d2cc0ab0fb0d581a64f8e4f800b1d2807a86f62): error transferring 2f7ae213e49b8b079b584b007d2cc0ab0fb0d581a64f8e4f800b1d2807a86f62: [0] remote missing object 2f7ae213e49b8b079b584b007d2cc0ab0fb0d581a64f8e4f800b1d2807a86f62 Errors logged to .../checkouts/X/.git/lfs/logs/20210323T161533.36114.log Use `git lfs logs last` to view the log. error: external filter 'git-lfs filter-process' failed

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

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 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.

I believe that this is related to the post https://developer.apple.com/forums/thread/790880. I essentially have the same problem that they did. I submit my Distribution PKG for notarization but the notarization fails and when I attempt to install the PKG user the UI I get a External component packages (3) trustLevel=0 (trust evaluation failed; treating as invalid due to higher trust level for parent product archive) However if I install using sudo installer -verboseR -pkg ConcealDistribution.pkg -target / everything works as expected. The difference between me and the other post is that when I expand my PKG using pkgutil --expand I do not have a Resources folder within my top level distribution. Instead my structure looks like ConcealDistribution ├── Distribution ├── ConcealConnect.pkg ├── ConcealBrowse.pkg └── ConcealUpdate.pkg The specific notary service errors I receive are as follows { logFormatVersion: 1, jobId: 7e30e3fd-1739-497c-a02e-64fbe357221d, s

I'm trying to use Swift Package Manager's binaryTarget to include the Stripe xcframework available here https://github.com/stripe/stripe-ios/releases/tag/v19.3.0. The package manager doesn't complain, and lets me link to it, but I can't import it in my files. I've made a sample repo to show it here https://github.com/martyu/StripePackageTest. Am I missing something?

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?