-
Notifications
You must be signed in to change notification settings - Fork 578
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
Remote Config HTTP errors for some RTL locales #3757
Comments
I found a few problems with this issue:
|
Thanks for reporting, @ilyasipek. I was able to reproduce the same behavior, I'll notify an engineer to see what we can do here. |
Thanks for reporting the issue @ilyasipek! Based on the error it looks like it might be a server-side issue. We're investigating now and will update this thread when we know more. |
Thanks for replying @danasilver, any updates? My app is already in production with thousands of users! |
i have same error with my flutter app |
I also got same error when I tried Arabic and Persian. The error message didn't help so I decided to intercept app traffic with a sniffer. I found the following. RTL Request (Arabic)
The error message after above request:
LTR Request (English)
The response was successful for LTR request. I think the server cannot understand Arabic time. I hope this gets fixed soon. You can access the above requests here https://www.getpostman.com/collections/e8c2d62e5f9efcff8354 |
Looks like the |
Thanks for the reports and detailed debugging. That's an interesting observation about the |
We've identified the issue and are working on a fix in the SDK. |
Great, thanks. I hope soon. |
…. This makes sure that first-open time digits are not formatted to the local language characters. This change is a fix for #3757
…. This ensures that the english numerals in the timestamp are not converted to the local language numerals. This is a fix for #3757
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! |
The newly released |
Yep! You beat me to it @JonasTrikiSPV! 😄 This is fixed in Remote Config v21.1.1 and Firebase BOM v30.3.0. Thanks everyone. |
Does this upgrade need to be propagated manually to the Flutter/Dart packages? Or will it be pulled in automatically, without having to upgrade the Pub dependencies? |
@zmeggyesi |
Latest firebase_core 1.19.2 depends on Android SDK The problem was fixed in
|
Environment
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:
and in my application
The text was updated successfully, but these errors were encountered: