Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: Already registered the google OAuth service #40

Closed
marcoschwartz opened this issue Feb 16, 2017 · 15 comments
Closed

Error: Already registered the google OAuth service #40

marcoschwartz opened this issue Feb 16, 2017 · 15 comments

Comments

@marcoschwartz
Copy link

Hello,

I got the following error since updating Meteor to 1.4.3.1:

Error: Already registered the google OAuth service

I guess it's coming from the fact that Meteor now uses google-oauth and not just google, and the google module therefore is installed two times... how to fix this? Thanks!

@nunohvidal
Copy link

+1

however I got this error today when I updated Meteor to 1.4.2.7

@nunohvidal
Copy link

nunohvidal commented Feb 17, 2017

@marcoschwartz I got around the issue by using a local version of the package and removing one of it's dependencies - google

Just add the package locally (see how below if you're not sure how to) and manually edit package.js file. What we need to change is in the call Package.on_use and change the google in api.use to google-oauth

From this

if (api.versionsFrom) {
    api.versionsFrom('0.9.0');
    api.use(['http', 'livedata', 'google', 'mrt:q@1.0.1', 'accounts-base', 'underscore']);
  }

to look like this

if (api.versionsFrom) {
    api.versionsFrom('0.9.0');
    api.use(['http', 'livedata', 'google-oauth', 'mrt:q@1.0.1', 'accounts-base', 'underscore']);
  }

I also changed the version in Package.describe from 1.0.3 to 1.0.3_1 so I know for sure I'm using the local package.

To use a local version of the package, download this package ZIP and unzip it to a folder names packages inside the folder of your Meteor app.
Then do the changes described above, and add the package again
meteor add percolate:google-api

if you changed the version as well you should get

meteor add percolate:google-api
percolate:google-api without a version constraint has already been added.

Changes to your project's package version selections:

google                removed from your project
percolate:google-api  upgraded from 1.0.3 to 1.0.3_1

allenfuller added a commit to allenfuller/meteor-google-api that referenced this issue Feb 20, 2017
Meteor recently updated their package naming from `google` to `google-oauth` which resulted in an error per [a href="percolatestudio#40 issue[/a]. This update resolves that issue.
@allenfuller
Copy link

I've just submitted a pull request to resolve this issue. Hopefully it works and the maintainers merge it in...

@nunohvidal
Copy link

thanks @allenfuller

@allenfuller
Copy link

allenfuller commented Mar 2, 2017

Just checking in to see if anyone has heard any updates on this, or found another resolution?

@tmeasday
Copy link
Member

tmeasday commented Mar 3, 2017

Hi, we are no longer using this project, and thus it is unmaintained. Is someone interested in taking over maintenance?

@ro6
Copy link
Collaborator

ro6 commented Mar 16, 2017

@tmeasday I can't put a lot of time into it, but I could take over maintaining the basics, merging PRs etc...

ro6 added a commit to ro6/meteor-google-api that referenced this issue Mar 16, 2017
ro6 added a commit to ro6/meteor-google-api that referenced this issue Mar 16, 2017
ro6 added a commit to ro6/meteor-google-api that referenced this issue Mar 16, 2017
ro6 added a commit to ro6/meteor-google-api that referenced this issue Mar 16, 2017
@tmeasday
Copy link
Member

@ro6 I'll give you GH access and permission to publish, use wisely :)

@tmeasday
Copy link
Member

@ro6 what is your MD username?

@merlinstardust
Copy link

@tmeasday do you have a recommendation as to another library/package that we should use?

@tmeasday
Copy link
Member

No, sorry @merlinpatt

@ro6
Copy link
Collaborator

ro6 commented Mar 22, 2017

@tmeasday ro6, same as GitHub

@tmeasday
Copy link
Member

@ro6, added as a maintainer

@adamgins
Copy link

@ro6 wondering if you still planned to release your pull request?

ro6 added a commit that referenced this issue Apr 12, 2017
@ro6
Copy link
Collaborator

ro6 commented Apr 12, 2017

@adamgins Added the fix and released. Closing this for now, please let me know if you have any issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants