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
Our app is targeting Android 13(targetSdk 33) and we are forcing the app to be Persian (an rtl language) at first, but users can change to English in settings. Before targeting API level 33 chucker showed its views LTR when our app was RTL. But now it is RTL and that is not convenient.
I guess that is because we are calling AppCompatDelegate.setApplicationLocales(LocaleList) in new changes. Somehow I want to force Chucker to be LTR.
Is there any way to force it to be LTR? or It can be added?
💣 Steps to reproduce
Create a sample app force app language in application class onCreate to rtl language like: AppCompatDelegate.setApplicationLocales(LocaleListCompat.forLanguageTags("fa"))
go to chucker and it is RTL
🔧 Expected behavior
Set to Be Ltr with ChuckerInterceptor
📷 Screenshots
📱 Tech info
tested on android 13 and 14 device
📄 Additional context
The text was updated successfully, but these errors were encountered:
✍️ Describe the bug
Our app is targeting Android 13(targetSdk 33) and we are forcing the app to be Persian (an rtl language) at first, but users can change to English in settings. Before targeting API level 33 chucker showed its views LTR when our app was RTL. But now it is RTL and that is not convenient.
I guess that is because we are calling
AppCompatDelegate.setApplicationLocales(LocaleList)
in new changes. Somehow I want to force Chucker to be LTR.Is there any way to force it to be LTR? or It can be added?
💣 Steps to reproduce
Create a sample app force app language in application class onCreate to rtl language like:
AppCompatDelegate.setApplicationLocales(LocaleListCompat.forLanguageTags("fa"))
go to chucker and it is RTL
🔧 Expected behavior
Set to Be Ltr with ChuckerInterceptor
📷 Screenshots
📱 Tech info
tested on android 13 and 14 device
📄 Additional context
The text was updated successfully, but these errors were encountered: