Move deployment build output to intermediates folder [69014026]

Fixed

Bug

Reviewed (L1)

Status Update

No update yet.

Description

xa...@google.com

created issue #1

Nov 8, 2017 04:48AM

When building an APK from Studio via the "run..." action, the APK is built specifically for the given device.

Putting these APKs under build/output/apks is misleading as developers might find them there and attempt to install them on other devices which is unlikely to work.

We should put them under intermediates now that Studio loads the output location after a build.

Comments

je...@google.com <je...@google.com> Nov 22, 2017 10:51PM

Reassigned to st...@google.com.

st...@google.com <st...@google.com> Aug 19, 2020 08:37PM

Reassigned to je...@google.com.

je...@google.com <je...@google.com> #2Oct 13, 2020 04:29PM

Hi I checked the issue, Cannot see the issue on N5, However did you put some check for setError ?
Would it be possible to get a complete standalone test app that reproduces this behavior?

je...@google.com <je...@google.com> #3Aug 12, 2021 11:09PM

Marked as fixed.

[Comment deleted]

sa...@google.com <sa...@google.com> #4Aug 26, 2021 06:34PM

Hi,

I also have this issue.

My application uses multiple fragments and a lot of them have text input layouts with setError(true).

I found that when I clear the keyboard on back stack change via:

public static void hideKeyboardToken(Activity activity) {
InputMethodManager imm = (InputMethodManager)activity.getSystemService(Activity.INPUT_METHOD_SERVICE);
View view = activity.getCurrentFocus();
if (view != null) imm.hideSoftInputFromWindow(view.getWindowToken(),0);
}

All of the text input layouts will be rendered as red.

When I stop hiding the keyboard all of the text input layouts behave as expected. (But the keyboard remains persistent when changing fragments.)

SDK Versions:

minSdkVersion 16
targetSdkVersion 22
compileSdkVersion 23
buildToolsVersion "23.0.2"

Phone: Samsung Galaxy S5

ka...@gmail.com <ka...@gmail.com> #5Mar 7, 2022 12:52PM

I have the same issue. Created a sample project to simulate the same.

https://github.com/pollux-/DesignLibIssue

je...@google.com <je...@google.com> #6Mar 7, 2022 05:33PM

We will have a look at the issue and provide more information on this as it becomes available

to...@gmail.com <to...@gmail.com> #7Mar 9, 2022 12:49AM

[Comment deleted]

to...@gmail.com <to...@gmail.com> #8Mar 9, 2022 12:56AM

Manual builds mean "Build / Generate Signed Bundle or APK" or press "assembleRelease" from gradle window.
When we build Signed APK files for distribution, they should be at the 'builds/outputs/apk' folder, not 'build/intermediates/apk' folder.
Please revert this change back to before.

je...@google.com <je...@google.com> Mar 9, 2022 05:00AM

Status: Assigned (reopened)

yu...@gmail.com <yu...@gmail.com> #9Mar 28, 2022 05:59AM

Comment has been deleted.

Message last modified on Mar 28, 2022 06:18AM

ak...@gmail.com <ak...@gmail.com> #10Apr 25, 2022 09:51AM

Is this issue fixed?

je...@google.com <je...@google.com> #11Apr 25, 2022 02:37PM

no, #8, when invoking build from the gradle window is still an issue.

so...@google.com <so...@google.com> #12Apr 25, 2022 02:45PM

Re comment #11, Jerome which task and on which project do you invoke?

je...@google.com <je...@google.com> #13Apr 25, 2022 02:51PM

apparently, assembleRelease. Probably a dup of b/229630014

so...@google.com <so...@google.com> #14Apr 25, 2022 02:58PM

asking because running a task from the root project would behave
differently than running a task from, for example, :app

On Mon, 25 Apr 2022 at 15:52, jedo <buganizer-system+jedo@google.com> wrote:

- Show quoted text -

je...@google.com <je...@google.com> #15Apr 25, 2022 03:29PM

#8, can you answer #14 ?

so...@google.com <so...@google.com> #16Apr 25, 2022 03:37PM

nm, "Build / Generate Signed Bundle or APK" is the answer.

ak...@gmail.com <ak...@gmail.com> #17Apr 25, 2022 06:48PM

I am facing the exact same issue. My gradle version is 7.4.2 and gradle plugin version is 7.1.2. In my case there is no output/apk folder generated. apks are present in intermediates folder. The problem is that we are using spoon test runner to run instrumentation tests and it is defined to pick test apk and debug apk from output folder which is non existent.

Message last modified on Apr 25, 2022 06:51PM

an...@crowdstrike.com <an...@crowdstrike.com> #18Jun 8, 2022 10:11AM

I can confirm what is reported at #5 using Gradle 7.4.2, AGP 7.1.3

Studio version: Android Studio Chipmunk | 2021.2.1 Patch 1 Build #AI-212.5712.43.2112.8609683, built on May 18, 2022 Runtime version: 11.0.12+0-b1504.28-7817840 x86_64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o. macOS 11.6.6

Tests I have done:

running ./gradlew :app:assembleProdDebug from Studio's terminal window leads to the apk being published at app/build/outputs/apk/prod/debug/app-prod-debug.apk folder
triggering Build -> Make Project of the app module from Studio's UI results in the same gradle task (as well as a couple more) being run, but results in the apk being published at app/build/intermediates/apk/prod/debug/app-prod-debug.apk folder.

Is that the expectation? (if so, what is the reason behind it?)

Message last modified on Jun 8, 2022 10:35AM

je...@google.com <je...@google.com> #19Jul 27, 2022 11:12PM

Marked as fixed.

This has been fixed in Dolphin :

~/AndroidStudioProjects/MyApplication10 > find . -name "*.apk" ./app/build/outputs/apk/debug/app-debug.apk

ma...@gmail.com <ma...@gmail.com> #20Oct 4, 2022 08:53PM