Search results for

missing package product

51,063 results found

Post

Replies

Boosts

Views

Activity

Reply to Upload Symbols Failed on Xcode 16
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*
Mar ’25
xcodebuild and swift package dependencies
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
4
0
5.6k
Dec ’22
How to exclude RealityKitContent from Swift package for iOS?
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
1
0
1.1k
May ’24
Reply to Preview in Canvas not working due to 'duplication of library code'
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:
Jun ’20
Reply to Pkg installation package uploaded to macstore email prompt ITMS-90296
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
Nov ’24
pkg 签名
我创建了一个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无法检查是否包含恶意软件 提示信息,希望可以得到大家的帮助谢谢,
4
0
899
Jun ’24
Reply to Notarizing my application issues
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:
Dec ’21
How can I sign a package from a privileged helper?
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?
2
0
728
Dec ’19
Reply to Large files in PKGs woes
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
Jun ’23