Are Swift Packages supported by String Catalogs?

I found my answer - yes they are supported. Two things to check:

1. Make sure you're using Swift Tools 5.9 +
2. I had to delete my existing Resources/ folder containing my *.lproj files.

Hi @kernelpop can you please mention your Swift Package Setup? A sample project would have been very helpful!!

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"]),
    ]
)

You have to add defaultLocalization to your Package.swift and it should work

let package = Package(
    name: "YourName",
    defaultLocalization: "en", <---
    platforms: [
      .iOS(.v16)
    ],
...

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.

For me it was missing CFBundleAllowMixedLocalizations, in case someone finds it helpful.

Besides the previously mentioned tips another important thing to note is that the Localizable file needs to be in a Resources folder without *.lproj files - at least this did the trick for me.