Search results for

“missing package product”

53,787 results found

Post

Replies

Boosts

Views

Activity

Reply to Staple notarization ticket to a daemon
As you've noticed stapling is not supported for .zip packages (there is nowhere to put ticket), this is correct. macOS will indeed download and check notarization ticket for your binary upon first launch. But if there is no internet connection, this will fail and you will get nasty Gatekeeper alert. What you can do — create a package that will install you daemon (and probably launchd plist and some bootstrap script I guess) with pkgbuild and productbuild. Product package can be signed, notarized and stapled.
Topic: Code Signing SubTopic: General Tags:
Jun ’20
Problem with swift package manager caching and binary package
I've setup my Xcode project to use a binary package, for which the manifest is stored in the private git repository. The dependency tracking is set to branch -- it just fetches the manifest from master branch of the repository. It seems, that after initial fetching Xcode or spm caches the commit hash used to fetch the manifest. If I push an update of Package.swift (i.e. containing updated artifact checksum) this change is not refreshed in the project (i.e. after resetting package cache it complains about the checksum mismatch between the actual binary artifact and the manifest). At the same time if I manually clone the repository I see valid checksum in the manifest. I've tried to use all 3 options in Xcode (i.e. reset package cache, resolve package versions, update to newest version). None of them solves the problem. It seems that to reset the cache I need to remove the package from the project and add it again. I'm looking for an elegant way to refresh the manife
1
0
2.2k
Sep ’22
Pkg installation package uploaded to macstore email prompt ITMS-90296
Project Background: I developed a Mac project using Electron and VSCode Successfully uploaded the packaged pkg using Transporter, However, I will receive an email informing me that there are some issues with the project: ITMS-90296: App sandbox not enabled - The following executors must include the 'com. apple. security. app sandbox' entitlement with a Boolean value of true in the entitlement property list: [[com. electron. iflyrecclient. pkg/Payload/iFlytek Listen. app/Contents/MacOS/iFlytek Listen]] ITMS-90886: 'Cannot be used with TestFlight because the signature for the bundle at' iFlytek hears. app 'is missing an application identifier but has an application identifier in the provisioning profile for the bundle.' Bundles with application identifiers in the provisioning profile are expected to have the same identifier signed into the bundle in order to be eligible for TestFlight.' Here is my packaging process: Generate an app using the electron packager
2
0
729
Nov ’24
How do i expand payload of 3rd party package?
Hi, I'm trying to notarise package file of our product. Notarization is success with some warnings on 3rd party package file. I see two executables in the 3rd party package file is not code signed properly. I need to expand, sign those binaries and flatten it again and include into our package file. I'm able to expand the 3rd party package file using the below command: pkgutil --expand directory name Now i'm able to see files of the above package file. But how do i expand pay-load files?
1
0
1.3k
Oct ’19
Reply to Xcode 11 how to work with .crash files?
Not sure how viewing crashes in Xcode is supposed to work either. Wasn't able to find anything useful when clicking Open in Project.For me, a couple of times I noticed vital information was missing when viewing the crash in Xcode (missing method calls on the stack but they were in the .crash log). So I right-clicked on the crash in the list on the left and choose Show in Finder which reveals a package with .xccrashpoint in Finder. I then right clicked that .xccrashpoint package in Finder and choose Show Package Contents and then dug through subfolders until I got to the Log folder with the .crash files in it. Then I just opened the .crash in Console. Reading the .crash in Console was a lot more useful. Was able to determine what caused the app to crash and was able to fix it in an update.
Mar ’20
Reply to Having a hard time notarizing a pkg.
It looks like you’re signing your package as code. That won’t work. You need to sign it as a package. My Signing a Mac Product For Distribution - https://forums.developer.apple.com/thread/128166 post has the relevant instructions. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @apple.com
Topic: Code Signing SubTopic: Notarization Tags:
Aug ’20
Failed to sign PKG Installer
I created PKG installer in command line (see below, command's output is in italic). Installer is opening on my MBP, but after uploading on server and download by link, macOS shows TestApp.app.2.0(32).pkg” can’t be opened because Apple cannot check it for malicious software. TestApp.app is application signed by Developer ID Application certificate and notarised with Xcode. Check TestApp.app signing: codesign --verify --verbose TestApp.app TestApp.app: valid on disk TestApp.app: satisfies its Designated Requirement spctl --assess --verbose TestApp.app TestApp.app: accepted source=Notarized Developer ID Build package component pkgbuild --identifier --version '2.0(32)' --sign 'Developer ID Installer: ….’ --install-location /Applications --component TestApp.app component.pkg pkgbuild: Adding component at …../Create PKG/TestApp.app pkgbuild: Using timestamp authority for signature pkgbuild: Signing package with identity Developer ID Installer: …” from keychain …./Librar
1
0
1.6k
Oct ’21
How to depend on a non-macOS external package in macros
Hello everyone, I am trying to create a macro that depends on an external package to abstract some of the packages logic. The point is that the dependency does not support macOS which results in a build failure when trying to build the macro. Since macOS 10.15 is required for creating macros, any thing can be done to get it to work? Here is a sample to what I'm trying to do import PackageDescription import CompilerPluginSupport let package = Package( name: Stringify, platforms: [ .macOS(.v10_15), .iOS(.v13), .tvOS(.v13), .watchOS(.v6), .macCatalyst(.v13) ], products: [ .library( name: Stringify, targets: [Stringify] ), .executable( name: StringifyClient, targets: [StringifyClient] ), ], dependencies: [ .package(url: https://github.com/apple/swift-syntax.git, from: 509.0.0), .package(url: https://github.com/MyDependency, from: 1.0.0), ], targets: [ .target( name: Stringify, dependencies: [StringifyMacros] ), .executableTarget( name: StringifyClient
1
0
429
Jul ’24
Reply to No such module 'FirebaseFirestore'
Interesting, I am just learning iOS, and during my courses I used Firebase but installed via CocoaPods, this time I added the package via add packages and when I want to use the Firestore DB to add in the app delegate also get this error, wonder what the issue could be. So the authentication features all work, but the Firestore seems to be missing for some reason. Will try and re install it later, but updating the package did not help. I am on Xcode 14.2 (14C18)
Apr ’23
Storekit2 Fetch Products
I have more than 230 in app products which is Consumable, Non-Consumable & Auto Renewable subscription, So while Initialise Inapp products in storekit2 let productIds = [...your 300 identifiers...] let products = try await Product.products(for: productIds) I am getting repose only few products few missing in TestFlight build, So how to resolve this issue, it happen in only TestFlight or App Store its working?
0
0
110
May ’25
Reply to Staple notarization ticket to a daemon
As you've noticed stapling is not supported for .zip packages (there is nowhere to put ticket), this is correct. macOS will indeed download and check notarization ticket for your binary upon first launch. But if there is no internet connection, this will fail and you will get nasty Gatekeeper alert. What you can do — create a package that will install you daemon (and probably launchd plist and some bootstrap script I guess) with pkgbuild and productbuild. Product package can be signed, notarized and stapled.
Topic: Code Signing SubTopic: General Tags:
Replies
Boosts
Views
Activity
Jun ’20
Problem with swift package manager caching and binary package
I've setup my Xcode project to use a binary package, for which the manifest is stored in the private git repository. The dependency tracking is set to branch -- it just fetches the manifest from master branch of the repository. It seems, that after initial fetching Xcode or spm caches the commit hash used to fetch the manifest. If I push an update of Package.swift (i.e. containing updated artifact checksum) this change is not refreshed in the project (i.e. after resetting package cache it complains about the checksum mismatch between the actual binary artifact and the manifest). At the same time if I manually clone the repository I see valid checksum in the manifest. I've tried to use all 3 options in Xcode (i.e. reset package cache, resolve package versions, update to newest version). None of them solves the problem. It seems that to reset the cache I need to remove the package from the project and add it again. I'm looking for an elegant way to refresh the manife
Replies
1
Boosts
0
Views
2.2k
Activity
Sep ’22
Pkg installation package uploaded to macstore email prompt ITMS-90296
Project Background: I developed a Mac project using Electron and VSCode Successfully uploaded the packaged pkg using Transporter, However, I will receive an email informing me that there are some issues with the project: ITMS-90296: App sandbox not enabled - The following executors must include the 'com. apple. security. app sandbox' entitlement with a Boolean value of true in the entitlement property list: [[com. electron. iflyrecclient. pkg/Payload/iFlytek Listen. app/Contents/MacOS/iFlytek Listen]] ITMS-90886: 'Cannot be used with TestFlight because the signature for the bundle at' iFlytek hears. app 'is missing an application identifier but has an application identifier in the provisioning profile for the bundle.' Bundles with application identifiers in the provisioning profile are expected to have the same identifier signed into the bundle in order to be eligible for TestFlight.' Here is my packaging process: Generate an app using the electron packager
Replies
2
Boosts
0
Views
729
Activity
Nov ’24
How do i expand payload of 3rd party package?
Hi, I'm trying to notarise package file of our product. Notarization is success with some warnings on 3rd party package file. I see two executables in the 3rd party package file is not code signed properly. I need to expand, sign those binaries and flatten it again and include into our package file. I'm able to expand the 3rd party package file using the below command: pkgutil --expand directory name Now i'm able to see files of the above package file. But how do i expand pay-load files?
Replies
1
Boosts
0
Views
1.3k
Activity
Oct ’19
Reply to Swift Package can be MAKE_MERGEABLE?
This is not a solution. it failed at the build time with error: The package product 'MyPackage' cannot be used as a dependency of this target because it uses unsafe build flags.
Replies
Boosts
Views
Activity
Dec ’23
Reply to Error while generating a DocC based documentation for a Swift Package
This sounds like it may be a general Swift Package Manager dependency resolution issue. If you see the same error when you try to build from the command-line using: $ swift build --product InternalFramework then I would recommend either opening an issue on the open-source Swift Package Manager repository or filing a Feedback.
Replies
Boosts
Views
Activity
Jul ’22
Reply to Xcode 11 how to work with .crash files?
Not sure how viewing crashes in Xcode is supposed to work either. Wasn't able to find anything useful when clicking Open in Project.For me, a couple of times I noticed vital information was missing when viewing the crash in Xcode (missing method calls on the stack but they were in the .crash log). So I right-clicked on the crash in the list on the left and choose Show in Finder which reveals a package with .xccrashpoint in Finder. I then right clicked that .xccrashpoint package in Finder and choose Show Package Contents and then dug through subfolders until I got to the Log folder with the .crash files in it. Then I just opened the .crash in Console. Reading the .crash in Console was a lot more useful. Was able to determine what caused the app to crash and was able to fix it in an update.
Replies
Boosts
Views
Activity
Mar ’20
Attestation Swift Package for servers?
Apple has provided a number of Swift Packages for backend development, including some new tools for wallet passes! Is there anything like this for attestation and device check capabilities for a swift-on-server product to consume? If not, consider this a placeholder for a future feedback request.
Replies
1
Boosts
0
Views
116
Activity
2w
Reply to Testflight down
My issue has been solved. A new installed package make the microphone on as default and I have to add NSMicrophoneUsageDescription in my info.plist. Some mails from app store has pointed out the problem but I missed them.
Replies
Boosts
Views
Activity
Oct ’24
Reply to Having a hard time notarizing a pkg.
It looks like you’re signing your package as code. That won’t work. You need to sign it as a package. My Signing a Mac Product For Distribution - https://forums.developer.apple.com/thread/128166 post has the relevant instructions. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @apple.com
Topic: Code Signing SubTopic: Notarization Tags:
Replies
Boosts
Views
Activity
Aug ’20
Failed to sign PKG Installer
I created PKG installer in command line (see below, command's output is in italic). Installer is opening on my MBP, but after uploading on server and download by link, macOS shows TestApp.app.2.0(32).pkg” can’t be opened because Apple cannot check it for malicious software. TestApp.app is application signed by Developer ID Application certificate and notarised with Xcode. Check TestApp.app signing: codesign --verify --verbose TestApp.app TestApp.app: valid on disk TestApp.app: satisfies its Designated Requirement spctl --assess --verbose TestApp.app TestApp.app: accepted source=Notarized Developer ID Build package component pkgbuild --identifier --version '2.0(32)' --sign 'Developer ID Installer: ….’ --install-location /Applications --component TestApp.app component.pkg pkgbuild: Adding component at …../Create PKG/TestApp.app pkgbuild: Using timestamp authority for signature pkgbuild: Signing package with identity Developer ID Installer: …” from keychain …./Librar
Replies
1
Boosts
0
Views
1.6k
Activity
Oct ’21
How to depend on a non-macOS external package in macros
Hello everyone, I am trying to create a macro that depends on an external package to abstract some of the packages logic. The point is that the dependency does not support macOS which results in a build failure when trying to build the macro. Since macOS 10.15 is required for creating macros, any thing can be done to get it to work? Here is a sample to what I'm trying to do import PackageDescription import CompilerPluginSupport let package = Package( name: Stringify, platforms: [ .macOS(.v10_15), .iOS(.v13), .tvOS(.v13), .watchOS(.v6), .macCatalyst(.v13) ], products: [ .library( name: Stringify, targets: [Stringify] ), .executable( name: StringifyClient, targets: [StringifyClient] ), ], dependencies: [ .package(url: https://github.com/apple/swift-syntax.git, from: 509.0.0), .package(url: https://github.com/MyDependency, from: 1.0.0), ], targets: [ .target( name: Stringify, dependencies: [StringifyMacros] ), .executableTarget( name: StringifyClient
Replies
1
Boosts
0
Views
429
Activity
Jul ’24
Reply to Swift Package that has `@objc` in Swift code can’t be used due to Objective-C module failure
Let me add extra observations here as well, Swift JIRA is also updated. This is caused by missing -Xcc -module-map-file for swift -frontend for the transitive Swift package dependency used for the Swift files in the application target. This is not happening if the module that Swift Package provided is written in Objective-C.
Replies
Boosts
Views
Activity
Jun ’20
Reply to No such module 'FirebaseFirestore'
Interesting, I am just learning iOS, and during my courses I used Firebase but installed via CocoaPods, this time I added the package via add packages and when I want to use the Firestore DB to add in the app delegate also get this error, wonder what the issue could be. So the authentication features all work, but the Firestore seems to be missing for some reason. Will try and re install it later, but updating the package did not help. I am on Xcode 14.2 (14C18)
Replies
Boosts
Views
Activity
Apr ’23
Storekit2 Fetch Products
I have more than 230 in app products which is Consumable, Non-Consumable & Auto Renewable subscription, So while Initialise Inapp products in storekit2 let productIds = [...your 300 identifiers...] let products = try await Product.products(for: productIds) I am getting repose only few products few missing in TestFlight build, So how to resolve this issue, it happen in only TestFlight or App Store its working?
Replies
0
Boosts
0
Views
110
Activity
May ’25