Search results for

“missing package product”

55,550 results found

Post

Replies

Boosts

Views

Activity

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
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
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
440
Jul ’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:
Aug ’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)
Apr ’23
Swift executables in installer packages (.pkg) preinstall/postinstall
It seems that preinstall/postinstall scripts in installer packages (.pkg) are not limited to shell scripts, but can be any kind of executable (e.g. compiled Swift programs). This sounds like an exciting possibility to re-use logic, constants, tests etc. from the app that is being installed, and at the same time benefit from Swift features like type safety for complex installer scripts. Has anyone done this? What were your experiences? Is it advisable, or is it likely to break on the next OS update?
2
0
373
Nov ’24
Reply to SMJobBless privileged helpers and granting permission
Thanks Quinn, Sorry, yes, my sloppy terminology of The Finder which I often use for unattached dialogs the user sees. I did not know this about the Full Disk Access being different so my experiments with plists for the priviledge helper need to be redone. One of the operations my helper is doing that needs Full Disk Access is downloading a pkg and checking it is signed. None of the normal security api's appear to work with pkg's, maybe I missed something there, I can check apps and so forth on disk. So I end up running /usr/sbin/pkgutil --check-signature instead as I could not figure out how pkgutil is implemented. Did I miss something in the security api, should I be able to look at a pkg's validity?
Topic: Privacy & Security SubTopic: General Tags:
Apr ’22
Reply to EAS build works in Expo Go & Simulator, TestFlight app crashes on open
Solved this one myself, but for anyone experiencing an operator() crash, be sure to read through the react navigation docs, then find exactly which part of react navigation you used (ie. Stack, Drawer, etc) as there can be some additional packages to add to ensure it runs cleanly on TestFlight. My problem was one missing package that needed to be added.
Jul ’22
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
119
May ’25
Reply to Swift Package with Resources – Upload issue
OK. It's working fine. What I did not understand was that I needed to change the Info.plist file that was located *inside* the archive. I initially thought it was supposed to be somewhere in the Package. So the process is: Create an archive and select it in Xcode Organizer. Show in Finder. Open package contents. Go down the Folder structure (Products -> Application) until you find your .app file. Again, show package contents. There should be your package .bundle file. Again show package contents. Here you should see the Info.plist file. Open it in Xcode and remove the Executable file entry. Save and return to Xcode Organizer. Now you can Distribute the app.
Jul ’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
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
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 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
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
488
Activity
Jun ’26
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
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
440
Activity
Jul ’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
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
Swift executables in installer packages (.pkg) preinstall/postinstall
It seems that preinstall/postinstall scripts in installer packages (.pkg) are not limited to shell scripts, but can be any kind of executable (e.g. compiled Swift programs). This sounds like an exciting possibility to re-use logic, constants, tests etc. from the app that is being installed, and at the same time benefit from Swift features like type safety for complex installer scripts. Has anyone done this? What were your experiences? Is it advisable, or is it likely to break on the next OS update?
Replies
2
Boosts
0
Views
373
Activity
Nov ’24
Reply to SMJobBless privileged helpers and granting permission
Thanks Quinn, Sorry, yes, my sloppy terminology of The Finder which I often use for unattached dialogs the user sees. I did not know this about the Full Disk Access being different so my experiments with plists for the priviledge helper need to be redone. One of the operations my helper is doing that needs Full Disk Access is downloading a pkg and checking it is signed. None of the normal security api's appear to work with pkg's, maybe I missed something there, I can check apps and so forth on disk. So I end up running /usr/sbin/pkgutil --check-signature instead as I could not figure out how pkgutil is implemented. Did I miss something in the security api, should I be able to look at a pkg's validity?
Topic: Privacy & Security SubTopic: General Tags:
Replies
Boosts
Views
Activity
Apr ’22
Reply to EAS build works in Expo Go & Simulator, TestFlight app crashes on open
Solved this one myself, but for anyone experiencing an operator() crash, be sure to read through the react navigation docs, then find exactly which part of react navigation you used (ie. Stack, Drawer, etc) as there can be some additional packages to add to ensure it runs cleanly on TestFlight. My problem was one missing package that needed to be added.
Replies
Boosts
Views
Activity
Jul ’22
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
119
Activity
May ’25
Reply to Swift Package with Resources – Upload issue
OK. It's working fine. What I did not understand was that I needed to change the Info.plist file that was located *inside* the archive. I initially thought it was supposed to be somewhere in the Package. So the process is: Create an archive and select it in Xcode Organizer. Show in Finder. Open package contents. Go down the Folder structure (Products -> Application) until you find your .app file. Again, show package contents. There should be your package .bundle file. Again show package contents. Here you should see the Info.plist file. Open it in Xcode and remove the Executable file entry. Save and return to Xcode Organizer. Now you can Distribute the app.
Replies
Boosts
Views
Activity
Jul ’20
Reply to ios14 "Notifications are not allowed" ERR
In my case, Build Settings - Packaging - Product Name was not English. Changed to English and worked. It was okay to set the name in other languages in iOS 13 though.
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Sep ’20