Skip to content
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

fix(android)(9_0_X): production builds no longer copy AAB to distribution folder as of 9.0.1 #11645

Merged
merged 4 commits into from
Apr 30, 2020

Conversation

jquick-axway
Copy link
Contributor

- Regression introduced in 9.0.1 by using newest Android gradle tool.
  * Google renamed built AAB file and Titanium failed to find the file.
  * AAB file was stilling be built, just not be copied to given destination folder.
- Added APK and AAB file validation. Will now trigger build failure if files were not found.
@build
Copy link
Contributor

build commented Apr 17, 2020

Messages
📖 ✊ The commits in this PR match our conventions! Feel free to Rebase and Merge this PR when ready.
📖

✅ All tests are passing
Nice one! All 2251 tests are passing.
(There are 225 skipped tests not included in that total)

Generated by 🚫 dangerJS against 17373cb

Copy link
Contributor

@garymathews garymathews left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CR: PASS

// Verify that we can find the above built file(s).
if (!await fs.exists(this.apkFile)) {
this.logger.error(`Failed to find built APK file: ${this.apkFile}`);
process.exit(1);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just an FYI - I am not fond of our use of exiting the process immediately in these functions like this. Ideally we simple return an error to the callback/throw an Error (if in an async function or sync function with no callback) - and let the top-level CLI do the exiting of the process with a failure exit code. We tend to have these calls sprinkled throughout CLI related code making re-use harder if we ever want to re-use in another context.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll change it to throw an exception instead, which I think is fine in this case.

That said, I don't think we should throw an exception for say end-user configuration issues, because the logged stack trace would make it look like an issue on our end when it's not.

@lokeshchdhry
Copy link
Contributor

FR Passed.
.aab file is successfully generated & copied to the specified location.

Studio Ver: 6.0.0.202003181504
SDK Ver: 9.0.2 local build
OS Ver: 10.15.4
Xcode Ver: Xcode 11.4
Appc NPM: 5.0.0
Appc CLI: 8.0.0
Daemon Ver: 3.2.0
Ti CLI Ver: 5.2.2
Alloy Ver: 1.14.6
Node Ver: 12.13.1
NPM Ver: 6.12.1
Java Ver: 11.0.6

@sgtcoolguy sgtcoolguy merged commit 1ca5f70 into tidev:9_0_X Apr 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants