I've been struggling to understand why the update package feature is failing for a private package I have hosted on our company gitlab server. I am able to add the package to the project just fine, and Xcode downloads the latest version. Any time I make a change and bump the minor version of my package (e.g. 0.0.8 -> 0.0.9), I cannot get Xcode to update to the latest. I have 0.0.8 - next major set for the version rules. Initially adding the package to the project was successful: But when I update my package, tag a new version e.g. 0.0.9, push to our gitlab repo (with tags), then in the project where I added this dependency, right click the package and select Update Package - I get the following error: If I remove the package dependency from the project and add it again, Xcode always correctly grabs the latest version. I have tried removing this package and running File > Packages > Reset Package
Search results for
missing package product
50,283 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
I add local packages via Add Files to project and then add package product in General tab, Frameworks, Libraries section. this way I can add -Wl,-make_mergeable to unsafe flags. Package compilation itself works fine, but main app target fails ld: -make_mergeable can only be used when creating a dynamic library. filed feedback to apple about it https://feedbackassistant.apple.com/feedback/13547751.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
I was wondering if there is any npm module for tvml js which we can use to import functions like: 'userDefaults', 'getAdvetisementId' for linting purposes?Thanks
Hello, I am a beginner with MacOS. I am trying to compile a program that builds using Xcode. Right now I have Xcode 12.2 on Catalina 10.15.5 . My build runs up to a point where I have : 'CoreServices/CoreServices.h' file not found. From my readings, I think that this file should be in a headers package, probably macOS_SDK_headers_for_macOS_10.15.pkg or something like that. I have reinstalled Xcode 12.2 (a .xip) and also the command lines tools for Xcode 12.2 ( a .dmg ). After doing these installs, I still do not find the missing headers or even the pkg file that would contain them. Can anybody help me with installing the missing headers ? How do I get the SDK headers to complete my compilation ? Thank you Gilbert
I’d like to get a better understanding of your requirements here. Here’s what I think is going on: You have a Mac product that you distribute directly (as opposed to on the Mac App Store). Your users download that product from your website. At the point of download, you want to customise the product for each user. Am I right so far? If so, I have a couple of follow-up questions: Roughly how many users are we talking about here? Tens? Hundreds? Thousands? How is your product currently packaged. You mentioned an disk image, so I’m presuming that’s the outermost container. What’s on that disk image? Just your app? Is there more nested containers, like an installer package? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
Code Signing
SubTopic:
General
I'm in the process of converting my local frameworks to local Swift packages. Things are (mostly) working well but I'm struggling with one of the packages: Package MyKit is used by an iOS and a tvOS app. It includes a storyboard for each platform. What is the most appropriate way to describe this in Package.swift? Xcode complains about iOS storyboards not being supported on tvOS so I moved them to their own targets, like this: let package = Package( name: MyKit, defaultLocalization: en, platforms: [ .tvOS(.v13) ], products: [ // Products define the executables and libraries a package produces, and make them visible to other packages. .library( name: MyKit, targets: [MyKit]), ], dependencies: [ // Dependencies declare other packages that this package depends on. // .package(url: /* package url */, from: 1.0.0), ], targets: [ // Targets are the basic building blocks of a package. A targe
Any suggestions as to what I'm missing or doing wrong? You are signing your installer package as code, which is not right. Installer packages must be signed by installer tools using a Developer ID Installer code signing identity. Packaging Mac Software for Distribution shows the basics. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
Code Signing
SubTopic:
Notarization
Tags:
I looked into the Info.plist file and it seems that it is the same before and after the pack md5 ./Build-Mac-EP-New/SBSimulatorPackage/build/SafeBreach EPS.app/Contents/Info.plist ./Build-Mac-EP-New/SafeBreachMenuBar/Build/Products/Release/SafeBreach EPS.app/Contents/Info.plist MD5 (./Build-Mac-EP-New/SBSimulatorPackage/build/SafeBreach EPS.app/Contents/Info.plist) = e9be84f77bf23176a8d337fbce83aeb2 MD5 (./Build-Mac-EP-New/SafeBreachMenuBar/Build/Products/Release/SafeBreach EPS.app/Contents/Info.plist) = e9be84f77bf23176a8d337fbce83aeb2 I'm using Packages (http://s.sudre.free.fr/Software/Packages/about.html) to create the final .pkg file.
Topic:
Code Signing
SubTopic:
Notarization
Tags:
Same. MacBook M1 Pro. All SPM packages are missing from the project folder, and same error as above. Downloading the previous version :-(
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
I try to upload my app on itunestore some erroe occur.ERROR ITMS-90529: Invalid package. Applications built with sdk 9.0 or later must be packaged as proper IPA files.
Hello,I successfully codesigned app bundle and it was accepted by notary service. Then I created a package using pkgbuild/productbuild commands and codesigned it using Installer identity. The installer works fine.I'm now trying to notarize the .pkg file but no success. It always returns invalid status with just one error:severityerrorcodenullpath<package internal path>.pkg Contents/Payload/Contents/MacOS/<executable>messageThe signature of the binary is invalid.docUrlnullarchitecturex86_64(I replaced real paths above).However, when the application is installed, both codesign and spctl return OK status. I use XCode 10.1 on macos 10.14.2.Any suggestions how to satisfy notary service?
I’m new to Mac packaging, and am confused by the multi-part signing and packaging process. I have built an app, using third party software, that I would like to upload to the Mac store for trial/testing purposes. I have joined the Apple Developers Programme, but am unsure whether I need to invest in third-party certification (e.g. Verisign) or can self-certify my app package. I would be obliged if someone would outline the sequence of steps that I need to follow to create a package that can be offered to users, and confirm whether my AD License is sufficient for me to follow same. Thanks in advance for any advice. Regards, L
I'm building a custom macOS installer for my software, primarily using the builtin tools of codesign, pkgbuild, productbuild and xcrun. My product consist of a list of plugins and a CEP extension for the Adobe After Effect app. All of my bundles and binaries are properly signed using a trusted Apple Developer certificate I've generated, of type Developer ID Application. My installer is a distribution pkg, and has this structure(expanding it using pkgutil --expand): SceneTools-3.4.4-osx-installer ├── Distribution ├── miscellaneous.pkg ├── plugins.aftereffects2022.pkg ├── plugins.aftereffects2023.pkg ├── plugins.aftereffects2024.pkg ├── plugins.aftereffects2025.pkg ├── preinstall.pkg ├── Resources ├── scenebuilder.pkg └── uninstaller.pkg Each child pkg would install parts of my product in different locations in the target macOS disk(this is why I'm using that kind of style of building the custom installer). Signing each and every bundle or
Topic:
Code Signing
SubTopic:
Notarization
I looked for any posts that indicate whether one can generate hashes (SHA256 or MD5) for packages in particular Photo and Photos Libraries but did not find any. Can hashes be generated for such packages?
Could you take a look and see if anything is packaged incorrectly? I can’t see anything obviously wrong that. I took a quick general look and I also run it through the steps described in Testing a Notarised Product (using macOS 13.0 in the VM) and it worked. If you send this dummy package to your customer, do they have the same problem they have with your real package? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
Code Signing
SubTopic:
General
Tags: