-
Notifications
You must be signed in to change notification settings - Fork 191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
new heroku deployments immediately crashing #212
Comments
Some additional output from the Heroku logs:
|
@33b5e5 Hey! It looks like your "worker dyno" is on but your "web dyno" is off. Can you make sure your heroic dashboard looks like the following image? The web dyno should be the only one that is on |
Thanks for the response @joshdholtz. I admittedly was fiddling with the dyno settings while trying to troubleshoot, but setting them back to the defaults as pictured and restarting the dynos results in the same error. I also tried deploying to a new app and not fiddling with the Heroku settings, but it's the same.
|
This is very strange 🤔 I literally created a new app from the Heroku button on the README about 15 minutes before you posted your issue. Did you deploy with the Heroku button? |
Yep! |
What environment variables did you all fill out when that form popped up? I only filled out user, password, and app id 🤔 |
ITC_USER, ITC_PASSWORD, ITC_APP_ID, ITC_APP_TESTER_GROUPS. So it looks like adding the tester group is the only difference. |
I tried removing ITC_APP_TESTER_GROUPS from the Heroku settings, then restarted all dynos, but no change. I'm tempted to try the "Update to a new version" (https://github.com/fastlane/boarding#recommended-using-the-terminal) steps just to see if it un-wedges anything. |
Does your |
@33b5e5 I think I know the issue. Let me push a change real quickly 😊 |
It's working fine now. Thank you very much! |
@33b5e5 Woot! Happy fastlaning 🚀 |
I've tried deploying twice with the same results. I'm not sure what other information is helpful, so please let me know what else I can provide. I was able to deploy to Azure successfully using the same underlying app and iTC access.
The text was updated successfully, but these errors were encountered: