heroku推动突然失败

本文介绍了heroku推动突然失败的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述 昨天晚上我推出了Herku，现在我的推动力正在失败，出现以下错误。 Heroku状态似乎没问题。我的heroku配置将RAILS_MASTER_KEY设置为我的master.key。这并没有帮助。

任何经验都可以......或者能够指向我的修复程序？

命令：'bin / rails runner'将％Q {heroku_detecting_active_storage_config =＃{Rails.application.config.active_storage.service}}''意外失败： remote：！缺少用于解密文件的加密密钥。向您的团队询问您的主密钥，并将其写入/tmp/build_996b65d7dc5d21b59fdaad7cc82a7aba/config/master.key 或将其放入ENV ['RAILS_MASTER_KEY']。

解决方案

参见： github/heroku/heroku-buildpack-ruby/pull/739 ，一个修复似乎被合并

I pushed out to heroku last night, and now today my pushes are failing with the following error. Heroku status appears to be ok. My heroku config has RAILS_MASTER_KEY set to my master.key. That did not help.

Any experience this...or, able to point me towards a fix?

Command: 'bin/rails runner "puts %Q{heroku_detecting_active_storage_config=#{Rails.application.config.active_storage.service}}"' failed unexpectedly: remote: ! Missing encryption key to decrypt file with. Ask your team for your master key and write it to /tmp/build_996b65d7dc5d21b59fdaad7cc82a7aba/config/master.key or put it in the ENV['RAILS_MASTER_KEY'].

解决方案

see : github/heroku/heroku-buildpack-ruby/pull/739, a fix seems to be merged