Rails部署Heroku后无法执行console、db:migrate问题求助

Hey there, let's tackle this tricky issue you're facing with your Rails app on Heroku. The fact that rolling back to an older Heroku build fixes things (but rolling back your code doesn't) tells us the problem isn't actually in your application code—it's likely related to dependencies, environment configuration, or Heroku's build environment. Here are some targeted troubleshooting steps to dig into:

1. Check for Unintended Gem Dependency Changes #

Even though you didn't touch auth-related code, discrepancies in your Gemfile.lock could be causing version mismatches for gems like warden-jwt-auth or its dependencies (like dry-configurable). Heroku uses your Gemfile.lock to install exact gem versions—if this file wasn't properly committed, or if it changed unexpectedly, Heroku might pull in incompatible versions.

• Action: Compare the Gemfile.lock from your working older build with the one you're trying to deploy now. Look for version changes in warden-jwt-auth, devise-jwt, and dry-configurable.
• Fix: Ensure Gemfile.lock is committed to Git, and if you find unintended version bumps, roll back that file to match the working build's version, then redeploy.

2. Verify Your Environment Variables #

The undefined method 'map' for nil:NilClass error suggests a configuration value that's supposed to be an array is coming up nil. warden-jwt-auth and devise-jwt rely on environment variables for critical settings like JWT audience, secret keys, or payload additions. If any of these variables were deleted or modified recently, it could break initialization.

• Action:
  • Run heroku config --app coco-sprint-3 to list current environment variables.
  • Check Heroku's Config Vars history (in your app's Dashboard > Settings) to see if any JWT-related variables were changed in the last two weeks.
• Fix: Restore any missing/modified variables to match the values from your working build. Also, add fallbacks in your initializer code to avoid nil values—for example:

  # In config/initializers/devise.rb
  config.jwt do |jwt|
    jwt.audience = ENV['JWT_AUDIENCE'] || 'your-app-default-audience'
    jwt.token_payload_additions = ENV['JWT_PAYLOAD_ADDITIONS']&.split(',') || []
  end
  

3. Clear Heroku's Build Cache #

Sometimes Heroku's build cache can get corrupted, leading to incomplete or mismatched gem installations. Even if your Gemfile.lock is correct, a bad cache might cause Heroku to install the wrong versions.

• Action:
  • Purge the build cache with: heroku builds:cache:purge --app coco-sprint-3
  • Redeploy your app with git push heroku dev:master
• Why this works: Purging the cache forces Heroku to do a fresh bundle install, ensuring all gems are installed exactly as specified in your Gemfile.lock.

4. Confirm Ruby and Buildpack Settings #

If you haven't explicitly set your Ruby version in Gemfile, Heroku might default to a newer version that has compatibility issues with your older gems (like warden-jwt-auth 0.3.6). Similarly, updates to Heroku's Ruby buildpack could introduce unexpected behavior.

• Action:
  • Add your exact Ruby version to Gemfile: ruby '2.4.4' (match the version from your working build)
  • Reset the buildpack to ensure you're using the official one: heroku buildpacks:set heroku/ruby --app coco-sprint-3
  • Commit these changes and redeploy.

5. Inspect the upcase_first_items Method Context #

Since the error happens in warden-jwt-auth's upcase_first_items method, let's confirm what value is coming in as nil. You can temporarily add debug code to your initializer to check the configuration values before they're passed to this method:

# Add this temporarily in config/initializers/devise.rb, before the JWT config
puts "Checking JWT config values:"
puts "Token payload additions: #{ENV['JWT_PAYLOAD_ADDITIONS']}"
puts "Audience: #{ENV['JWT_AUDIENCE']}"

Then run heroku run rails console --trace to see the output—this will tell you exactly which config is nil. Remember to remove this debug code after troubleshooting!

Since rolling back the Heroku build works, focusing on these non-code factors should lead you to the root cause. Let me know if any of these steps help narrow it down!

内容的提问来源于stack exchange，提问作者michaelsking1993