-
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
Push failed: Precompiling assets failed; Push rejected, failed to compile Ruby app #175
Comments
I don't think its an apple security check, I'm seeing the same thing on a secondary account with does not use tfa. |
Did you follow the 2 factor guide? https://github.com/fastlane/fastlane/blob/master/spaceship/README.md#2-step-verification |
My account does not use two step. I ended up using a fork with a different ruby version and that worked for me. |
Encountering same problem here, no 2FA, so suspect failing due to Ruby version as well. |
I checked the forks and found someone who had updated the ruby version. I THINK it was https://github.com/gustanas/boarding, but I'm not 100% positive. |
Awesome - will give that a shot - thanks! (update: thanks @hankinsoft - that did the trick indeed :) ) |
I have a similar issue, but give me this, help me pls, i think is the materialize gem |
I am not able to reproduce this at all. Heroku builds fine for me when creating a new instance. Is this still an issue for anyone? |
Yes. In the log there is a SASS syntax error that I have too (trying a rails app in dev mode): Invalid CSS after ".blue.": expected class name, was "#007bff" It doesn't compile the css. |
Hi All, I am getting this error in apache error log. Can someone please help me to resolve this: s3_website push --force The s3_website push --force is working fine when I am running this from CLI but from apache getting an error. |
I've got some kinda same issue, any idea ?
WARNING:
-----> Installing node-v22.11.0-linux-x64 ! |
I am recieving the following error when attempting to deploy with Heroku. I could be very wrong, but it seems to be an issue with Apple's security checks:
The log shows as follows:
The text was updated successfully, but these errors were encountered: