i also meet this problem when meteor run iOS,the error like this,can you give me some advice?
the error is in the attached picture.
You could try first to delete the .meteor/local/cordova-build/ folder.
Meteor will re-build it entirely when you launch the meteor run ios command.
This troubleshooting step resolves such issues most of the time.
Related
I've developed NextJS Project and already deployed to Vercel. Today when I updated my code and pushed to Github, and begin to deploy on Vercel, it shows me error. Build logs is attached in screenshot.
I've tried to delete node_modules, cleaning cache and all, but it didn't work.
The strange thing I'm not seeing any error and the reason for failing. In my local host, everything is working perfectly and no errors whatsoever, but Vercel is not giving me any error but just one notification:
Error: Command "npm run build" exited with 1
Can somebody let me know please what could be the reason of it? I can see there are some warnings but these warnings I suppose are not the main cause of this strange issue.
Thanks for reply. After spending 2-3 hours , I had intentionally put an error in my code, deleted one dependency from node_modules to see the build logs of Vercel. And removed a component from my code. So during deployment on Vercel of ERROR Code, it has shown me the errors indeed. And when I undo my changes and again started to deploy, that works like a charm. Not sure what was the reason still. Might be Vercel got some bugs at that period of time in my account. LOL
Removed one of the dependency from package.json
Then Deployed again to Vercel. Then it has shown me some error that makes sense.
Screenshot is attached.
Errors shown in Vercel
After fixing that error, it worked !
A development build works fine, but when I try a release build, it crashes immediately on start due to the Proguard.
I installed Crashlytics to try getting any error but it does not show any error (crashlytics works).
Might be important to add:
Just added Firebase and Facebook SDK.
How should the proguard.txt file look like?
Thank you in advance.
I am having trouble with my Meteor up, which is perfectly functional on localhost and on Modulus. When I try to deploy to a *.meteor.com instance the upload fails and I get a very cryptic error. The first line is the gist of it I guess
Error: not a tracked temp dir: /Users/valentin/.meteor/packages/velocity_core/.0.4.5.1dbi101++os.osx.x86_64+web.browser+web.cordova
I have tried installing and reinstalling velocity and tried deploying it with/without, the error persists. There are a bunch of hidden files in the folder the error points too. Deleting the one mention in the error simply creates new ones and throws an error again (naming a different folder though) Does anyone have an idea what it is about?
I had the same problem with another meteor package. It was solved after I delete everything from myapp/.meteor/local/ directory.
I think you can leave your local db there (myapp/.meteor/local/db), but I did not check if it still be working. (I've deleted all and probably it is the same as running meteor reset for your local project.)
OK, this seems to work: You have to manually downgrade the meteor version to 1.0.2.1, by editing .meteor/release and changing the version number. (There's a fix in dev, so it should be solved in a more complete fashion soon.)
Were you trying to deploy while your meteor app still ran in localhost? I faced the same problem for another package but resolved it by stopping my local meteor app first then deploy.
I'm trying to use the Artifactory-Plugin for bamboo to deploy a tar.gz into artifactory. However, after the build went successful, the plugin won't even try to deploy and instead just writes
Build failed, not deploying to Artifactory.
I have no idea, why it would think, that the build failed. Does anyone else know this problem and has a suggestion on how to solve it?
As I just noticed, there was actually an error in my build before, which I didn't see, because it wasn't critical and was well hidden in the hundreds of lines of log. After getting rid of that error, it worked.
BAP-195 Was filed for this issue.
In my case Artifactory plugin fails to deploy even if build scripts has failonerror="false".
I'm hoping someone has seen this error before. I'm using MSBuild with CruiseControl.Net to run the build for this project. When i run the build from the command prompt it actually builds without errors, but when i run it with CruiseControl.net i get the following error:
error MSB3025: The source file "C:\PE\PE-DEV\UIProjects\FolderName\" is actually a directory. The "Copy" task does not support copying directories.
6 Warning(s)
1 Error(s)
Time Elapsed 00:01:50.07
I have been doing a search and nothing with that error number shows up in google. Any help will be greatly appreciated.
<msbuild>
<executable>C:\Windows\Microsoft.NET\Framework\v3.5\MSBuild.exe</executable>
<workingDirectory>C:\PE\PE-DEV</workingDirectory>
<projectFile>Solution.sln</projectFile>
<buildArgs>/p:Configuration=DeployDev;BuildMode=DRYRUN;CreatePackage=true /fileLogger /verbosity:normal</buildArgs>
<targets>Build</targets>
<timeout>900</timeout>
<logger>C:\Program Files (x86)\CruiseControl.NET\server\ThoughtWorks.CruiseControl.MsBuild.dll</logger>
</msbuild>
This task works fine in other projects... If i use command prompt and run msbuild it works fine as well.
If it works when you run it from the command prompt (runs using your user account and permissions) and fails when running under CC (runs under whatever service account cc is running) it might be a permission issue. Try changing the account that cc.net runs under to your own account and see what happens.
This one was a tricky one, i was able to make the project work. The issue was the deploy build xml file had a typo somewhere and i was able to find the bug and fix it and now the project is building as it should.