Search results for

“missing package product”

55,551 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
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
550
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 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 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 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.3k
Mar ’23
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
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
Why swift packages are resolved in the DerivedData folder
I just integrated a first Swift package into my app. I was looking for committing it, but found out that the package is downloaded into the DerivedData when it's resolved. I was wondering why that is, and if there's a way around it? Can we specify another folder? In my team we commit the pods with our code (so we can go back and build an old version with the exact versions of the pods). It seems odd to include that in the DerivedData. Also, it is not rare that we need to delete that folder, so it seems not so productive to delete and redownload that each time...
0
0
1.3k
Jul ’19
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
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
550
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 CKShare works only outside App Store released Application
I think the problem is due to the container schema that's not deployed to the production environment. Strangely everything works except the sharing functionality. But now the question is: if I deploy to the production environment the users will lose their data?
Topic: App & System Services SubTopic: iCloud Tags:
Replies
Boosts
Views
Activity
Dec ’24
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 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
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 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 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.3k
Activity
Mar ’23
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 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
Why swift packages are resolved in the DerivedData folder
I just integrated a first Swift package into my app. I was looking for committing it, but found out that the package is downloaded into the DerivedData when it's resolved. I was wondering why that is, and if there's a way around it? Can we specify another folder? In my team we commit the pods with our code (so we can go back and build an old version with the exact versions of the pods). It seems odd to include that in the DerivedData. Also, it is not rare that we need to delete that folder, so it seems not so productive to delete and redownload that each time...
Replies
0
Boosts
0
Views
1.3k
Activity
Jul ’19
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 Current bundle does not have a SystemExtensions directory
Can anyone think of anything I have missed which would cause Xcode to continue packaging it as an appex rather than a sysex? Are you signing your container app with this entitlement: com.apple.developer.system-extension.install Are you using the OSSystemExtensionRequest API to install your Network System Extension?
Topic: Code Signing SubTopic: Entitlements Tags:
Replies
Boosts
Views
Activity
Jul ’22