Skip to content

Locale resolves incorrectly when multiple regions are present #1910

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jeran opened this issue Apr 7, 2025 · 0 comments
Open

Locale resolves incorrectly when multiple regions are present #1910

jeran opened this issue Apr 7, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@jeran
Copy link

jeran commented Apr 7, 2025

Description
When using Paparazzi, locale resolution does not work correctly when multiple regions for the same language are present.

For example, if I have strings set up with fr translations and fr-rCA translations, then run a Paparazzi test with the fr-rCA translation configured, it will choose strings from fr instead of fr-rCA.

I believe this is actually a bug with Google's code and not Paparazzi's but I figured I'd open this issue just to let you know or in case I'm wrong. I've opened an issue with Google here: https://issuetracker.google.com/issues/408843420

Steps to Reproduce
You can check out the sample project here: https://github.com/jeran/paparazzi-locale-bug

Specifically the fr-rCA screenshot is incorrect.

This commit should explain the issue in further detail to the best of my knowledge.

Expected behavior
When choosing the fr-rCA locale, the screenshots should use the fr-rCA translations and not the fr translations.

Additional information:

  • Paparazzi Version: 1.3.5
  • OS: macOS 14.6.1 (23G93)
  • Compile SDK: 35
  • Gradle Version: 8.10.2
  • Android Gradle Plugin Version: 8.8.0
@jeran jeran added the bug Something isn't working label Apr 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant