Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
build fail due to task always checking default outputpath
See original GitHub issuesetResultFailed('The Unity build task finished without results. Check editor logs for details.');
in unity-build.ts, it’s always the default output path for the platform that is checked to be empty or not.
This is problematic when using a custom build method that output the version in a different folder.
i would like to be able to override the output path (getBuildOutputDirectory) that is checked as a parameter in the task.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
How can I change the default build output directory in Visual ...
I can do this by manually going into properties of each project, going to the Build tab, changing Output path from bin\Debug to...
Read more >Deploying next.js app to vercel or netlify throws error #5660
I tried to switch to using the custom output path in vercel config and removing the --outputPath=. but that makes me run into...
Read more >Visual Studio 2005 Build Output Path - MSDN - Microsoft
Now open the new project and change the build output path. Choose "File -> Save All" and then close the project properties window....
Read more >OutputPath - AWS Step Functions
OutputPath enables you to select a portion of the state output to pass to the next state. This enables you to filter out...
Read more >Authoring Tasks - Gradle User Manual
This registers a copy task with no default behavior. ... These problems then fail the build or are turned into deprecation warnings when...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi @gilbdev,
thank you. This is fixed with the next version of the build task which I am planning to release soon. V3 generally aims at more advanced use cases and doesn’t have as many restrictions as before in how you can use it.
This is resolved in v2.7 of the extension that just got released. Sorry everyone for the deeeeeeeeeeeeelay.