Search results for

“missing package product”

53,790 results found

Post

Replies

Boosts

Views

Activity

Reply to How to use Apple server to host IPA content
From TN2413 In-App Purchase FAQ > How do I create a hosted non-consumable product?There is a current bug that prevents Xcode 6 from uploading hosted content to iTunes Connect. To workaround this issue, use Application Loader to upload a package containing your hosted content. See below for steps on how to do so:In the Xcode Archives Organizer, select the archive containing your hosted content.Click Export.In the dialog that appears, choose Export as an Installer Package.Click Next to start generating your package, then select Export to save your package (a file with a .pkg filename extension).Use Application Loader to upload the above package. See Using Application Loader for more information about it.
Topic: App & System Services SubTopic: StoreKit Tags:
Feb ’17
Xcode 12.2 beta: Cannot add package dependency
I am unable to add package dependency. Everything seems to load and resolve fine, but when I get to the bit where you are asked to Choose package products and targets The Package product is selected, but the Finish button is disabled.... Im on a DTK system and the project is a new project using the App lifecycle. Ive also tried other adding other dependencies with no luck.
12
0
3.1k
Sep ’20
Notarization Rejected for .pkg installer
HiI have a vst plugin installer package (build with Whitebox Packages v 1.2.6) to be notarized. I get Notarization is successful mail from Apple. And also I don't get any error message from any of the process. But when it comes Notarization check - It's been Rejected! I am following this procedure, am I missing something?Sign the vst plugins with codesignBuild the .pkg with Whitebox Packages. (I don't use build-in digital signing tool, I use productsign in command line)Signing the .pkgproductsign --sign Developer ID Installer: XXXXXXX /Volumes/Data/Installer v1.1.0.pkg /Volumes/Data/Signed/Installer v1.1.0.pkgNotarizationxcrun altool --notarize-app -f /Volumes/Data/Signed/Installer v1.1.0.pkg --primary-bundle-id com.xxxxinstaller.pkg --username xxxx --password xxxxAfter a couple of minutes, I get Notarization is successful mail from AppleTime Staple - The staple and validate action worked!xcrun stapler staple /Volumes/Data/Signed/Installer v1.1.0.
2
0
3.4k
Oct ’19
Mac App Packaging
Can someone please explain why Mac app packaging is so farcically convoluted? Windows app packaging can be picked up in an hour or so. But I've spent longer trying to fathom how to package the Mac version than I did building the app. And it's not done with me yet. Every single line of code requires a deep dive into a new, unrelated skillset. So, it’s sidebar after sidebar. Kafka’s ‘The Trial’ comes to mind. Why does it have to be like this?
4
0
522
Nov ’25
Reply to SwiftUI image from Bundle.main not working
Hi, mmm it seems an interesting use case, but what are the benefits on this approach? The main bundle should be app single dependency. if we have the needs of pass data to the package itself , probably some sort of dependency injection could be the best option. I'm not sure that put a main.bundle a shared resources container on different framework/package is the best approach, but probably I miss some point. Bye Rob
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Oct ’24
Reply to xcode 7.3.1 ERROR ITMS - 90167 No. app bundles found in the package
This worked for me:1. Use XCode 7.3.1 (not the Xcode beta) to archive.2. Go to the archive file > Show Package Contents > Products > Applications > {AppName} > Show Package Contents > Info.plist3. Change `BuildMachineOSBuild` to 15G31 (or the most up-to-date prod build number of the macOS) and save it.4. Now export this archive for iOS App Store Deployment5. Forward the .ipa file to a co-worker who runs production version of the macOS.6. Use Application Loader to upload the .ipaLesson learnt: Do not update the macOS to beta version on your primary development machine.
Topic: App & System Services SubTopic: Core OS Tags:
Aug ’16
Reply to Confusions with what can be notarized and what must be notarized
Thank you for your inputs.What bothers us with notarization requirements is that there is no way to test it.You know, testing is fail first, understand the why, then fix.We did put our product on macOS 10.14.5 beta and public release, and we though we were be able to fail there, but we never experienced a failure to demonstrate that notarization helped us to fix it in order to have it run.Implementing notarization in our context represents some kind of work, as we currently build and package our bundles with a build agent.In order to prioritize the implementation of the notarization process in our automated build workflow, I have to explain the why to my product owner and my stakeholder.Currently the why is only because Apple told us to do it, not because we are able to reproduce the failure on macOS beta software by not doing it.If I follow you clearly on the user testing workflow you are suggesting, we will surely encounter a failure.But that won't be a testing failure in the Gate
Topic: Code Signing SubTopic: General Tags:
May ’19
Reply to Xcode fails to start Loading a plug-in failed.
On my MacMini (3 GHz 6-Core Intel Core i5) Xcode, Garageband an iMovie did not launch and opening a terminal window also issued the missing framework error. I manually installed XcodeSystemResources.pkg, MobileDeviceDevelopment.pkg and MobileDevice.pkg in this order. These packages are found in the Xcode.app bundle Xcode.app/Contents/Resources/Packages/... Now the Apps are launching. No idea if there are problems left.
Oct ’20
Reply to codesign osx binary
Presumably you: Are not using Xcode to build your product Want to distribute this outside of the Mac App Store Given that, I recommend that you read through: Creating Distribution-Signed Code for Mac Packaging Mac Software for Distribution Those explain how to sign and then package your product for independent distribution, and have links to notarisation advice. Apropos that last bit: altool is deprecated for the purposes of notarisation and will stop working in Fall 2023. If you’re just getting started, start off with notarytool. For more information about notarytool, watch WWDC 2021 Session 10261 Faster and simpler notarization for Mac apps. Fetch the notary log to see what the notary service is complaining about specifically. My best guess is that you’re signed your installer package with your Developer ID Application code signing identity. That’s not right; for an installer package, you need Developer ID Installer. Packaging Mac Software for D
Topic: App & System Services SubTopic: Core OS Tags:
Aug ’22
Reply to Unable to import local XCFramework module
I was able to do this by adding a module.modulemap file to the Headers. This is all within my library Package project: // swift-tools-version: 6.0 import PackageDescription /** This package wraps FTDI’s D2XX library for macOS. In order to simp xcodebuild -create-xcframework -library /Users/rmann/Downloads/lib3mf_sdk_v2.3.1/Bin/lib3mf.dylib -headers /Users/rmann/Downloads/lib3mf_sdk_v2.3.1/Bindings/C -output lib3mf.xcframework */ let package = Package( name: SwiftD2XX, platforms: [.macOS(.v13)], products: [ .library( name: SwiftD2XX, targets: [SwiftD2XX] ), ], dependencies: [ .package(url: https://github.com/apple/swift-testing.git, branch: main), ], targets: [ .target( name: SwiftD2XX, dependencies: [ ftd2xx ] ), .binaryTarget( name: ftd2xx, path: ../ftd2xx.xcframework ), .testTarget( name: SwiftD2XXTests, dependencies: [ SwiftD2XX, .product(name: Testing, package: swift-testing), ] ), ] ) When I build my xcframework, I use this: xcodebui
Jun ’24
CoreData in SPM Package
I've developed an SPM module in which I have a CoreData model defined as a xcdatamodeld file and I'm having trouble executing tests from the command line, which I want for a CI integration. In the package I load the model by constructing a URL using Bundle.module.url(forResource: ModelName, withExtension: momd). This works when building and testing in Xcode. When executing commands such as swift test from the terminal however, it doesn't, as Bundle.module.url(forResource:withExtension) fails to find the file. Comparing the build artifacts between Xcode's DerivedData and SPM's .build I see that both produce a PackageName_PackageName.bundle but while the Xcode version contains a momd file the SPM version contains an unprocessed xcdatamodeld file. I've tried adding the xcdatamodeld as an explicit resource in the Package.swift file such that the package target now includes resources: [.process(Resources/ModelName.xcdatamodeld)] as an argument. This does not impact the Bundle output. Any ideas ho
1
0
2.1k
Mar ’23
Reply to Unable to import local XCFramework module
There is a workaround by defining a dummy C target that includes the XCFramework. This is explained on the forum: https://forums.swift.org/t/swift-package-and-xcframework-target-for-c-library-where-to-include-the-header/51163/6 You will find a link to a sample repository that show how to architecture the project: https://github.com/withuno/UnoSwift // The swift-tools-version declares the minimum version of Swift required to build this package. import PackageDescription let package = Package( name: IBANKit, products: [ // Products define the executables and libraries a package produces, making them visible to other packages. .library( name: IBANKit, targets: [IBANKit]), ], dependencies: [], targets: [ // Adds the C module as a dependencies to your C sources .target( name: IBANKit, dependencies: [C], path: Sources/IBANKit ), // Create a dummy c package that uses the XCFramework .target( name: C, dependencies: [IBANChecker-Core], pa
Oct ’23
Reply to How to use Apple server to host IPA content
From TN2413 In-App Purchase FAQ > How do I create a hosted non-consumable product?There is a current bug that prevents Xcode 6 from uploading hosted content to iTunes Connect. To workaround this issue, use Application Loader to upload a package containing your hosted content. See below for steps on how to do so:In the Xcode Archives Organizer, select the archive containing your hosted content.Click Export.In the dialog that appears, choose Export as an Installer Package.Click Next to start generating your package, then select Export to save your package (a file with a .pkg filename extension).Use Application Loader to upload the above package. See Using Application Loader for more information about it.
Topic: App & System Services SubTopic: StoreKit Tags:
Replies
Boosts
Views
Activity
Feb ’17
Xcode 12.2 beta: Cannot add package dependency
I am unable to add package dependency. Everything seems to load and resolve fine, but when I get to the bit where you are asked to Choose package products and targets The Package product is selected, but the Finish button is disabled.... Im on a DTK system and the project is a new project using the App lifecycle. Ive also tried other adding other dependencies with no luck.
Replies
12
Boosts
0
Views
3.1k
Activity
Sep ’20
Notarization Rejected for .pkg installer
HiI have a vst plugin installer package (build with Whitebox Packages v 1.2.6) to be notarized. I get Notarization is successful mail from Apple. And also I don't get any error message from any of the process. But when it comes Notarization check - It's been Rejected! I am following this procedure, am I missing something?Sign the vst plugins with codesignBuild the .pkg with Whitebox Packages. (I don't use build-in digital signing tool, I use productsign in command line)Signing the .pkgproductsign --sign Developer ID Installer: XXXXXXX /Volumes/Data/Installer v1.1.0.pkg /Volumes/Data/Signed/Installer v1.1.0.pkgNotarizationxcrun altool --notarize-app -f /Volumes/Data/Signed/Installer v1.1.0.pkg --primary-bundle-id com.xxxxinstaller.pkg --username xxxx --password xxxxAfter a couple of minutes, I get Notarization is successful mail from AppleTime Staple - The staple and validate action worked!xcrun stapler staple /Volumes/Data/Signed/Installer v1.1.0.
Replies
2
Boosts
0
Views
3.4k
Activity
Oct ’19
Reply to Application Installer now only works on a few versions of OS
How are you building your installer package? Using Apple tools? Or a third-party product? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Replies
Boosts
Views
Activity
Mar ’22
Mac App Packaging
Can someone please explain why Mac app packaging is so farcically convoluted? Windows app packaging can be picked up in an hour or so. But I've spent longer trying to fathom how to package the Mac version than I did building the app. And it's not done with me yet. Every single line of code requires a deep dive into a new, unrelated skillset. So, it’s sidebar after sidebar. Kafka’s ‘The Trial’ comes to mind. Why does it have to be like this?
Replies
4
Boosts
0
Views
522
Activity
Nov ’25
Reply to Could not find the main bundle or missing CFBundleIdentifier
Progress - discovered a missed step. First have to run 'productbuilder' to create a .pkg from the .app.Would suggest that 'altool' issue an error message if the file given in -f does not have one of the supported types.
Topic: Code Signing SubTopic: General Tags:
Replies
Boosts
Views
Activity
Jun ’20
Reply to SwiftUI image from Bundle.main not working
Hi, mmm it seems an interesting use case, but what are the benefits on this approach? The main bundle should be app single dependency. if we have the needs of pass data to the package itself , probably some sort of dependency injection could be the best option. I'm not sure that put a main.bundle a shared resources container on different framework/package is the best approach, but probably I miss some point. Bye Rob
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Oct ’24
Reply to xcode 7.3.1 ERROR ITMS - 90167 No. app bundles found in the package
This worked for me:1. Use XCode 7.3.1 (not the Xcode beta) to archive.2. Go to the archive file > Show Package Contents > Products > Applications > {AppName} > Show Package Contents > Info.plist3. Change `BuildMachineOSBuild` to 15G31 (or the most up-to-date prod build number of the macOS) and save it.4. Now export this archive for iOS App Store Deployment5. Forward the .ipa file to a co-worker who runs production version of the macOS.6. Use Application Loader to upload the .ipaLesson learnt: Do not update the macOS to beta version on your primary development machine.
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Aug ’16
Reply to Confusions with what can be notarized and what must be notarized
Thank you for your inputs.What bothers us with notarization requirements is that there is no way to test it.You know, testing is fail first, understand the why, then fix.We did put our product on macOS 10.14.5 beta and public release, and we though we were be able to fail there, but we never experienced a failure to demonstrate that notarization helped us to fix it in order to have it run.Implementing notarization in our context represents some kind of work, as we currently build and package our bundles with a build agent.In order to prioritize the implementation of the notarization process in our automated build workflow, I have to explain the why to my product owner and my stakeholder.Currently the why is only because Apple told us to do it, not because we are able to reproduce the failure on macOS beta software by not doing it.If I follow you clearly on the user testing workflow you are suggesting, we will surely encounter a failure.But that won't be a testing failure in the Gate
Topic: Code Signing SubTopic: General Tags:
Replies
Boosts
Views
Activity
May ’19
Reply to Xcode fails to start Loading a plug-in failed.
On my MacMini (3 GHz 6-Core Intel Core i5) Xcode, Garageband an iMovie did not launch and opening a terminal window also issued the missing framework error. I manually installed XcodeSystemResources.pkg, MobileDeviceDevelopment.pkg and MobileDevice.pkg in this order. These packages are found in the Xcode.app bundle Xcode.app/Contents/Resources/Packages/... Now the Apps are launching. No idea if there are problems left.
Replies
Boosts
Views
Activity
Oct ’20
Reply to codesign osx binary
Presumably you: Are not using Xcode to build your product Want to distribute this outside of the Mac App Store Given that, I recommend that you read through: Creating Distribution-Signed Code for Mac Packaging Mac Software for Distribution Those explain how to sign and then package your product for independent distribution, and have links to notarisation advice. Apropos that last bit: altool is deprecated for the purposes of notarisation and will stop working in Fall 2023. If you’re just getting started, start off with notarytool. For more information about notarytool, watch WWDC 2021 Session 10261 Faster and simpler notarization for Mac apps. Fetch the notary log to see what the notary service is complaining about specifically. My best guess is that you’re signed your installer package with your Developer ID Application code signing identity. That’s not right; for an installer package, you need Developer ID Installer. Packaging Mac Software for D
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Aug ’22
Reply to Apple TV Developer Kit - Missing cable?
Really, I wonder why you wonder?Shipping pre-packaged product is a complex process. We'll never know why you scored. It's not like they did a background check on you and cherry picked the kit with your name on it, afterall 🙂
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Oct ’15
Reply to Unable to import local XCFramework module
I was able to do this by adding a module.modulemap file to the Headers. This is all within my library Package project: // swift-tools-version: 6.0 import PackageDescription /** This package wraps FTDI’s D2XX library for macOS. In order to simp xcodebuild -create-xcframework -library /Users/rmann/Downloads/lib3mf_sdk_v2.3.1/Bin/lib3mf.dylib -headers /Users/rmann/Downloads/lib3mf_sdk_v2.3.1/Bindings/C -output lib3mf.xcframework */ let package = Package( name: SwiftD2XX, platforms: [.macOS(.v13)], products: [ .library( name: SwiftD2XX, targets: [SwiftD2XX] ), ], dependencies: [ .package(url: https://github.com/apple/swift-testing.git, branch: main), ], targets: [ .target( name: SwiftD2XX, dependencies: [ ftd2xx ] ), .binaryTarget( name: ftd2xx, path: ../ftd2xx.xcframework ), .testTarget( name: SwiftD2XXTests, dependencies: [ SwiftD2XX, .product(name: Testing, package: swift-testing), ] ), ] ) When I build my xcframework, I use this: xcodebui
Replies
Boosts
Views
Activity
Jun ’24
CoreData in SPM Package
I've developed an SPM module in which I have a CoreData model defined as a xcdatamodeld file and I'm having trouble executing tests from the command line, which I want for a CI integration. In the package I load the model by constructing a URL using Bundle.module.url(forResource: ModelName, withExtension: momd). This works when building and testing in Xcode. When executing commands such as swift test from the terminal however, it doesn't, as Bundle.module.url(forResource:withExtension) fails to find the file. Comparing the build artifacts between Xcode's DerivedData and SPM's .build I see that both produce a PackageName_PackageName.bundle but while the Xcode version contains a momd file the SPM version contains an unprocessed xcdatamodeld file. I've tried adding the xcdatamodeld as an explicit resource in the Package.swift file such that the package target now includes resources: [.process(Resources/ModelName.xcdatamodeld)] as an argument. This does not impact the Bundle output. Any ideas ho
Replies
1
Boosts
0
Views
2.1k
Activity
Mar ’23
Reply to Unable to import local XCFramework module
There is a workaround by defining a dummy C target that includes the XCFramework. This is explained on the forum: https://forums.swift.org/t/swift-package-and-xcframework-target-for-c-library-where-to-include-the-header/51163/6 You will find a link to a sample repository that show how to architecture the project: https://github.com/withuno/UnoSwift // The swift-tools-version declares the minimum version of Swift required to build this package. import PackageDescription let package = Package( name: IBANKit, products: [ // Products define the executables and libraries a package produces, making them visible to other packages. .library( name: IBANKit, targets: [IBANKit]), ], dependencies: [], targets: [ // Adds the C module as a dependencies to your C sources .target( name: IBANKit, dependencies: [C], path: Sources/IBANKit ), // Create a dummy c package that uses the XCFramework .target( name: C, dependencies: [IBANChecker-Core], pa
Replies
Boosts
Views
Activity
Oct ’23