How are you determining the size of the app? After compression of the zip file or before?
Also: make absolutely sure you aren't uploading /platforms or /plugins if your project originated from the CLI. That has often mucked things up in the past for other users.
hi cooper, it seems your account is the paid plan, the single product build subscription with a maximum app upload size of 100mb as seen here https://build.phonegap.com/plans
i had a look at that adobe id and it does not seem to have a full creative cloud subscription. is the account you are using different to the account you are using on this forum?
Hi Kerri, I'm zipping the www and the config.xml - not using any custom plugins in this build.
Sorry, this is the uncompressed size of the www folder and config.xml as according to my Mac! I've managed to squeeze the life out of it to get it down to 82MB which goes through okay.
Hi there, thanks for your reply! This is the account that I'm using for the app upload. It should be a standard all-in CC account as far as I'm aware.
I've posted this question because I don't seem to be able to get an app over ~90MB to successfully upload via any of the methods.
when using a git repo what does the error say?
It was going to a white screen but today appears to be happy with a smallish size app (150MB).
I've just tried using the repo method to get a 900MB test app into PGB under a CC account and it's doing what it was consistently for me over the last few days. It waits on 'updating' for a while then goes to a white screen with a url like this...
I suppose in answer to the original question, can I presume that there are no particular limits on each of the upload methods and if it's not accepting an app appropriately sized for the particular account type that it's an unexpected error?
Thanks for your help!
a smallish size app (150MB).
I couldn't help but grin when I read this.
Smallish when it's 15% of the maximum! But yes I take your point.
We generate offline resource apps for enterprise distribution, so they're full of videos. I'm trying to sell PGB build in as an alternative to continuous integration strategy but at the moment there's just not enough debugging information from the interface when it doesn't work so I might lose this one unfortunately.
if these are enterprise apps, are they also only used within the enterprise environment? If so, do they have to be offline (couldn't they just use the local wlan and a local web server)?
And if those videos must be available locally, must they be there when installing the app? Can't such enterprise have the users download the videos at first start, after which these are present in the device? (You would have to have such mechanism anyway, in case one of the videos is changed....or are you going to release a new app version every time a bit of content is changed?)
We have no desire to make 'apps' in this manner but a very particular set of circumstances for their use mean they're filled with resources and shipped off. So they're to be used in locations where's there's no connectivity.
But yes, a mechanism for downloading them at first launch would be a great workaround, it's just getting the time to work on it, as it wanders out of our skillset. Our previous solution of CI was great, allowing apps of any size, but needed constant maintenance and that team doesn't exist any more. We're looking for ways for front end devs to manage their own workflow.
It's certainly not optimal to create gigantic apps in this manner and if PhoneGap Build had an 'unlimited app size (fair use applies)' policy then I'd understand friction when approaching this way. My frustration is that as it stands, the published limit is 1GB and I can't get anything approaching that size through the process!
1 person found this helpful
This doesn't answer your current issue, but I thought I'd throw it out there for when it comes time to push updates: CodePush Supposedly it has no asset size limits while in beta, although you'd almost certainly end up paying something to host 1GB worth of assets when it exits beta. (See Frequently Asked Questions · CodePush )
This does seem like an issue that needs addressing ... it appears that Adobe Build simply crashes rather than an error message explaining why. Give what is being said here upgrading is not going to solve the issue either.
We are still trying to overcome loading larger zips into Adobe Build. Firstly we found that larger zips (say > 50MB) would crash out unless we use a VPN. But, when we have managed to fully upload a zip, using a VPN, we get a white screen with no error message (e.g. saying your zip/app is too large for your plan) at the end of the uploading once Adobe Build gets to "work". Anyway we have now upgraded to CC (InCopy Monthly) linked to the same AdobeID as we were using on Build ... the result same as before implying nothing to do with CreativeCloud licensing!
IIRC, you need to be subscribed to the full CC plan ($50/mo) in order to raise the limit to 1GB. Don't quote me on that, though.
However, it's entirely possible that the upload problems you hare having are due to some sort of configuration or issue somewhere downstream, especially if using a VPN somehow improves the situation. Perhaps the uploads are timing out due to slow transfer speeds? How fast are your uploads? What size of apps are you uploading?
Also, try using a Github repo -- unless you have a lot of bandwidth, I would wager that PGB can pull from a PGB repo faster than you can upload it directly to PGB. If timeouts are an issue, then that might help the situation.