Skip to content

[v0.73.1][Android] Google.Play rejects app bundles because it "targets the following unrecognized languages: cb, fb" #42024

Closed

Description

@birdofpreyru

Description

I'm getting the following error when uploading an app bundle, built with RN v0.73, to Google.Play (it is an existing project, that had no such issue before):
image

Googling for the error message, I came across this StackOverflow thread, which is old, and is not related to RN, but it mentions

I think it's because a folder named 'values-fb', that's a folder which have some files, usually used to translations

So, I've checked whether my project has some folders with names ending with -cb and -fb suffixes, and I found them in RN package, and then in intermediate built artifacts:
image
image

I guess, it requires a fix on RN side, renaming those folders (although the very error message suggests a workaround via resConfigs Gradle prop)?

Steps to reproduce

N/A

React Native Version

0.73.1

Affected Platforms

Other (please specify)

Output of npx react-native info

N/A

Stacktrace or Logs

N/A

Reproducer

N/A

Screenshots and Videos

No response

Activity

  1. github-actions commented on Dec 20, 2023

    @github-actions
    ⚠️ Missing Reproducible Example
    ℹ️ We could not detect a reproducible example in your issue report. Please provide either:
    • If your bug is UI related: a Snack
    • If your bug is build/update related: use our Reproducer Template. A reproducer needs to be in a GitHub repository under your username.
  2. pandaninjas commented on Dec 21, 2023

    @pandaninjas

    Seems to be caused by 8c63e3f and 3052c41

  3. PierreCapo commented on Dec 21, 2023

    @PierreCapo

    Workaround for now that fixes the problem:

    1. Go to android/app/build.gradle
    2. In the defaultConfig section, do the following:
        defaultConfig {
             // previous code here...
             
            // Workaround for https://github.com/facebook/react-native/issues/42024
            resConfigs "en", "fr", "es" // change this line by the languages you support within your app.
        }
    
  4. GunnarAK commented on Dec 22, 2023

    @GunnarAK

    Next release of RN 0.73 will contain the fix for this issue.

  5. added a commit that references this issue on Jan 5, 2024
  6. charlesoestergaard commented on Jan 5, 2024

    @charlesoestergaard

    How can I resolve the issue using the Expo bare workflow without modifying any files in the /android directory? I'm concerned that changes made to the /android folder won't be reflected in the build since Expo constructs this folder during the build process. I'm looking for solutions that won't involve alterations to the Android-specific files.

  7. rklomp commented on Jan 5, 2024

    @rklomp

    How can I resolve the issue using the Expo bare workflow without modifying any files in the /android directory? I'm concerned that changes made to the /android folder won't be reflected in the build since Expo constructs this folder during the build process. I'm looking for solutions that won't involve alterations to the Android-specific files.

    See expo/expo#26218

  8. cortinico commented on Jan 22, 2024

    @cortinico
    Contributor

    Closing as fixed in 0.73.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions