Twitter is hard-coded in OAuth1 #2154
Comments
Thanks for tracking this down, @InfloErik. I fixed it on devel. |
Yep just caught this too - after many hours debugging an accounts package for Xero.com... When will this be released? |
We'll get it out in a patch release very soon (in the next few days). |
@InfloErik and @axwaxw, can one of you verify that 0.8.1.3-rc2 fixes the problem? You can run your app with it by running |
Hi, Sorry for the delay - yes this is working now and I have published a package for xero that is now working: https://github.com/axwaxw/accounts-xero Thanks! |
Sorry, about the delay. Yes, 0.8.1.3 has resolved the issue. Thank you for On Thu, May 22, 2014 at 12:00 AM, Emily Stark notifications@github.comwrote:
|
I have written an OAuth client for Fitbit, which was broken by Meteor 0.8.1. If your project does not use twitter, you will receive a "Service not configured" error when trying to connect to an OAuth server like Fitbit.
I have traced the error to line 14/15 in meteor/packages/oauth1/oauth1_server.js:
var callbackUrl = Meteor.absoluteUrl("_oauth/twitter?close&state=" +
query.state);
This issue is resolved when line 14/15 are changed to:
var callbackUrl = Meteor.absoluteUrl("_oauth/" + service.serviceName +
"?close&state=" + query.state);
The text was updated successfully, but these errors were encountered: