Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 3978482
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 20, 20262026-05-20T05:03:10+00:00 2026-05-20T05:03:10+00:00

I’m getting this error with the Paperclip gem. NoMethodError (You have a nil object

  • 0

I’m getting this error with the Paperclip gem.

NoMethodError (You have a nil object when you didn't expect it!
You might have expected an instance of Array.
The error occurred while evaluating nil.size):
  paperclip (2.3.8) lib/paperclip/attachment.rb:104:in `assign'

How can I debug this, seeing as though it’s in a gem? If this was my code I would place a few puts to see what’s going on, but I can’t do that here. I’m using Rails 3.0.1

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-20T05:03:11+00:00Added an answer on May 20, 2026 at 5:03 am

    here’s my best shot.

    • Open one of your controllers and add a debugger line to it. We need the debugger to kick in to set the breakpoint
    • Next run rails --debug
    • navigate to the page / controller with the breakpoint
    • the debugger console will appear.
    • run Gem.find_files("attachment.rb") <- I’ll call $GEM_ROOT to the path that this returns
    • run list $GEM_ROOT/lib/paperclip/attachment.rb:104 – this will show the code around the area where the error occurred.
    • run b $GEM_ROOT/lib/paperclip/attachment.rb:$LINE – replace $LINE for a good candidate for the breakpoint.
    • run cont
    • hit the page / action that causes the error, and the debug console should open at the break point.

    I think there must be a way to get the path to the gem file programmatically, but I have no idea how to do it 🙁

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

No related questions found

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.