Building instrumentation tests against release build while depending on data binding fails [37073165]

Obsolete

Bug

Migrated-Tools-Gradle

Status Update

No update yet.

Description

ni...@gmail.com

created issue #1

Dec 4, 2015 10:16AM

Building instrumentation tests which are configured against release build (testBuildType 'release') fails after introducing data binding to any project.

I've created a sample project at

https://github.com/Nilzor/AndroidDatabindingAndInstrumentationTests.git

To reproduce:

1. Clone the repo
2. Make sure you're on the latest commit on the master branch (SHA 119e5fba314b945b84794ba782e30a7ab6c0829e)
3. run gradle task "connectedCheck"
4. Observe that you get the following error during build:

"Warning: library class android.databinding.DataBindingUtil depends on program class android.databinding.DataBindingComponent"
"Execution failed for task ':app:transformClassesAndResourcesWithProguardForReleaseAndroidTest'."
(full output in attached file)

Test system and versions:
Windows 10 , but also tested on Mac
------------------------------------------------------------
Gradle 2.8
------------------------------------------------------------

Build time: 2015-10-20 03:46:36 UTC
Build number: none
Revision: b463d7980c40d44c4657dc80025275b84a29e31f

Groovy: 2.4.4
Ant: Apache Ant(TM) version 1.9.3 compiled on December 23 2013
JVM: 1.7.0_79 (Oracle Corporation 24.79-b02)
OS: Windows 8.1 6.3 amd64

Android Studio 2.0 Preview 2
Build #AI-143.2461418, built on December 2, 2015
JRE: 1.7.0_79-b15 amd64
JVM: Java HotSpot(TM) 64-Bit Server VM by Oracle Corporation

databinding-release-instrutests-output.txt

7.3 KB

View

Download

Comments

ni...@gmail.com <ni...@gmail.com> #2Dec 4, 2015 10:18AM

Looking so good new version

ni...@gmail.com <ni...@gmail.com> #3Feb 12, 2016 11:39AM

Thank you for reporting this issue.

Please provide the below details to debug this issue further.

1. Please attach your sample android project which reproduces the issue, zip it and share
2. Explain the steps to reproduce the issue with your apk. Provide all necessary information including preconditions if any, to reproduce the issue.

3. Android bug report
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.

Alternate method:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.

4. Screen Record of the issue
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue.

[Deleted User] <[Deleted User]> #4Mar 22, 2016 09:24PM

1. Code Sample attached. Cannot attach the original app code because of copyright.

2. Steps to reproduce it:
1. Tap on the first image (this activity is portrait)
2. It will go to a landscape ativity
3. Tap back button
4. Observe that the previous activity goes to portrait, then to landscape and finally portrait again.
Note: On the original app is happening always. On this code sample I was able to reproduce it 5/10 times.

4. Video attached, error on the last seconds.

pr...@gmail.com <pr...@gmail.com> #5Apr 24, 2016 07:52AM

Could you please share the bugreport too?

Android bug report
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.

Alternate method:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.

do...@gmail.com <do...@gmail.com> #6May 6, 2016 05:51PM

Attaching the bug report.

je...@google.com <je...@google.com> Aug 10, 2016 11:08PM

Assigned to cm...@google.com.

am...@google.com <am...@google.com> #7May 23, 2023 03:09PM

Status: Won't Fix (Obsolete)

Thank you for reporting this issue. We have shared this with our product and engineering team and will update this issue with more information as it becomes available.