missing package product

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

These are the Developer Forums, where developers of apps for Apple's platforms ask each other for hints and tips on coding. These forums are NOT where Apple's actual developers chat about stuff. Your post is more of a product support one, so I'd suggest you post it over at the Apple Support Forums. Thanks.

For those who have just stumbled upon this thread, my situation is that I am trying to run the code above in the first post to verify that the colors that I get from an asset catalog are being correctly converted into SwiftUI Color instances so that frequently used custom colors can be more easily managed. This conversion is done automatically using a Swift package plugin that generates the accessors automatically based on the asset catalogs. The persistent issue that I've been having for a longer period of time as I am writing this is that neither XCTest nor Swift Testing find the two instances equal because one is instantiated using the initializer that takes three Double instances (one red, one green, and one blue) and the other is instantiated using the initializer that specifies the color as it appears in an asset catalog. These tests have been consistently failing as a result and are marked as being known issues. My updated version of this project uses Swift Testing for these tests, though the

Another option is to use the sftp CLI command via the foundation Process object. I like this option and am considering experimenting with this, but it seems like a hack. How much of a hack this turns into really depends on how you end up needing to interact with the tool If you can structure your interactions with the tool such that you're simply sending the command and getting a result, then it can actually work reasonably well. Indeed, there are a number of command line tools that effectively operate as API and have even been designed to facilitate that functionality (notably, hdiutil and disk image mounting). ssh is another example of this- many applications intentionally use the ssh command line tool instead of integrating with a library because using the command line allows them to rely more on the users existing security configuration instead of having to duplicate that functionality. However, if you'll end up need to drive the tool interactively, that can be pretty painful. Similarly, things like progr

I compared the console log from a phone with this problem and another one that works: good case: (iOS 17.4) Connection 0: creating secure tcp or quic connection Connection 4: enabling TLS bad case: (iOS 16.0.2) Connection 1: enabling TLS I.e. the bad case is missing the log line creating secure tcp or quic connection. Any ideas how this could happen?

I have the same trouble. Sometimes I get SMAppServiceStatusNotFound status. I noticed that my macOS app is not in the System Preferences/Login Items/Allow Background apps list. So I did run a terminal command sudo sfltool resetbtm I rebooted, and my app was in that list. I had to turn back off all the apps in the Allow Background list, which turned on since the Terminal command. You would agree with me, this is not the way to distribute the app to the customers. I can't ask my customers to run the Terminal command, reboot then turn off all the unwanted apps from the Allow Background list. I guess I miss something. Any idea? How to get my app in that list just after I copied the app within the /Applications folder?

Thank you for your response. I tried the suggested solution, and although it resolved the issue of the view being popped automatically, a different problem has now arisen. (The new issue: Tapping Back from a lower-level View returns to the Root View / No transition animation ) However, while this fix may work for the simplest code, I think it cannot be applied to our production code for the following three reasons: This fix requires placing navigationDestination directly under NavigationStack. In our production code, we have multiple levels such as two, three, or more, each handling different data models within a large navigation view. It's not practical to describe all levels of navigationDestination directly under NavigationStack. This fix introduces another problem, making it unsuitable for inclusion in our production code at this time. I am unsure whether this behavior is due to a specification change in iOS 18 or a bug in the iOS 18 beta, and whether this solution is just a tem

Yes, I have the same issue, Package resolution errors must be fixed before building

Thanks. The part I was missing is the one the documentation for NSTextContentManager doesn't mention, which is that it is an abstract class whose (apparently) only concrete subclass is NSTextContentStorage, which has a textStorage property. guard let textStorage: NSTextStorage = (textLayoutManager?.textContentManager as? NSTextContentStorage)?.textStorage else { return } The sample code also changes the textStorage inside the block passed to textContentManager.performEditingTransaction(_:), which the documentation doesn't seem to explain why it's necessary.

This change is terrible and, as messages show, discriminatory. My hearing is starting to go, which I didn't expect in my 40s, and I work in healthcare and am on call overnights often. I keep missing texts since there's no way to make the phone extra loud and some of my go-to ringtones that were at least a bit longer seem to be gone. Please consider an option to make it louder- even if it's under accessibility.