I’m having some trouble with a CrowdIn workflow I’m trying to finalise for a mobile app project. The CrowdIn project that I’ve set up, is intended for providing localizations for an Android and iOS app. 
I’ve recently put together a workflow that enables our Design Team 
to push source string changes through to CrowdIn using the Figma plugin. All strings that are uploaded are added to a Strings Vault file (.csv) in the Sources section of our project. This part works wonderfully. 
All required source strings end up in our CrowdIn project, including context, labels, etc. and can be translated into the target languages without issue. 
In order to get our translation changes pushed through to our Android and iOS codebases, I have added the GitHub VCS integration to our CrowdIn project and have configured it to use the “Target file bundles mode” to enable me to export Android XML and iOS Strings format files and push them to the appropriate codebases. Again, this works great… Except for one thing (and I hope that I’m simply missing something obvious):
The “Resulting file pattern” field of the “Branch Configuration” for my Android target file bundle doesn’t seem to have a way for me to remove or omit the -en from the end of the values-en export directory. Android treats the values directory as the default language, which in my case, is English (as is, our source language in our CrowdIn project).
Here’s a screenshot of where I got a bit stuck: 
I’ve tried working with different placeholders, like %android_code%, %two_letters_code%, etc. with no success. The closest I managed to get was using %two_letters_code%, but the -en predicament remained.
I then tried overriding the “English” language in the project’s “Language Mapping” section (in “Settings” > “Languages”) to try and make the English language placeholder for %android_code% return an empty value, but the Language Mapping UI wouldn’t let me do that. So I then tried the following:
Finally, using this rather hacky method, I managed to get the output that I required (and I’d imagine everyone(?) using Bundles via VCS integration for managing their localizations). 
Long-winded post, though I want it to be easily searchable 
for those who are encountering the same issue. I spent more time than I’d have liked to, on finding this method of achieving the desired output. 
Is there a better way to achieve this output, that I’ve completely missed? I’ve pored over countless CrowdIn articles, blogs, guides, forums, docs, code, third-party guides, videos, etc. and managed to turn up nothing that worked. 
so far it’s working well! 
I’d like to add an automated pre-translation step that uses both Translation Memory 
and the Machine Translation 
engine to seed translations (as outlined in 
I can imagine that this will reduce the initial (manual) translation step of our localization workflow.
during the design of this localization workflow! I found that in the past, I needn’t add the source language to the list of target languages, because the source strings were all procured from the same repositories that the translations were getting sent through to. This was utilising the “Source and translation files mode” of VCS integration (
(I hope that makes as much sense to you as it did in my head! 
)
The idea here is that the designers can build UIs that contain strings, that can then be sent through to CrowdIn with unified key/identifier naming, and once translated, those strings can then be pushed through to the app repositories (Android and iOS) in the formats they require. 
The keys used in both codebases would remain uniformed, making things more manageable for the Engineering Teams 
working on these projects. 
Since the strings are sourced from Figma (in our case), the source strings are not present in the destination project repositories, so the source strings must be pushed through alongside the target language strings. 
