Remote Config HTTP errors for some RTL locales

Environment

• Android Studio version: Android Studio Chipmunk | 2021.2.1 Patch 1
• Firebase Component: Remote Config
• Component version: firebase-bom:30.1.0

The problem

I have an application that supports multiple locals languages and remote configurations work fine with any LTR language (EN, FR, etc) but it gives me FirebaseRemoteConfigServerException in all the RTL languages (I have tried Arabic, Urdu and Persian)

Steps to reproduce:

Just setting the apps locale to any RTL language will give this error. FirebaseRemoteConfigServerException: Fetch failed: The server returned an unexpected error. 400 bad request

Relevant Code:

private val remoteConfig by lazy {
       val settings = remoteConfigSettings {
           minimumFetchIntervalInSeconds = if (BuildConfig.DEBUG) {
               0
           } else {
               60 * 30
           }
       }
       val defaults = mutableMapOf<String, Any>(
           "a" to true,
           "b" to true
       )
       Firebase.remoteConfig.apply {
           setConfigSettingsAsync(settings)
           setDefaultsAsync(defaults)
       }
   }

   fun init() {
       loadSettings()
   }

   private fun loadSettings() {
       remoteConfig.fetchAndActivate()
           .addOnSuccessListener {
               Toast.makeText(context, "Done", Toast.LENGTH_SHORT).show()
           }.addOnFailureListener {
               Toast.makeText(context, "$it", Toast.LENGTH_SHORT).show()
           }
   }

and in my application

override fun onCreate() {
        super.onCreate()
        remoteConfigUtil.init()
        ...
    }

[danasilver]

Yep! You beat me to it @JonasTrikiSPV! 😄 This is fixed in Remote Config v21.1.1 and Firebase BOM v30.3.0. Thanks everyone.

[danasilver]

Thanks for your patience, everyone. We’ll be releasing the new version of the SDK with the fix next week and in the meantime have marked v21.1.0 as deprecated. We recommend using the previous version of Remote Config (v21.0.2) in the meantime, which does not contain this bug.

I’ll update this issue once that new version is live. Thanks!