Variables are not localized correctly

[futuretap]

• [x ] I have updated Purchases SDK to the latest version
• I have read the Contribution Guidelines
• [ x] I have searched the Community
• [ x] I have read docs.revenuecat.com
• [ x] I have searched for existing Github issues

Describe the bug
When using the German localization, standard (static) texts are localized but all variable content is not localized but just empty.

1. Environment
   1. Platform: iOS
   2. SDK version: 5.16.1
   3. StoreKit version:
      • StoreKit 1 (default on versions <5.0.0. Can be enabled in versions >=5.0.0 with .with(storeKitVersion: .storeKit1))
      • StoreKit 2 (default on versions >=5.0.0)
   4. OS version: 18.2
   5. Xcode version: 16.2
   6. Device and/or simulator:
      • Device
      • [x ] Simulator
   7. Environment:
      • [ x] Sandbox
      • TestFlight
      • Production
   8. How widespread is the issue. Percentage of devices affected: 100% reproducible
2. Debug logs that reproduce the issue. Complete logs with Purchases.logLevel = .verbose will help us debug this issue.

Logs here

3. Steps to reproduce, with a description of expected vs. actual behavior

Create a Paywall with variable content that is localized in German.
The variable content is not localized but just empty.

4. Other information (e.g. stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc.)
   This seems to be a bug in the SDK. I can fix the issue by changing one line, UIConfigProvider.swift:53:

guard let localizations = self.uiConfig.localizations[locale.identifier] ?? self.uiConfig.localizations[locale.languageCode ?? locale.identifier] else {

The workaround is dirty and you should fix this properly.

5. Additional context

[RCGitBot]

👀 We've just linked this issue to our internal tracker and notified the team. Thank you for reporting, we're checking this out!

[nyeu]

Hi @futuretap,
We've made a fix for this issue and it's going to be available in the next SDK version. I'll keep this issue opened until we verify this is fixed for your case.
Best,

[nyeu]

Hi @futuretap,
This should be fixed in the latest version. Let me know if it works on your end so we can close the ticket.

[futuretap]

Yep, looks good. Thanks!