Search results for

“missing package product”

52,926 results found

Post

Replies

Boosts

Views

Activity

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
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
502
Nov ’25
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 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
How to verify signature of a package
In order to verify the signature of an application on disk, we can use SecStaticCodeCheckValidityWithErrors, which works as expected.However, if this is used on a signed package, the following error occurs The operation couldn’t be completed. (OSStatus error -67062.)Error 67062 also represents that an application is not signedIt appears that SecStaticCodeCheckValidityWithErrors only works with binary code or application bundles. To confirm this, calling codesign also fails to verify the signature of a package: codesign -dvvv myPackage.pkg myPackage.pkg: code object is not signed at allHow can we programmatically verify the signature of a package (pkg), without resorting to calling an external process such as pkgutil?
3
0
3.9k
Mar ’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
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 10.11 beta 3 took sound away from me
Sorry, I'm not clear on the sequence of events - I thought you had reinstalled from beta 1, then updated to 2 and then to 3 today after realising that you were missing core components of your OS.To reinstall beta 3 over itelf, just download from this link and install the .pkg file:http://swcdn.apple.com/content/downloads/45/55/031-27723/jfp6s17zwamp7zr7iwmkmdigzudq3fd72e/OSXUpd10.11.pkg
Topic: App & System Services SubTopic: Core OS Tags:
Jul ’15
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 Notarizing a MIDI Plugin
However, Gatekeeper is not letting direct installation. Can you clarify why you mean by that? Does Gatekeeper prevent you from opening the installer package? Did you notarise and staple that package? ps We generally recommend that you sign everything from the inside out and then only notarise your outermost container (in this case your installer package). For more hints on this topic, see Signing a Mac Product For Distribution - https://forums.developer.apple.com/thread/128166. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @apple.com
Topic: Code Signing SubTopic: Entitlements Tags:
Jun ’20
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
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
Swift Package with Metal
Hi, I've got a Swift Framework with a bunch of Metal files. Currently users have to manually include a Metal Lib in their bundle provided separately, to use the Swift Package. First question; Is there a way to make a Metal Lib target in a Swift Package, and just include the .metal files? (without a binary asset) Second question; If not, Swift 5.3 has resource support, how would you recommend to bundle a Metal Lib in a Swift Package?
12
0
9.5k
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
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
502
Activity
Nov ’25
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 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
How to verify signature of a package
In order to verify the signature of an application on disk, we can use SecStaticCodeCheckValidityWithErrors, which works as expected.However, if this is used on a signed package, the following error occurs The operation couldn’t be completed. (OSStatus error -67062.)Error 67062 also represents that an application is not signedIt appears that SecStaticCodeCheckValidityWithErrors only works with binary code or application bundles. To confirm this, calling codesign also fails to verify the signature of a package: codesign -dvvv myPackage.pkg myPackage.pkg: code object is not signed at allHow can we programmatically verify the signature of a package (pkg), without resorting to calling an external process such as pkgutil?
Replies
3
Boosts
0
Views
3.9k
Activity
Mar ’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
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 10.11 beta 3 took sound away from me
Sorry, I'm not clear on the sequence of events - I thought you had reinstalled from beta 1, then updated to 2 and then to 3 today after realising that you were missing core components of your OS.To reinstall beta 3 over itelf, just download from this link and install the .pkg file:http://swcdn.apple.com/content/downloads/45/55/031-27723/jfp6s17zwamp7zr7iwmkmdigzudq3fd72e/OSXUpd10.11.pkg
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Jul ’15
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. I solved this problem with this solution! Thanks!
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Sep ’20
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
Reply to Notarizing a MIDI Plugin
However, Gatekeeper is not letting direct installation. Can you clarify why you mean by that? Does Gatekeeper prevent you from opening the installer package? Did you notarise and staple that package? ps We generally recommend that you sign everything from the inside out and then only notarise your outermost container (in this case your installer package). For more hints on this topic, see Signing a Mac Product For Distribution - https://forums.developer.apple.com/thread/128166. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @apple.com
Topic: Code Signing SubTopic: Entitlements Tags:
Replies
Boosts
Views
Activity
Jun ’20
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
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 "Cannot connect to iTunes Store" during testing
I'm getting this error in production and losing subscribers. I haven't done any updates to either the app or the backend recently.
Replies
Boosts
Views
Activity
May ’20
Swift Package with Metal
Hi, I've got a Swift Framework with a bunch of Metal files. Currently users have to manually include a Metal Lib in their bundle provided separately, to use the Swift Package. First question; Is there a way to make a Metal Lib target in a Swift Package, and just include the .metal files? (without a binary asset) Second question; If not, Swift 5.3 has resource support, how would you recommend to bundle a Metal Lib in a Swift Package?
Replies
12
Boosts
0
Views
9.5k
Activity
Jun ’20