No. I clone the app fresh. didn’t change anything at all. The cli is also freshly upgraded and installed. I found this because my own apk is facing the same problem. I didn’t change build process for that one as well. That’s why i started a sample app to test.
I am already in the weekend, hopefully someone will be able to retest this on his machine and confirm that this is not a general problem but only on your machine.
You got me wrong. Ionic home page has very clear instruction on how to do that. And the video is from 2 years ago. The problem I’m facing now is that cli --release generates an corrupted apk, even for sample app directly from ionic repository without any code change. That means the build tool is bugged. All the developers out there with this version of ionic will not be able to publish their app until this issue is fixed.
Do you both also get a “corrupted” apk when building the blank template or is it only the super one?
How exactly do you define corrupted by the way? I never asked…
I only tried the “super” template. And my own app faces the same problem. The definition of “corrupted apk” is that when u click that apk in the android phone, the install will fail with a message “corrupted apk”. the build process reported no problem.
I tried the unzip thing it works. I got some webapp back. How am I supposed to compare? what should I look for? and I don’t really have uncorrupted apk though. since all the builds are corrupted.