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: registry returned 404 for GET on https://registry.npmjs.org/com.jareddickson.cordova.tag-manager #33

Open
dittops opened this issue May 31, 2016 · 3 comments

Comments

@dittops
Copy link

dittops commented May 31, 2016

I'm trying to install the plugin. But i'm getting an 404 error and not able to install.

Error: Registry returned 404 for GET on https://registry.npmjs.org/com.jareddickson.cordova.tag-manager

Can anyone please help?

@catchmartin
Copy link

Had the same problem today but got around it as follows: cordova plugin add https://github.com/kraihn/cordova-plugin-tag-manager.git

@gitge
Copy link

gitge commented Nov 29, 2016

The npm package name was changed to 'cordova-plugin-tag-manager'.
This worked for me:

cordova add plugin cordova-plugin-tag-manager

@abinici
Copy link

abinici commented Oct 11, 2017

When installing this plugin with the command:

cordova add plugin cordova-plugin-tag-manager

I get the following error message during cordova prepare:

Discovered plugin "com.jareddickson.cordova.tag-manager" in config.xml. Adding it to the project

Failed to restore plugin "com.jareddickson.cordova.tag-manager" from config.xml. You might need to try adding it again. Error: Cannot find plugin.xml for plugin "com.jareddickson.cordova.tag-manager". Please try adding it again.

Then I tried changing the name of the plugin in config.xml from:

<plugin name="com.jareddickson.cordova.tag-manager" spec="~1.0.1" />

To:

<plugin name="cordova-plugin-tag-manager" spec="^1.0.1" />

And I did the same in package.json, changing from:

"com.jareddickson.cordova.tag-manager": "^1.0.1",

To

"cordova-plugin-tag-manager": "^1.0.1",

Which fixed the installation issue for me. There seems to be some discrepancy between the old and new name of the package.

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

4 participants