Tim De JongFeb 14

@danielsaidi I was reading your article: https://danielsaidi.com/blog/2025/12/02/a-better-way-to-localize-swift-packages-with-xcode-string-catalogs

And I've since moved all my Localizable.xcstrings to my SPM packages. However, Xcode is now marking all translations as stale (unless I marked them as manual). Is this to be expected?

#swift #swiftlang #iOSDev #localization

A Better Way to Localize Swift Packages with Xcode String Catalogs

Xcode 26 fixes many problems involved in localizing Swift Packages with Xcode String Catalogs. Let’s see how we can use its automatically...

Show threadDaniel SaidiFeb 20

@tjadejong Hi Tim! You need to add the resource information to your Swift package file, so that Xcode handles it properly. Otherwise, the string catalog will not be processed by the package. You must also add the default locale to the package. You can take a look at this package file for reference :)

https://github.com/danielsaidi/EmojiKit/blob/main/Package.swift

EmojiKit/Package.swift at main · danielsaidi/EmojiKit

Create emoji-based features on all major Apple platforms, using Swift & SwiftUI. - danielsaidi/EmojiKit

GitHub
Show threadTim De JongFeb 20
@danielsaidi thanks!! I added the resources but not the default language. Maybe it’s because of that it marks everything as stale? Will try to add it tomorrow!
Show threadDaniel Saidi
@tjadejong Try adding a new key with the plus button to generate a symbol and see if it gets processed. :)
Feb 21 at 1:03pmIvory for iOS
Show threadTim De JongFeb 23
@danielsaidi it all started working when I've added the defaultLocalization. Thanks!!