Skip to content
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

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

Closed
birdofpreyru opened this issue Dec 20, 2023 · 7 comments
Labels
📦Bundler Platform: Android Android applications. Resolution: PR Submitted A pull request with a fix has been provided.

Comments

@birdofpreyru
Copy link
Contributor

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

@github-actions github-actions bot added Platform: Android Android applications. 📦Bundler Needs: Author Feedback Needs: Repro This issue could be improved with a clear list of steps to reproduce the issue. labels Dec 20, 2023
Copy link

⚠️ 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.

@pandaninjas
Copy link

Seems to be caused by 8c63e3f and 3052c41

@PierreCapo
Copy link

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.
    }

@GunnarAK
Copy link

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

pfrazee added a commit to bluesky-social/social-app that referenced this issue Dec 26, 2023
@cortinico cortinico added Resolution: PR Submitted A pull request with a fix has been provided. and removed Needs: Triage 🔍 Needs: Author Feedback Needs: Repro This issue could be improved with a clear list of steps to reproduce the issue. labels Dec 27, 2023
pfrazee added a commit to bluesky-social/social-app that referenced this issue Dec 29, 2023
RikSchefferAmsterdam pushed a commit to Amsterdam/amsterdam-app-frontend that referenced this issue Jan 3, 2024
Door een RN bug, faalt de Android release. Het probleem is dat er ongeldige language codes in een lijstje komen te staan, waardoor de validate van Google faalt. De oplossing is om een geldige language code expliciet te configureren.

Dit is een tijdelijke workaroun; de verwachting is dat dit gefixt wordt in de komende RN versie (facebook/react-native#42024) en dan kan dit weer weg.
pfrazee added a commit to bluesky-social/social-app that referenced this issue Jan 5, 2024
@rumfiske
Copy link

rumfiske commented Jan 5, 2024

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.

@rklomp
Copy link

rklomp commented Jan 5, 2024

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

@cortinico
Copy link
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
Labels
📦Bundler Platform: Android Android applications. Resolution: PR Submitted A pull request with a fix has been provided.
Projects
None yet
7 participants