[AC-1552] Package file was not signed correctly when installing from Google PlayStore

A "Package file was not signed correctly message" comes on some devices while downloading from the app store. Some devices do not generate this error. I am re-submitting this issue because no Appcelerator supported solution is found. Today I have to update an app which was originally created by Ti 3.1.2 and therefore also signed with the tools that where available at that time. I had to update my app to Ti 3.3.0 because of iOS demands. I uploaded that new version to PlayStore and then the "not signed correctly" issue comes popping up over the last weeks. The 3.1.3 to 3.3.0 updata has already taken up a lot of time because a lot of Appcelerator downward incompatibilty issues (still not solved either so far...). This "not signed correctly" issue is also a downward incompatible issue. Appcelerator should broaden their attention to developers that create apps having a lifetime that exceeds the update frequency of Ti versions!! Nothing is mentioned in the Appcelerator documentation, some comments are found in the internet about this problem, and the most promising one is to manually sign the APK using "MDAwithRSA" signing algorithm instead of "SHA256withRSA". I did that but Google rejects the apk because the file is not "zip aligned". I can "zip align" it and hope for the best, but I did not find a lead about this zip aligning in the Appcelerator documentation nor in the internet also, so I have no guarantees that that is the way to go. Another thing I tested is to start a package action from my Macbook Pro and the same project from my iMac, and compare the both APK files. Result: the files are different... I use exactly the same source files and Ti software on both machines, so the resulting file should be the same. This is also not encouraging... Simply try-and-error actions using different apk signing actions is not the way to go. This is production hey! All of this is simply not acceptable. The Ti toolchain should take care of the whole process, instead of hiding behind "it is a Java tooling problem". I do not work with Java, I work with Titanium. I need a solution ASAP!! My customer is pressing me for a solution because he does not accept failing downloads from the PlayStore. Currently I am not able to generate new versions of the app that simply work.