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
Search results for
missing package product
50,339 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
This is a known issue related to Xcode previews building all package products dynamically. You may be able to work around it by making the affected products explicitly static, except for the one you are trying to preview, using the type argument - https://developer.apple.com/documentation/swift_packages/product/2878196-library. For example, in this case you could make HAP an explicitly static product. Since the diagnostic mentions more targets being affected, this workaround might unfortunately be an iterative process.
Topic:
UI Frameworks
SubTopic:
SwiftUI
Tags:
我创建了一个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无法检查是否包含恶意软件 提示信息,希望可以得到大家的帮助谢谢,
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
What an awful, awful experience. My package dependencies were fine a few days ago, and will I fired it up today I encountered this error 5. Just lost about two hours trying to figure it out. Thanks for the solution @kironet. I'm going to bill Apple for my lost two hours. How pointless.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
I tried using a third-party app (Pacivist) to open the app in pkg, nd export the app locally,then followed your instructions to perform the following actions: 1、 Run codesign against the results app to confirm that its signature is valid: % codesign --verify -vvv /path/to/your.app The results obtained: PS:I noticed an error message IFlytek heard. app: a sealed resource is missing or invalid File missing:/Users/pploo2/Desktop/icon/1/iFlytek heard. app/Contents/Resources/tj_S1/_MACOSX/ node_modules I don't know if this is the key to the problem ITMS-90926. 2. Run codesign again to check that you have App Sandbox enabled: % codesign --display --entitlements - /path/to/your.app The results obtained: You can see that there is sandbox=true here Now back to the first step, I performed operations on the app before packaging it as pkg and found that there were no missing related issues
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
I'm using Packages … to create the final .pkg file. Hmmm. If you package your app using Apple tools and then unpackage it the same way (Pacifist ftw!), do you still see the problem? For instructions on how to package an app using Apple tools, see Signing a Mac Product For Distribution. If the Apple tools work, you have a choice: You can either continue using Apple tools. You can escalate this with your third-party third-party tool provider. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
Code Signing
SubTopic:
Notarization
Tags:
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?
I have the same issue, did you resolve this? iTMSTransporter could not generate an itmsp: could not find any packages bundle within the swinfo description (product-metadata.packages) The build will otherwise install succefully.
Topic:
App Store Distribution & Marketing
SubTopic:
TestFlight
Tags:
When I try to package my IPA for the production version What tool are you using for that? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Tags:
Somehow the missing webhook for one of the packages just showed up one day. I'm not sure what triggered it, or if it was just a delay of sorts, but this setup is working now.
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud
Tags:
Sorry if I missed it - did you confirm to move from development/sandbox provisioning to release/production/store provisioning?
Topic:
Code Signing
SubTopic:
General
Tags:
Ok I figured it out. I still haven't checked the AppStore process but at least all checks pass now It's MUCH more complex than product build, but product build itself is buggy. So. Prepare your .app with HUUUGE file (> 8Gb). Sign it correctly, do everything as usual! pkgbuild --identifier --large-payload --compression latest --min-os-version 12.4 --root .pkg Make the following 'Distribution' file MY com.XXX.pkg productbuild --sign Signer --distribution ./Distribution --package-path ~ Final.pkg Something like that Your package definitely will be 1) compressed fine 2) smaller 3) with super large file Feed the stuff to the Transporter. Don't forget to adjust Distribution with correct version, id's etc. Have fun! I certainly had it
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Easy Fix Locate the missing.framework in your Flutter app *Missing is the name of missing DSYM find ~/Library/Developer/Xcode/DerivedData -name missingframework | grep -v SourcePackages Generate the dSYM file manually xcrun dsymutil -o ~/Desktop/missing.framework.dSYM /path/to/found/missing.framework/missing Find your recent archive Go to Xcode > Window > Organizer Right-click on your most recent archive and select Show in Finder Right-click on the .xcarchive file and select Show Package Contents Navigate to dSYMs folder Copy the generated dSYM** Copy the generated Razorpay.framework.dSYM file from your Desktop Paste it into the dSYMs folder in your .xcarchive package Retry uploading or validating*
Topic:
App Store Distribution & Marketing
SubTopic:
TestFlight
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?
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