The primary intent of this plugin is to resolve issues commonly associated with Cordova CLI-compliant apps checked into source control and adds features (res/native) to help developers avoid having to check in the "platforms" folder as this can cause problems particularly if different members of a developer team are on a combination of OSX, Windows, or Linux.
MIT License
8
stars
12
forks
source link
Error: "file" argument must be a non-empty string #3
This just starting popping up last week for me. I have tried all sorts of node, npm, and cordova combinations and done a clean wipe of the environment with each iteration. I have settled back on my last known good configuration.
osx 10.13.2
node 8.7.0
npm 5.5.1
cordova 7.0.1
taco-team-build 0.2.4
cordova-ios 4.5.3
cordova-android 6.4.0
I am not using Visual Studio, rather VS Code. I am leveraging the taco team build in my gulp tasks and the cordova-plugin-vs-taco-support gets installed along with that plugin.
The steps required to trigger the error are generally:
Setup project (npm install, cordova prepare, etc)
Run a build that leverages taco-team-build configure() (set to cordova 7.0.1) and buildProject()
Successful result
Run same build again, but this time cordova-plugin-vs-taco-support is present from being auto-installed on the last run
Build fails with the error below
$ cordova prepare
Executing script found in plugin cordova-plugin-vs-taco-support for hook "before_prepare": plugins/cordova-plugin-vs-taco-support/hooks/hook-execute-bit-fix.js
Resolving module name for q => q
Error: "file" argument must be a non-empty string
If I $ cordova plugin rm cordova-plugin-vs-taco-support before attempting another cordova build I can get a successful build, but the scenario repeats and this error pops back up on any subsequent builds.
This just starting popping up last week for me. I have tried all sorts of node, npm, and cordova combinations and done a clean wipe of the environment with each iteration. I have settled back on my last known good configuration.
I am not using Visual Studio, rather VS Code. I am leveraging the taco team build in my gulp tasks and the cordova-plugin-vs-taco-support gets installed along with that plugin.
The steps required to trigger the error are generally:
If I
$ cordova plugin rm cordova-plugin-vs-taco-support
before attempting another cordova build I can get a successful build, but the scenario repeats and this error pops back up on any subsequent builds.