Ionic Pro Android Package

Now that I have one of my applications moved over to Ionic Pro, I have noticed the Android Release packaging is much larger in filesize and appears to not use the production mode. I do an ionic build --prod before I do git push ionic master. Then I select Android, Release, and my production security profile using the new Ionic Pro dashboard.The filesize is about double the size of a package built using ionic package build android --prod --release on Ionic Legacy cloud and it has that delayed white screen after the splash screen disappears but before the app begins responding. It seems like the --prod switch is missing…

Can you replicate with a new project created with ionic start blank blank?

If yes, this sounds like a case for support: (Keep us updated though please)

I am attempting to create a new test app to see if the issue happens on a newly created app but the new app won’t even build…

C:\Users\Greg\IonicProjects\andtest>git commit -m"Triggering a change" --no-gpg-sign
[master 48cafd6] Triggering a change
 1 file changed, 2 insertions(+)

C:\Users\Greg\IonicProjects\andtest>git push ionic master
Enter passphrase for key 'C:\Users\Greg\.ssh\ionic\260995_rsa':
Counting objects: 6, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (6/6), done.
Writing objects: 100% (6/6), 493 bytes | 493.00 KiB/s, done.
Total 6 (delta 5), reused 0 (delta 0)
remote: Creating build for master branch from 48cafd6 (Triggering a change).
remote: New commit or branch detected triggering new build...
Connection to closed by remote host.
fatal: The remote end hung up unexpectedly
error: error in sideband demultiplexer
   63f0d08..48cafd6  master -> master
error: failed to push some refs to ''

I even tried to run a new build of my existing app but get the same error. So, it is difficult to test this at the moment…

I can submit another post on this, but this has exposed another issue. When the remote build process hangs up like this, I have to make a bogus change/commit to be able to trigger another build…

In case this is relevant…

cli packages: (C:\Users\Greg\IonicProjects\bygm\node_modules)

@ionic/cli-utils  : 1.9.2
ionic (Ionic CLI) : 3.9.2

global packages:

Cordova CLI : 7.0.1

local packages:

@ionic/app-scripts : 1.3.7
Cordova Platforms  : android 6.2.3
Ionic Framework    : ionic-angular 3.2.1


Node : v6.11.0
npm  : 3.10.10
OS   : Windows 10

This seems to be a known issue:

Turns out the build continued on the remote server. So I was able to create a new APK after it finished. The resulting APK was over 7MB. That is double what I expected. But the splashscreen did not have a delay with a blank white screen. So I’ll create a new app and copy my existing code over. If the problem persists, I’ll check my code to see if something is suddenly blocking anything.

Thanks for the help!

1 Like

That is still fishy, especially if the local build really is only 3.5MB.
You should definitely already start a conversation with support about this.

I narrowed this down. If I create a blank project, I am getting a small production APK. I am now thinking the difference in my Ionic Legacy builds and the new Ionic Pro builds is the added plugins for such things as monitoring and deploy. I did not previous include those in my builds. So, I have concluded the new larger size was my own misunderstanding as it is not apples to apples in this case. The APK I mentioned being over 7MB was one that was created with the super template and not the blank one. I had been playing around with the super template and forgotten this when I created the test app for troubleshooting my issue. An APK built from the actual blank template was just over 3MB; which seems appropriate.

Thanks again!

1 Like