The output from the failed build logs is the exact same and posted below. The only thing that changes when I upload a build that does correctly build, is that I might add or remove an extraneous space from a .scss file or something. That is just so that git will recognize it as versioned, and allow it to be uploaded to ionic pro again.
Failed build output:
Running with gitlab-ci-multi-runner 9.1.0 (0118d89)
on Prod Snapshot Builds 1 (c9648220)
Using Shell executor...
Running on ip-10-2-78-101...
Fetching changes...
Removing .bowerrc
Removing .editorconfig
Removing .gitignore
Removing .io-config.json
Removing .project
Removing .settings/
Removing README.md
Removing bower.json
Removing config.xml
Removing gulpfile.js
Removing hooks/
Removing ionic.config.json
Removing package-lock.json
Removing package.json
Removing relivvitvine/
Removing resources/
Removing scss/
Removing www/
error: cache entry has null sha1: relivvitvine
fatal: Could not write new index file.
ERROR: Job failed: exit status 1
It does build after several tries of uploading the exact same project, but it really is a pain.
this is most likely due to the work they are doing on the 400: bad address issue on Androids.
and it is probably not going to be an issue going forward.
I happen to like Pro, because I can let the client set the app and get feed back without having to go into production.