missing package product

Hi, I tried to create a swift package using xCode's „Swift Package“ template and tried to write some tests. Unfortunately because my package is all about Bluetooth, the test binary fails with the following message; xctest[9145:288236] [access] This app has crashed because it attempted to access privacy-sensitive data without a usage description. The app's Info.plist must contain an NSBluetoothAlwaysUsageDescription key with a string value explaining to the user how the app uses this data. But how to add this key in a Swift Package? Is it really impossible to write and run test cases for a Swift Package containing Bluetooth? I must miss something...

I have created a swift package and successfully added some stub code, imported into another class import PackageName This all works as expected when building in debug configuration. When I try to build for release using xcodebuild, it fails with no such module : PackageName Is there something missing that dictates how a package works in different configurations? Thanks

Distribute a Metal renderer in a Swift package. View Technote TN3133 >

I have successfully created subscription with all metaData: Localization(inside subscription and also for subscription group), logo, description and also screenshots but subscription shows missing metadata instead of ready to submit causing flutter app package inAppPurchase to not found the subscription id or product it.

I work on iOS App project in workspace. I splitted feature in a Local Swift Package. Workspace contains both iOS App Project and Swift Package. https://i.stack.imgur.com/LhL5j.jpg Swift package platform is iOS 14 and deployment target of project is iOS 13. I put optional link on my Swift Package to avoid crash on iOS 13 https://i.stack.imgur.com/Y1HYb.png Application run well on iOS 14 but still crash on iOS 13 : dyld: Symbol not found: _$s7SwiftUI4ViewP14_viewListCount6inputsSiSgAA01_ceF6InputsV_tFZTq Just for example, I would like to use Swift Package like this : Swift #if canImport(Classifier) @available(iOS 14.0, *) struct ActionClassifier: View { var body: some View { Text(Hello, World!) } } #endif Did I miss something on the way of link my Swift Package Binary to my project ?

I have made a custom swift package that contains the encoding and decoding functions for my app String Conversion Tool. It is uploaded to GitHub: (https://github.com/Casual3306/ConverterExtra). I do a request for the package (in my apps main project) and the package imports just fine, it is present in the Frameworks, Libraries, and Embedded Content and it is present in Package Dependencies, I have also run: Reset Package Caches and Resolve Package Versions. The package also imports into the designated module as a module but when I try to access any of that modules files like > ConverterExtras > Encoders it is giving me an error saying that This class may not be available in this context. All of the files are in the module package but Xcode isn't finding them for some reason: Xcode version: 13 System: MacOS (Big Sur 11.6)

To ship a product outside of the Mac App Store, you must notarise it. The notary service issues a notarised ticket, and the ultimate consumer of that ticket is Gatekeeper. However, Gatekeeper does not just check the ticket; it also applies a variety of other checks, and it’s possible for those checks to fail even if your notarised ticket is just fine. To avoid such problems showing up in the field, test your product’s compatibility with Gatekeeper before shipping it. To do this: Set up a fresh machine, one that’s never seen your product before. If your product supports macOS 10.15.x, x < 4, the best OS version to test with is 10.15.3 [1]. Download your product in a way that quarantines it (for example, using Safari). Disconnect the machine from the network. It might make sense to skip this step. See the discussion below. Install and use your product as your users would. If the product is signed, notarised, and stapled correctly, everything shou

The flags like #if DEBUG ... endif are dependent on the Active Compilation Conditions. So if they say DEBUG the enclosed code block will be executed, otherwise not. Now I have the phenomenon that a #DEBUG block in a Package does not evaluate these conditions. It rather depends on the name of the configuration used to build. So if I build my app with Active Compilation Condition set to DEBUG, but the configuration name is something like App-Release, the DEBUG block in my Package is not added/executed. The ones which are directly in the project are added. Vice versa if the Compilation Condition say RELEASE but the configuration is called App-Debug the blocks in the Package are added to the compilation, but the ones in the project itself are not It suffices that the config name contains the word Debug for this to happen. E.g. the configuration App-Release-Debug (I know that this would be stupid, but it is for demonstrating purposes) will cause the Packages to include the DEBUG

我想在我的 Mac OS 项目 （Swift UI） 中添加一个 Package dependency Package，但我只能添加一个 Package Collection，我不能只添加一个单独的包依赖包，我想添加 mysql kit 以使我的项目链接到 Mysql 数据库

Hi AllI am trying to Notarize and Staple a pkg installer of our app, I am facing issues with staplingMy PKG is product signed with a valid developer certificateFollowing is how i verify itspctl -a -v --type install test.pkg test.pkg: acceptedsource=Notarized Developer IDpkgutil --check-signature test.pkgPackage test.pkg: Status: signed by a certificate trusted by macOSIt was successfully Notarized and status of the request shows success.But when i try Staple the same app it fails with following errorstapler staple --verbose test.pkgProcessing: /Users/admin/Downloads/test.pkgProperties are { NSURLIsDirectoryKey = 0; NSURLIsPackageKey = 0; NSURLIsSymbolicLinkKey = 0; NSURLLocalizedTypeDescriptionKey = Installer package; NSURLTypeIdentifierKey = com.apple.installer-package-archive; _NSURLIsApplicationKey = 0;}Sig Type is RSA. Length is 3Could not find an appropriate code signature in the test.pkg installer package.Cannot download ticket. CDHash must be set.Please let

Good day I am developing XRKit framework, which contains the pipeline logic for rendering using Metal, in manifest it has two targets - framework itself in Swift and XRKitDefenitions in C++ and MSL (since Apple forbids us multilingualism in one package). Both targets have Resources folders open in their manifest. When I try to access the test files hello01.txt (Resources for XRKit) and hello2.txt (Resources for XRKitDefenitions) via Bundle.module, I only see hello01.txt and it doesn't read hello2.txt because it's in a different target. How do I properly organize my code with SPM to access the Resources of XRKitDefenitions target? PS When trying to organize XRKitDefenitions as a remote package on GitHub and defining it as a dependency, situation does not change. I understand now that Bundle.module only refers to its Resources. Is there a way to refer to resources that provided other targets or dependencies in the same package?

I've been trying for hours just wanted some direction. I am trying to set up an app that uses a local mongo database. I've set up the IP address and everything, I'll be port forwarding for usage outside my local network. But I've been having some trouble importing mongbodb for my swift app. I keep getting this error with the package manager. If you have some tips please send them my way. So here is the code I'm supposed to use got this from the GitHub page: https://github.com/mongodb/mongo-swift-driver // swift-tools-version:5.1 import PackageDescription let package = Package( ttname: MyPackage, ttdependencies: [ tttt.package(url: https://github.com/mongodb/mongo-swift-driver.git, from: VERSION.STRING.HERE), tt], tttargets: [ tttt// Async module tttt.target(name: MyAsyncTarget, dependencies: [MongoSwift]), tttt// Sync module tttt.target(name: MySyncTarget, dependencies: [MongoSwiftSync]) tt] ) So all I did was add the version I needed and I put the latest. // swift-tools-version:5.3