I tried to build my project after updating my unity to version 2019.1. Unfortunately, it says Gradle build failed. I can't build that as internal because it's not supported anymore.
Your project folder probably in the desktop or in a non-ASCI character folder. Just make a new folder in C:// and put your project in it then re-open the project and compile.
Related
I have a brand new Visual Studio 2015 project stored in a TFS Git repo. I've configured a build using the standard Default Git build template. The new project builds locally just fine, but fails during the TFS Build with the following error:
This project references NuGet package(s) that are missing on this computer. Use NuGet Package Restore to download them. For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is ..\packages\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.1.0.0\build\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.props.
When TFS first creates your Git repository, it includes a default .gitIgnore file which "hides" certain files from your your (Pending) Changes window. One of the wildcard based exclusions in the default .gitIgnore file specifically excludes any files from being checked in under any folder that includes "build/" which includes this specific file. For now, I've commented out that exclusion in the file, and now it shows up in my (pending) Changes window.
First I cloned github repository on my local machine. Then open Existing Android Studio project and selected "example" folder from the repo on the local machine. Then I got:
There were two events log :
1. Unlinked Gradle project?
2. Android Framework detected
When I clicked on the link for linking to Gradle "Improt project from gradle" dialogue box opened and then I got "Resolve Error" dialogue box with error:
Could not download artifact 'gradle.jar (com.android.tools.build:gradle:0.14.4)': No cached version available for offline mode
My Android Studio version:
I have searched on the Google and stack Overflow, but can't find appropriate solution.
You can't import the Swipecards repo in Android Studio 1.0.1 using gradle.
This project is using this unsupported version of gradle-plugin.
classpath 'com.android.tools.build:gradle:0.14.4'
I suggest you cloning the repo locally changing these values: classpath 'com.android.tools.build:gradle:1.0.0' in build.gradle distributionUrl=http\://services.gradle.org/distributions/gradle-2.2.1-all.zip in gradle/wrapper/gradle-wrapper.properties
When I try to Archive my Xcode project, it can no longer find the .h files from the subproject in the same workspace. It works fine otherwise.
Any ideas on how to fix it?
It turns out I had created a new build configuration on the main project and that same build configuration didn't exist in the subproject, so when it went to archive it couldn't find the .h files that had been copied over.
I added the same build configuration to the subproject and it archived just fine.
I have a project embed another project, and the xcode GUI build was successful, but in command line xcodebuild failed as such.
fatal error: 'OHAttributedLabel/OHAttributedLabel.h' file not found
#import <OHAttributedLabel/OHAttributedLabel.h>
^
1 error generated.
but I had this in the project HEADER SEARCH PATH (where the h is located)
${PROJECT_DIR}/MyProject/Vendor/OHAttributedLabel/Source
the problem is the header is located in the "OHAttributedLabel/Source" folder, while the import statement is looking for header under OHAttributedLabel folder, I don't want to touch the embedded project directory structure, what can I do in this case?
The best way is to modify the embedded project to publish the header files:
Select the embedded project in xCode
Select the applicable target.
Click on the build phases
Expand "Copy Headers" section and add OHAttributedLabel.h file.
Select your main project
Select the applicable target.
Click on build phases.
Click on Target dependencies.
Make sure that the embedded project is added as a dependency.
Try to run the app
If the above doesn't work double-check the order of the build phases. E.g. make sure that the "Target Dependencies" build phase is before "Compile sources".
We have a TFS build definition set up where we pass the following extra MSBuild arguments in:
/p:DeployOnBuild=true;DeployTarget=PipelinePreDeployCopyAllFilesToOneFolder;_PackageTempDir="\\server\build";AutoParameterizationWebConfigConnectionStrings=false
This has been detailed elsewhere as a way to have the published files copied to a specific location instead of generating a deploy package.
This unfortunately does not work on our build server, however if I run the exact same msbuild command line as called by TFS on my dev machine then it works perfectly and copies the output files to the location.
I have checked the log file and there is no errors, it just seems to completely skip the publish/deploy step.
Done building target "_BuiltWebOutputGroupOutput" in project "xyz.csproj".
Target "PrepareForRun" in file "c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets" from project "C:\Builds\2\xyz\xyz build\Sources\xyz.Web\xyz.Web.csproj" (target "CoreBuild" depends on it):
whereas on my local machine, after _BuiltWebOutputGroupOutput target is run the package target runs and deploys the files correctly.
I have tried using different paths and even setting the properties in the project file but it seems to make no difference. My local solution and project files are the same as in the repository that the TFS build is using. Is there something config related on our build server or with the build agent that would cause the packaging target not to run?
I was having a similar problem today and found a fix so it maybe worth a look for you. Here