Files mistakenly identified as .so files
mourjan opened this issue · 2 comments
Good day,
I am trying to publish a release on play store but my app is flagged and rejected as not compliant with 64bit devices even though I am 100% sure that my app doesn't include any .so files.
The only reason that I could think of is that the play store compiler is mistakenly classifying the following files ending with _SO as C code .so files:
app\base\assets\io\michaelrocks\libphonenumber\android\data\PhoneNumberMetadataProto_SO
and
app\base\assets\io\michaelrocks\libphonenumber\android\data\ShortNumberMetadataProto_SO
which are metadata files for the country Somalia.
I am trying to resolve this issue with the play store support team but so far I'm suffering of their passive replies.
Do you have any idea? or were you able to release any 64bit compliant apps using the latest release of this libphonenumber fork?
Thank you for your time
Hi @mourjan,
Yes, we're using this for in production and everything is fine. Have you tried to unzip your apk and check the libs folder?
yes I did, and there is no lib folder.. anyways sorry to bother, I removed all libphonenumber uses and tries to post a release and still the same problem.. again.. sorry to bother