You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[v0.73.1][Android] Google.Play rejects app bundles because it "targets the following unrecognized languages: cb, fb" #42024
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):
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:
I guess, it requires a fix on RN side, renaming those folders (although the very error message suggests a workaround via resConfigs Gradle prop)?
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.
}
Reacted by Swain, ILKERC, Victor P., Dionísio Malteso and QuangV
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.
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.
Activity
github-actions commentedon Dec 20, 2023
pandaninjas commentedon Dec 21, 2023
Seems to be caused by 8c63e3f and 3052c41
PierreCapo commentedon Dec 21, 2023
Workaround for now that fixes the problem:
android/app/build.gradledefaultConfigsection, do the following:GunnarAK commentedon Dec 22, 2023
Next release of RN 0.73 will contain the fix for this issue.
Hackfix to react/react-native#42024
Merged PR 19636: Fix Android release
Hackfix to react/react-native#42024
charlesoestergaard commentedon 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 commentedon Jan 5, 2024
See expo/expo#26218
cortinico commentedon Jan 22, 2024
Closing as fixed in 0.73.2