Android String-Array not being recognized

**Describe the bug**

I'm using the Weblate to handle multiple projects translations and everything was working very well until we detected that the string-arrays were not being recognized by the Weblate.

**To Reproduce**

Steps to reproduce the behavior:

1. Create a component
2. Integrate with an Android Git Repo
3. Pull the default strings.xml
4. Ensure that your strings.xml have a string-array
Sample:

```

Mercury
Venus
Earth
Mars

```
5. Try to find the string `planets_array` in the Component source Translation
6. No string is found

**Expected behavior**

According to old issues opened here, the last version of the TTK should support string-arrays, and looks like a simple thing, because in the jsonNext format array strings are supported without a problem.

**Server configuration and status**

```
* Weblate: 4.1.1
* Django: 3.0.8
* siphashc: 1.3
* Whoosh: 2.7.4
* translate-toolkit: 3.0.0
* lxml: 4.5.2
* Pillow: 7.1.2
* bleach: 3.1.5
* python-dateutil: 2.8.1
* social-auth-core: 3.3.3
* social-auth-app-django: 3.4.0
* django-crispy-forms: 1.9.2
* oauthlib: 3.1.0
* django-compressor: 2.4
* djangorestframework: 3.11.0
* django-filter: 2.3.0
* django-appconf: 1.0.4
* user-agents: 2.1
* filelock: 3.0.12
* setuptools: 40.8.0
* jellyfish: 0.8.2
* openpyxl: 3.0.1
* celery: 4.4.7
* kombu: 4.6.11
* translation-finder: 2.1
* html2text: 2020.1.16
* pycairo: 1.16.2
* pygobject: 3.30.4
* diff-match-patch: 20181111
* requests: 2.24.0
* django-redis: 4.12.1
* hiredis: 1.1.0
* sentry_sdk: 0.15.1
* Cython: 0.29.21
* misaka: 2.1.1
* GitPython: 3.1.7
* borgbackup: 1.1.13
* pyparsing: 2.4.7
* Python: 3.7.3
* Git: 2.20.1
* psycopg2: 2.8.5
* psycopg2-binary: 2.8.5
* phply: 1.2.5
* chardet: 3.0.4
* ruamel.yaml: 0.16.10
* tesserocr: 2.5.1
* akismet: 1.1
* boto3: 1.14.33
* zeep: 3.4.0
* aeidon: 1.7.0
* iniparse: 0.5
* mysqlclient: 2.0.1
* Mercurial: 5.4.2
* git-svn: 2.20.1
* git-review: 1.28.0
* hub: 2.13.0
* lab: 0.16
* Redis server: 4.0.14
* PostgreSQL server: 11.5
* Database backends: django.db.backends.postgresql
* Cache backends: default:RedisCache, avatar:FileBasedCache
* Email setup: django.core.mail.backends.smtp.EmailBackend: smtp.mandrillapp.com
* OS encoding: filesystem=utf-8, default=utf-8
* Celery: redis://cache:6379/1, redis://cache:6379/1, regular
* Platform: Linux 4.14.146-120.181.amzn2.x86_64 (x86_64)

```

**Weblate deploy checks**

```
System check identified some issues:

WARNINGS:
?: (security.W004) You have not set a value for the SECURE_HSTS_SECONDS setting. If your entire site is served only over SSL, you may want to consider setting a value and enabling HTTP Strict Transport Security. Be sure to read the documentation first; enabling HSTS carelessly can cause serious, irreversible problems.
?: (security.W008) Your SECURE_SSL_REDIRECT setting is not set to True. Unless your site should be available over both SSL and non-SSL connections, you may want to either set this setting True or configure a load balancer or reverse-proxy server to redirect all connections to HTTPS.
?: (security.W012) SESSION_COOKIE_SECURE is not set to True. Using a secure-only session cookie makes it more difficult for network traffic sniffers to hijack user sessions.
?: (security.W018) You should not have DEBUG set to True in deployment.

INFOS:
?: (weblate.I021) Error collection is not set up, it is highly recommended for production use
HINT: https://docs.weblate.org/en/weblate-4.1.1/admin/install.html#collecting-errors
?: (weblate.I028) Backups are not configured, it is highly recommended for production use
HINT: https://docs.weblate.org/en/weblate-4.1.1/admin/backup.html

System check identified 6 issues (1 silenced).
```