.mo files don't seem to be allowed in packages of arch 'all'

[Daniel Holbach]

https://plus.google.com/u/0/+SzymonWaliczek/posts/P9Pupxb3hEv

<beuno> I guess .mo's are technically binaries
<popey> people re-submit their app as armhf or whatever to pass the tests, which seems flawed for qml based apps
<beuno> indeed
<dholbach> so the problem (I think is in _list_all_compiled_binaries()), python-magic seems to return 'application/octet-stream; charset=binary' for all .mo files

[costales (costales)]

In the manifiest.json, change:
   "architecture": "all",
by:
    "architecture": ["armhf", "i386", "amd64"],

that worked for me. A hug

[Simos Xenitellis  (simosx)]

I suppose that either the locale subdirectory should be excluded from testing for binary files.
or the "all" architecture should only contain the .po files that are compiled into .mo during installation (more chances for things to break).

[Olivier Tilloy (osomon)]

Can this be assigned and fixed? I can’t publish an update to an app of mine because of that bug. The workaround suggested by Marcos doesn’t look acceptable to me.

[Olivier Tilloy (osomon)]

Does the "Fix Committed" status mean that automatic review by the store will now work? If so, can I re-upload the same version that failed the check, or do I need to bump the version?

[Daniel Holbach (dholbach)]

Olivier. No, the bug status in this project is unrelated to when myapps pulls in a new version of it.

Martin: how often is this done?

[Daniel Holbach (dholbach)]

myapps should up to date now.

[Jamie Strandboge (jdstrand)]

This was fixed in 0.36.