this was working fine till now but suddenly i got this error everytime on trigger toolkit while trying to forge as a web application
[ERROR] [Error 183] Cannot create a file when that file already exists: u'development\\web'
what could be wrong?
I have experienced this before on Windows. It has to do with the OS not being able to delete the folders for the last working environment. While I don't know why this happens, I can fix it by navigating to the /development folder and removing the /web folder. Once removed, you can run the process.
Related
I am downloading the file from the server in ionic via "Cordova-file-transfer" plugin. It works fine but when I kill app when downloading is in progress, then I reopen I start downloading, sometimes it gives "Could not create path to save downloaded file: You don’t have permission to save the file “folderName” in the folder “Documents”." error.
It's random issue.
I found the cause of the error. It has occurred when I update my app when any of the downloads are in the progress.
The solution for it. Create a file(mp3 file) again when the app restarts.
I use the command cordova serve to test the app in browser. But when I issue the command, I find all the code changes I made to the app has been disappeared include newly added js files etc. The app just got a complete reset. How can I avoid this and still use cordova serve command to test in browser? Thanks.
I got the issue resolved. It took sometime to figure out what is happening under the hood. As I was making changes directly in platform IOS directory, the cordova prepare or serve statement just replaces the code from the parent www folder.
To conclude, I have to make changes in root www folder and then issue the prepare/serve command that copies the code to the platform to test it out.
Using VS2015 RTM together with remotebuild#1.0.1, I have the problem that the incremental build is not working. The problem is that the changed web resources are not updated in the remote-builds directory on the Mac.
I assume the problem is that the uploaded upload_xxxx.tgz contains an empty www folder. Currently, I know 2 workarounds:
stop and restart the remotebuild
rebuild in Visual Studio
Both alternatives I do not like. They are easy to forget, and they take a lot of time.
Is there a solution to the problem - or a better workaround?
Until the product team fixes the bug, you can patch a nodejs file as follows:
Open File Explorer and Navigate to %APPDATA%\npm\node_modules\vs-tac\lib\
Replace file remoteBuild.js with one from here
Note: if you are not using default npm installation location, then to find out the directory where remoteBuild.js is located, run “npm config get prefix” (from a command prompt) to get the base of the directory, “C:\Users\AppData\Roaming\npm” for me, and then replace “\node_modules\vs-tac\lib\remoteBuild.js”.
So I think the iosRemoteLaunch.js also needs to be updated, to reflect the new method name of httpOptions vs httpOptionsAsync. If you dont, you end up getting this little gem:
TypeError: undefined is not a function
at invokeUrl (C:\Users\Nigel\AppData\Roaming\npm\node_modules\vs-tac\lib\iosRemoteLaunch.js:31:24)
at Object.remote.debug (C:\Users\Nigel\AppData\Roaming\npm\node_modules\vs-tac\lib\iosRemoteLaunch.js:57:12)
at C:\Users\Nigel\AppData\Roaming\npm\node_modules\vs-tac\emulator.js:37:27
at _fulfilled (C:\Users\Nigel\AppData\Roaming\npm\node_modules\vs-tac\node_modules\q\q.js:787:54)
at self.promiseDispatch.done (C:\Users\Nigel\AppData\Roaming\npm\node_modules\vs-tac\node_modules\q\q.js:816:30)
at Promise.promise.promiseDispatch (C:\Users\Nigel\AppData\Roaming\npm\node_modules\vs-tac\node_modules\q\q.js:749:13)
at C:\Users\Nigel\AppData\Roaming\npm\node_modules\vs-tac\node_modules\q\q.js:557:44
at flush (C:\Users\Nigel\AppData\Roaming\npm\node_modules\vs-tac\node_modules\q\q.js:108:17)
at process._tickCallback (node.js:355:11)
at Function.Module.runMain (module.js:503:11)
I am having trouble opening soap ui.
I have gone onto their website and downloaded SoapUI-5.0.0-mac-bin.zip from http://sourceforge.net/projects/soapui/files/soapui/5.0.0/
I have then unzipped it and have many different files but there is none with the icon to open the application. Someone said to open soapui-5.0.0.jar in the bin folder but when I do I get an error saying it cannot be launched and to check the console for possible error messages.
I cant seem to find the error message on the console - I have very limited technical ability I think haha I am running 10.9.2 apple OS if that helps at all.
I would attach screenshots but my reputation isn't good enough
In the bin folder there is a file named soapui.sh. To start SoapUI you can run this file from the terminal.
A possible easier way to run SoapUI is to download the SoapUI-5.0.0.dmg file from http://sourceforge.net/projects/soapui/files/soapui/5.0.0/. Running that file will start an installer for SoapUI. Once installed you will get an icon on your desktop that you can use to start SoapUI.
I just recently updated to the new version of forge, did not change anything on my setting and when I went to build my app I got an error that said it could not find the file..
so I made the copy of aapt file and put it in a directory where trigger said it was looking (the docs said trigger.io should have moved this file for me already but Im guessing it did not)
After I moved this file and ran the build again it looked like it found the file but now I get [Error 5] Access is denied.
I have checked the permissions on the folder as I am the admin and I have full permissions and I have launched trigger as an administrator and still nothing.
Thanks.
So again from what I can tell this is a problem with the python script that calls aapt.
When you look at the script it points only to aapt, this means its looking for a directory and not the aapt.exe file itself so the first thing that happens is
1) forge says it cant find the aapt directory, this is why you are getting the error message "cant find aapt tool"
2) by adding the directory you would get the access denied because then the script is trying to run all these commands on just the directory (this was the problem I ran into), by making the change below you do not need to create a directory, just leave everything how it is but add the exe and it should work
After doing some testing I found that by adding .exe to the pythong script in android_tasks.py the build was able to run successfully
if you look on line 35 of android_tasks.py and change 'appt' to 'appt.exe' it should build for you
this is what it looks like for me
path.join(sdk, 'build-tools', '*','aapt.exe')
Hope this helps