bug
Disregarding AndroidSdkRoot, if SdkUseEmbedded is enabled when building for Android.
#704
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thanks for proposing a pull request!
To help us review the request, please complete the following:
bug
for bug fixes)Pull Request Details
In fresh Unity installations the
AndroidSdkRoot
editor pref is not set. They rather default to the tools installed with the editor (SdkUseEmbedded
set to true).Before the fix, we were unable to build unless a correct SDK path was explicitly set, even if the
SdkUseEmbedded
option was enabled.By checking the
SdkUseEmbedded
boolean first we can mitigate the problem.The code can be further optimized by getting the set
AndroidSdkRoot
in an else statement, but I don't know if that's within the scope of this fix.Test Plan
Test Plan: Add your test plan here