I'm also seeing this issue. Frustrating.

This isn't working for me. I followed the example given in the video: https://developer.apple.com/videos/play/wwdc2023/10155/?time=1831 And it doesn't detect the default localization, so just shows an empty table. Tools version is 5.9 I even tried renaming the table, so it wouldn't conflict with the main application's Localizable table with no success. // Catalogs file is then FakeModule.xcstrings public func printModuleInfo() { let statement = String(localized: "TestString", table: "FakeModule") log.info("\(statement)") }

Here is the package manifest: // swift-tools-version: 5.9 // The swift-tools-version declares the minimum version of Swift required to build this package. import PackageDescription let package = Package( name: "FakeModule", defaultLocalization: "en", platforms: [ .iOS(.v16) ], products: [ // Products define the executables and libraries a package produces, making them visible to other packages. .library( name: "FakeModule", targets: ["FakeModule"]), ], targets: [ // Targets are the basic building blocks of a package, defining a module or a test suite. // Targets can depend on other targets in this package and products from dependencies. .target( name: "FakeModule", dependencies: [], path: "Sources" ), .testTarget( name: "FakeModuleTests", dependencies: ["FakeModule"]), ] )

The solution could be a mix of some of these things. I just now discovered that there are 2 ways to import a local package. You can do it via importing from the project inspector and provide a Local... package, or you can just drag the Package.swift file into your project, so that it doesn't look like an installed package dependency, but another target in the "workspace" (which is not a workspace), and then these values start to get populated at build time.

yes it seems super weird that they would not help you identify what's causing the warning. For example, the privacy report (via Organizer > right click on Archive) doesn't indicate much either. For me it just had a listing of a SPM package I'm linking. So do I have to fork that repo and fix it in the package, or does my privacy manifest act as an umbrella for any module in my binary? It's strange that they would just say "fix it" and not really tell you where and what the problem is.

Did anyone ever solve this? I'm having the same issue. None of the above helped.

I had wanted to allow my test flight testers to try this out before we deploy it. It hasn't been released yet. So how can I create a default app clip experience for Testflight if I haven't already released v1.0 ? Also, I tried deleting the app from my test device, running the app clip via Xcode, killing it, then scanning a QR of a local app experience that I set up. It gives me this blank card. So now I can't test local experiences anymore. Help!

I have an even worse problem. So I test the app via TestFlight's invocation system (Test/Open) button to launch the app clip. Then I background the app clip. Now I scan a different QR code (set up as a local experience). It calls func scene( _ scene: UIScene, willContinueUserActivityWithType userActivityType: String ) but the scene.userActivity.webpageURL is nil. Because the userActivity is nil. (scene.userActivity) So what are we supposed to do?

I've been experiencing this same thing.

Same issue here! DTS, why would you be secretive about this? This issue affects multiple people and I can't understand how it would be programmer error here. I've done everything as well. I wrap my view in a subclass of UIHostingController where I even call self.view.endEditing(true) and nothing happens. Extremely frustrating. Makes our software look bad.

OP, I find your insolent tone unbecoming of a software professional and it only serves to piss everyone off while you throw a temper tantrum. Please next time leave your feelings out of it; there was someone nice enough to help you restore the functionality you were expecting. Other people see this change as a welcome one, so please stop acting like you're the center of the universe. And yes, I went out of my way to write this because it was THAT bad, how you speak to people.