Login with Fb worked fine when I was hosting locally but I'm having issues now that it's on heroku. I already updated the domain on FB associated with my app from localhost:3000 to myapp.herokuapp.com
I've also checked out this thread omniauth with facebook not working on production and tried adding the 'client_options' hash to my initializer file and am still having trouble. I don't know if this is relevant, but when I try and navigate to /usr/lib/ssl/certs/ca-certificates.crt I get a "No such file or directory" error.
When I click login to FB on my app (http://playedbyme.herokuapp.com/) I get a callback error.
Here is what my OmniAuth initializer file looks like:
Rails.application.config.middleware.use OmniAuth::Builder do
provider :facebook, 'MY_APP_ID', 'MY_SECRET_KEY',
{:client_options => {:ssl => {:ca_file => '/usr/lib/ssl/certs/ca-certificates.crt'}}}
end
UPDATE: I think that it's some sort of issue with my database. When I run "heroku run rake db:migrate" I get an error
rake aborted!
An error has occurred, this and all later migrations canceled:
PG::Error: ERROR: column "id" of relation "parties" already exists
: ALTER TABLE "parties" RENAME COLUMN "party_id" TO "id"
But, I don't have a column named party_id in my Parties table