16 hours have passed, no response from Galaxy support. I’ve got pressure from clients, asking me why I can’t deploy, and all I can do is shrug. I understand a 24-hr turnaround time is reasonable, but maybe MDG should keep a close eye out for emails that could potentially be bugs in Galaxy, and address those ASAP?

EDIT: Ok, the 24-hr turnaround doesn’t happen till Sept 1st. However, I feel like there are two levels of support for any given SaaS:

Support for the people who are confused and need help with basic stuff.

One business day turnaround support for when things are broken that are expected to work. This is just going on the principle that, if a customer is paying for something, they do expect it to work. IMO bugs shouldn’t fall under the support level above, where a customer could wait 2-3 days to hear back.

UPDATE: I’m betting this is a meteor CLI tool bug (which generates the bundles). I can replicate this same issue on an EC2 instance.

Some parts of it seem to be hosted on S3, could it be that you might include a newer version in your package file which is still available on S3? Maybe it’s some kind of a version conflict which you can override to make your app working again?