I use visual studio 2015 to build mobile cordova useing remotebuild
but I got wanrning and error :
Warning PackageApplication is deprecated, use `xcodebuild -exportArchive` instead.
Error BLD102 Error : BLD00102 : No such file or directory 'xxx.plist'
Work around is to ignore the problem and locate build folder on mac its hold number that shown when you build set it to release and then go to the xcode open project fix errors and test it
Related
I have a project which was working fine till I was working on my older MacBook. I am now working on new MacBook and the same project gives me build error. My friend also works on the new MacBook with same configuration and os but he is able to build it successfully.
Error on my system is :
<unknown>:0: error: no such file or directory: '/Users/myuser/Library/Developer/Xcode/DerivedData/MyProject-dlhksnilacudcebpmorlzpzlkbid/Build/Intermediates.noindex/MyProject.build/Debug-iphoneos/MyProject.build/DerivedSources/CoreDataGenerated/Model/Model+CoreDataModel.swift'
Command CompileSwiftSources failed with a nonzero exit code
I have navigated to the path
'/Users/myuser/Library/Developer/Xcode/DerivedData/MyProject-dlhksnilacudcebpmorlzpzlkbid/Build/Intermediates.noindex/MyProject.build/Debug-iphoneos/MyProject.build/DerivedSources/CoreDataGenerated/Model'
There I found an unknown folder named "emplate" under which the required file exists.
I have searched the whole project, build settings, build phases, scripts but nowhere I found "emplate".
The CoreData entity Codegen has been specified as "Category/Extension".
Its better if you can install new version xcode or use same version of xcode which your friend is using, i think some path issues with your current xcode
I have got the solution for this. Renamed and Moved Xcode from Desktop to Applications folder, clean the project , removed DerivedData folder. And it works.
So I'm trying to get my react native software to run and it's popping up with an error saying The SDK directory 'C:\Program Files\Android\Android studio; ' does not exist. How can I fix this?
Lookup 2 places:
Possible duplicate of your question
React Native start Guide
If you installed all necessary things listed in guide just do:
react-native init YOURPROJECTNAME
and after build add local.properties file in android folder of your app.
It should contain line: sdk.dir = C:\\Users\\USERNAME\\AppData\\Local\\Android\\sdk
I am getting the following error when building the android project generated by Zebble for Xamarin.
I followed the steps in -READ-ME-NOW!!!!!!!!!!!! text file. When I did build the android project, this is error I got:
The command "Zebble" update-schema auto" exited with code -1.
Some additional error log I found from Build output:
EXEC : error : Failed to update the xml schema for intellisense: Failed to find the UWP exe file. Searched all EXE files inside: E:\Labs.NET\Xamarin\TestZebble\TestZebbleApp\Run\UWP\bin
Could you please tell me what has gone wrong.
Hope this helps:
Remove all zebble folders from nuget packages folder.
Remove the Run\Android\Zebble.exe file.
Update the zebble nuget to latest version.
Set the Android project as startup project.
From Build > Configuration Manager be sure that Build and Deploy are enabled for android project.
Rebuild the solution.
I am using the Jenkins Xcode plugin (https://wiki.jenkins-ci.org/display/JENKINS/Xcode+Plugin) to build an iOS application, however it hangs when running the following command on a project I have inherited from another developer:
$ /usr/bin/xcodebuild -list
It also hangs when I run this command manually from a terminal. Does anyone know what the cause may be? The warning displayed is also displayed on another project I have, but it does not hang in this case.
Running Xcode 6.1 on OS X 10.10
$ /usr/bin/xcodebuild -list
2014-11-12 04:47:21.234 xcodebuild[42642:1431240] [MT] DVTAssertions: Warning in /SourceCache/IDEFrameworks/IDEFrameworks-6604/IDEFoundation/SourceControl/Model/IDESourceControlManager.m:423
Details: Error Domain=com.apple.dt.IDESourceControlErrorDomain Code=-1 "Missing extension: public.vcs.subversion" UserInfo=0x7f9792309200 {NSLocalizedDescription=Missing extension: public.vcs.subversion}
Object: <IDESourceControlManager: 0x7f9792302860>
Method: -loadRepositories
Thread: <NSThread: 0x7f9790d2dbe0>{number = 1, name = main}
Please file a bug at http://bugreport.apple.com with this warning message and any useful information you can provide.
Information about project "DOHSmokefree":
Targets:
DOHSmokefree
DOHSmokefreeTests
Build Configurations:
Debug
Release
If no build configuration is specified and -scheme is not passed then "Release" is used.
TLDR; My solution: Mark the schemes as shared in XCode if building them from the command line as a different user, or without ever opening XCode on the build machine.
I was having this same problem, intermittently on our CI server. I came across this question. The accepted answer with the problem being an issue and fixing the SVN version did not work for me as the SVN being used on the CI server was the default SVN and it was, as mentioned, working intermittently.
What I finally noticed is that, between a working version and a non-working version the schemes were not being listed. I had recently upgraded a library on the project and that got me to thinking about the schemes. After realizing that schemes are stored locally per user, unless shared, the fix for me was to go into the scheme manager and mark the schemes as shared.
The problem apparently being that the CI server user never actually opened the project in Xcode, thus causing the list command to hang because there were no available schemes for the user to build.
The times when it had intermittently worked were times after, logged in as the CI server user, I had opened the project in Xcode to test the build process, thus creating the necessary schemes. Wiping the CI server or refactoring/adding schemes would cause the build to break until the project was reopened in Xcode in desperation.
I had a similar issue when updating to Xcode 6.1 while using a newer version of subversion on the command line.
Disabling Source Control in Xcode Preferences should do the trick.
If that isn't an option you might try replacing the subversion implementation inside Xcode as I have done, using this technique: Use SVN 1.7 in XCode 4.3+
Basically that would be the following steps:
This assumes you already have SVN 1.7 installed to /opt/subversion, you can get it from WANdisco: http://www.wandisco.com/subversion/download#osx
Now open the Terminal and get an elevated shell using sudo -s.
Then, cd to inside the XCode.app package, to where the SVN binaries are.
Make a backup directory and move the old SVN files into it
bash-3.2# mkdir bup
bash-3.2# mv svn* bup/
Lastly, symbolically link the new files into the package:
bash-3.2# ln -s /opt/subversion/bin/svn* ./
That’s it!
I have the same problem on OS X 10.10 with XCode 6.4，just close XCode's Source Control to solved this issue:
run XCode
open Menu: XCode -> Preferences...
Click "Source Control" Tab and uncheck "Enable Source Control"
/fatal error: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/lipo: can't open input file: /Users/zicjin/Library/Developer/Xcode/DerivedData/Baozou-iOS-gsgjiwiqjwffeheenpeffrqpytqx/Build/Intermediates/Baozou-iOS.build/Debug-iphoneos/Baozou-iOS.build/Objects-normal/armv7/Baozou-iOS (No such file or directory)
Use virtual machines to compiler does not complain, but switched to the real machine (iphone5s) runtime compilation error will be so
the sourcecode on github
Set your Build Active Architecture Only to YES, then it will work
This happened to me. I'm using a static library in my project and the issue was that I put the aggregate with the universal script as a target instead of using the library itself.
This happens when the universal script tries to generate the universal library but the library itself is not compiled, this script needs the library to be created before running.
In Xcode 7.2 I had to set Enable Bitcode to No in Build Settings > Build Options.
I ran into this problem while migrating my project from Xcode 5.0.2 to Xcode 6.1. These are the steps that I followed to get it working.
There was a warning generated - "Used recommended settings ... blah blah" - I allowed Xcode to change my project to whatever recommended settings there was.This did not stop the error though.
In TARGET -> BUILD SETTINGS -> BUILD ACTIVE ARCHITECTURES ONLY . I turned the flag to YES.
set TARGET -> BUILD SETTINGS -> Linking -> Other Linker Flags : $(OTHER_LDFLAGS)
After step 3 -I cleaned and then build my project and Whoa the error just vanished!!!!!
In your project > Build Phases
Place your lipo run script after CocoaPods scripts, your lipo will run after cocoapods finishes building its frameworks
As you can see here
This same thing happened to me in Xcode 12.4, in Mac os CataLina This issue was occured by Not Enough Storage, I have deleted derived and some other data, then Build for Diawi link was successfully created.