New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[TIMOB-25865] Android: Modified CLI to not select "build-tools" version newer than supported if a supported version is installed #28
Conversation
…supported if a supported version is installed. - This avoids an unecessary "too new" warning logged after every build. - Also modified to log which version(s) are supported if installed build-tools is older than supported.
lib/android.js
Outdated
missing.forEach(function (m) { | ||
msg += ' ' + commandPrefix + 'ti config android.executables.' + m + ' "' + path.join(dummyPath, m + requiredSdkTools[m]) + '"\n'; | ||
}); | ||
msg = ""; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
single quotes?
FR Passed.
Studio Ver: 5.1.0.201804230827 |
Waiting for CR to merge. |
@sgtcoolguy Can you do the CR? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CR: PASS
But the package.json
version needs bumping
@garymathews, We will need a SDK PR for updating the package.json. So this can be merged. Have commented in the ticket to open a SDK PR for the same. |
JIRA:
https://jira.appcelerator.org/browse/TIMOB-25865
Summary:
Note:
Our
appc.version.satisfies()
function returns boolean valuestrue
andfalse
... as well as the string'maybe'
if above supported version range (ie: too new). Doing an if-check on the'maybe'
string was what was biting us here.Test:
~/Library/Android/sdk/build-tools