Paywall language changes on every app re-install

[akashpopat]

• [x] I have updated Purchases SDK to the latest version
• [x] 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 On every app re-install the language shown on the paywall switches from the current region to the current locale. The app supports Dutch and English and I am using the app from the Netherlands but my current language set on device is English. I would assume the Paywall to be in English as well but on multiple times of trying it is random. Sometimes English and sometimes in Dutch.

VERBOSE: Storing event: impression(RevenueCat.PaywallEvent.CreationData(id: 183B960F-7C43-4861-8603-8A120CF54CBE, date: 2024-04-11 13:58:47 +0000), RevenueCat.PaywallEvent.Data(offeringIdentifier: "Premium", paywallRevision: 3, sessionIdentifier: AE5D703D-9AAC-412D-A1C1-2348B5BDC814, displayMode: RevenueCat.PaywallViewMode.fullScreen, localeIdentifier: "en_001@rg=nlzzzz", darkMode: true))

[RCGitBot]

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

[akashpopat]

I get this sometimes

VERBOSE: Looking up localized configuration for ["en_001@rg=nlzzzz", "en-NL"], searching for ["en_001@rg=nlzzzz", "en", "en-NL", "en"] WARN: ⚠️ Failed looking up localization, using fallback: nl_NL

and this another

VERBOSE: Looking up localized configuration for ["en_001@rg=nlzzzz", "en-NL"], searching for ["en_001@rg=nlzzzz", "en", "en-NL", "en"] WARN: ⚠️ Failed looking up localization, using fallback: en_GB

[WesleyClarkRC]

Hi, we actually use the store account's region, Can you let me know what it is set to for that?

[akashpopat]

@WesleyClarkRC The store account is set to India

[WesleyClarkRC]

I apologize for the delay. Can you let me know which version of the SDK that you are using? This issue may have been resolved in a later version

[github-actions[bot]]

This issue has been automatically locked due to no recent activity after it was closed. Please open a new issue for related reports.