-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Description
Describe the issue
Whenever I add Persian (Old) as a language in my app's Android Fastlane component on Hosted Weblate, it is created with 0 strings.
This seems similar to #12747, except that recreating the component doesn't work (already tried several times). Also waiting several days for the strings to hopefully show up doesn't work.
Strangely enough the Persian (Old) language works fine for the regular Android translation component.
I already tried
- I've read and searched the documentation.
- I've searched for similar filed issues in this repository.
Steps to reproduce the behavior
- Go to https://hosted.weblate.org/projects/catima/fastlane/
- Click "Operations" and "Start new translation"
- Choose Persian (Old)
Expected behavior
The language is filled with untranslated strings like all other languages are.
Screenshots
Exception traceback
How do you run Weblate?
weblate.org service
Weblate versions
No response
Weblate deploy checks
Additional context
This seems to either be unique to the Weblate version or my component, as a quick search shows me other applications with a functional Persian (Old) Fastlane component like https://hosted.weblate.org/projects/gramophone/fastlane/peo/