Search results for

missing package product

50,279 results found

Post

Replies

Boosts

Views

Activity

Local xcFrameworks in Swift Packages
In the talk, it was explained how to use a binaryTarget to add a .xcframework from a url, but what about a local path? Take the following Package and file structure, is this the correct way to structure and refer to the .xcFramework? | SamplePackage | - | Package.swift | - | README.swift | - | Sources | - | - | Sample | - | - | - | file.swift | - | - | SampleFramework | - | - | - | framework.xcframework | - | - | Tests | - | - | - | LinuxMain.swift | - | - | - | SampleTexts | - | - | - | - | sampleTests.swift // swift-tools-version:5.3 // The swift-tools-version declares the minimum version of Swift required to build this package. import PackageDescription let package = Package( name: Sample, platforms: [ .iOS(.v13), .macOS(.v10_12) ], products: [ // Products define the executables and libraries produced by a package, and make them visible to other packages. .library( name: Sample, targets: [Sample, SampleFramework]), ], targets: [ // Tar
4
0
8.9k
Jun ’20
Package Authoring Error when opening pkg file
When opening a pkg file on Mojave and Catalina I'm seeing following Package Authoring Errors in Installer log (/var/log/install.log):Package Authoring Error: <background> has an unsupported MIME type: image/data Package Authoring Error: <background_scaling> has an unsupported MIME type: X-NSObject/NSNumber Package Authoring Error: <background_alignment> has an unsupported MIME type: X-NSObject/NSNumber Package Authoring Error: <layout-direction> has an unsupported MIME type: X-NSObject/NSNumberwhich is weird because background is defined in pkg Distribution XML as:<background file=background.tiff alignment=bottomleft scaling=none mime-type=image/tiff/>based on specification of Distribution file in https://developer.apple.com/library/archive/documentation/DeveloperTools/Reference/DistributionDefinitionRef/Chapters/Distribution_XML_Ref.htmlSimilar problems can be seen even on pkg installers that contain no back
5
0
5.1k
Jan ’20
Reply to UIDocumentBrowserViewController won't let me pick existing document
Looks like my problem is definitely related to it being a file package. I have a second document type that is not a file package/directory and the UIDocumentBrowserViewController calls the delegate method documentBrowser(_ controller: UIDocumentBrowserViewController, didPickDocumentURLs documentURLs: [URL]) when I tap on it.So am I doing something wrong (i.e., missing an extra step necessary for file packages) or is UIDocumentBrowserViewController broken for file packages and I need to file a bug?Thanks,Dave
Topic: App & System Services SubTopic: Core OS Tags:
Jun ’17
Which part to be notarized in a pkg, .app or pkg or both ?
Hi, I have to publish a macOS application outside the AppStore, downloadable from another a third-party website. I have to build an app say for example myapp.app and then pack it inside a package installer .pkg file users will download and run pkg to install the app. Which part in the least should be Notarized & signed, the app has to run on catalina 10.14 & newer versions Should .app and .pkg both should be signed and notarized or .pkg is enough to be signed & notarized ? if some one can direct me to any documentation on this subject along with answer, that would be great. Thanks, Ahmed
1
0
573
Feb ’21
Reply to Notarization has stopped working for .pkg files
Just to add to the post, I tried notarizing again a .pkg installer that I had already notarized successfully a few weeks ago and I got the same problem, so unless I'm missing something obvious here, there was a change in Apple's side that is now causing this problem.In the meantime, I'm going to try to notarize the app first, then package it, and then notarize the .pkg file.
Topic: Code Signing SubTopic: General Tags:
Oct ’19
How can you communicate that a .xcframework is a dependency OF the swift package inside Swift package definition?
I am sort of trying to do the opposite of what others are doing. I have a target called CopyFramework that creates a CopyFramework.framework within my main xcproj file. I set up this target because a specific framework (we can call it Tools.xcframework) is distributed as a binary. That framework file lives within the code. Tools.xcframework is structured like so Tools.xcframework (Coding/testBuild/DynamicToolFrameworks/Tools.xcframework) info.plist ios-arm64/ Tools.xcframework/ Tools (executable file) Tools.bundle Headers/ Info.plist Modules/ Tools.swiftmodule/ arm64-apple-ios.abi.json arm64-apple-ios.private.swiftinterface arm64-apple-ios.swiftdoc arm64-apple-ios.swiftinterface module.modulemap module.private.modulemap PrivateHeaders/ ios-arm64_x86_64-simulator/ When the CopyFramework target is run xcode does a few steps which copy the correct version of this framework to derived data. Process Tools.xcframework (iOS) Coding/testBuild/DynamicToolFrameworks/Tools.xcframework /Library/Developer/Xcode/DerivedDat
0
0
75
Jun ’25
Reply to Framework built on Xcode9 are not working on Xcode8
It could be a bug or incompatibility, but there are some other subtle problems in your project(s) that may be affecting you.Incidentally, there is no such thing as a static framework. A framework is a dynamic library packaged as a bundle. Perhaps you mean a private framework (a framework embedded in an app bundle, so not shared between apps, which is very common), or a static library (which is a collection of object files, a library in the Unix sense, not in the Apple sense).— One possibility is that the deployment target got changed when you converted the framework project for Xcode 9. This might result in an incompatible build product.— Another possibility is that your are not producing the framework using Archive (from the Product menu), but are trying to use the build product from a Build or Run operation. The difference is that Build might not build all of the CPU architectures that a finished (Archive'd) framework needs — the variant for arm64 might actually be missing
Sep ’17
*.pkg Not compatible with your MacOS
Hello,Is there any way to debug why my pkg is nt compatible with my MacOS?I was building the *.app using Qt and deploy by `macdeployqt`. After check every Frameworks and plugins paths the next step was:- `pkgbuild --component <NAME>.app --install-location /Application <APP_NAME>.pkg`and`sudo productbuild --package <APP_NAME>.pkg --content <APP_NAME>.app --sign Developer Install ID: (XXXXX) <SIGNED_APP_NAME>.pkg `I was trying to Install <SIGNED_APP_NAME>.pkg but Instaler throws me an error: This package is incompatible with your version of MacOS.I'm using MacOs 10.15. + I found also that there is no codesign folder in my bundle is that might be a reason?Maybe I missed something?
3
0
2.5k
Apr ’20