-
Notifications
You must be signed in to change notification settings - Fork 21
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
Failed to install 'cordova-spotify':Error: spawn EACCES #32
Comments
Any more detail about which file is accessed? This is probably a duplicate of #31. |
I'm not 100% sure but I'm assuming it has to do with creating the folders (plugins/cordova-spotify/src/android/spotify-auth and plugins/cordova-spotify/src/android/spotify-sdk) in the install-android.sh since it aborts before these folders get created |
Tried to install it from local file system with a modified install script, but I keep running into erros with missing files Probably have to wait until you convert the install scripts to JS, I would be glad to help, but I'm kind of a noob when it comes to Android Development ... :( |
Just something that came to my mind right now: did you ensure that there are no spaces in the projecg folder path? I might have fixed these issues just now, but we've had problems with that in the past. Could you try installing the plugin from git directly? I just made a path-related commit that isn't published yet. |
One thing, could you create a new release from the current develop branch? With the current status it seems to work, but I can only use it as a plugin correctly with a release version. Thanks in advance! |
I experience the same. Installing with |
@andreasseiler @Remco75 Got the new release out. |
So everything seems to be working now? I'll just close this. Feel free to reopen if the problem persists. :) |
Hi,
I'm trying to install your plugin in my Meteor App (current Meteor version 1.5.1) and it gives me the above error ... Failed to install 'cordova-spotify':Error: spawn EACCES. I'm running Ubuntu 16.04 LTS.
Did anyone else run into this error? I tried modifying the permissions in all related folders.
Regards,
Andi
The text was updated successfully, but these errors were encountered: