Uncompile Development Asset Pipeline

To remove precompiled assets use:

rake assets:clean

What this basically does is remove the public/assets directory. You may need to include the RAILS_ENV variable if you need to run it for a certain environment.

Try using

rake assets:clobber

worked for me in rails 4

When you run the compile task locally (on your development machine) the assets are compiled in the Rails production environment, but are written to the public folder.

This means that even when you run in development mode it'll use the compiled assets instead of sending requests to the pipeline. This is normal behavor - requests only go to the pipeline if the file does not exists in public/assets.

The compile task should generally only be used when deploying, and on the remote (production) machine.

If you have compiled locally, you can delete all the files in the public/assets folder and development will behave as before. If you checked these files into source control you'll need to remove them.

Once removed things should work fine.sOne final tip: if this is an upgraded app check your config settings against those in the last section of the Rails asset pipeline guide.