espresso 3.0.1 incompatible with play-services-auth:11.6.0 in android library module. [69333598]

Fixed

Bug

Status Update

No update yet.

Description

ad...@atlassian.com

created issue #1

Nov 15, 2017 04:22AM

Library used (Espresso, Runner, Rules etc.):
Version used: espresso 3.0.1, runner:1.0.1

What steps will reproduce the problem?
1. Using this build.gradle from a standard library module created by the android studio 3.0.0 template

apply plugin: 'com.android.library'

android {
compileSdkVersion 26

defaultConfig {
minSdkVersion 16
targetSdkVersion 26
versionCode 1
versionName "1.0"

testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"

}

buildTypes {
release {
minifyEnabled false
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
}
}

}

dependencies {
implementation fileTree(dir: 'libs', include: ['*.jar'])

implementation 'com.android.support:appcompat-v7:26.1.0'
implementation 'com.google.android.gms:play-services-auth:11.6.0'
testImplementation 'junit:junit:4.12'
androidTestImplementation 'com.android.support.test:runner:1.0.1'
androidTestImplementation 'com.android.support.test.espresso:espresso-core:3.0.1'
}

2. execute ./gradlew :myLibrary:connectedAndroidTest
3. Results in
Execution failed for task ':mylibrary:transformResourcesWithMergeJavaResForDebugAndroidTest'.
More than one file was found with OS independent path 'protobuf.meta'

How are you running your tests (via Android Studio, Gradle, adb, etc.)?
run through Gradle.

What is the expected output? What do you see instead?
Expected successful build

Comments

ad...@atlassian.com <ad...@atlassian.com> #2Nov 15, 2017 05:36AM

First of all thanks for this detailed issue.

This issue had been investigated thoroughly when it was first reported internally. The surprising detail in this report is that the issue is not reproducible before 1.7. I will look into this.

The main problem with POBox is the fact that it is deprecated. Since 2021 Sony has been shipping new Xperia devices with Gboard pre-installed. Although we are aware that there is still a considerable amount of users still using POBox, the described behavior is caused by POBox's noncompliant behavior with InputConnection and InputMethodManager documentation. However, this is understandable since TextView implementation was also not respecting the behavior that is expected from Editors.

Ultimately we have decided to enforce the documented behavior with specifically regards to when editors should call InputMethodManager.updateSelection. Also, although unconfirmed, there were traces of possible custom code being included in Sony OEM images that changed how InputMethodManager was notified from TextView. If POBox also depended on something like this, it would be impossible for Compose code to replicate the same unknown behavior.

sl...@google.com <sl...@google.com> Nov 15, 2017 08:19PM

Assigned to be...@google.com.

be...@google.com <be...@google.com> Nov 16, 2017 01:47PM

Reassigned to cm...@google.com.

cm...@google.com <cm...@google.com> #3Nov 16, 2017 02:18PM

If the investigation takes time, would it be possible to revert the surrounding implementation to 1.6.x equivalent?

Or is that option not available?

Even if the root cause is POBox, from the perspective of the app's customers, it looks like an app bug, so this issue is a blocker against updating Jetpack Compose.

ad...@atlassian.com <ad...@atlassian.com> #4Nov 16, 2017 10:38PM

Just to be sure, it is dangerous to replace Compose TextField with Android View EditText as a workaround for this issue.

Compose 1.7 has a bug that causes ANR when the focus is on EditText. https://issuetracker.google.com/issues/369354336

Another View-related bug in Compose 1.7 is that an Android View is focused by calling FocusManager.clearFocus(). https://issuetracker.google.com/issues/374031296

Perhaps there is a lack of testing of Compose 1.7 in combination with Android View. There is also a possibility that there are other fatal bugs related to View.

In other words, the only options for apps targeting the Japanese market that require POBox support are to continue using Compose 1.6 or to use EditText in combination with various workarounds.

cm...@google.com <cm...@google.com> #5Nov 17, 2017 05:07PM

Reassigned to sl...@google.com.

Project: platform/frameworks/support
Branch: androidx-main
Author: Halil Ozercan <halilibo@google.com>
Link: https://android-review.googlesource.com/3317256

Fix POBox keyboard issue

Expand for full commit details

Fix POBox keyboard issue 
 
Fix: 373743376 
Fix: 329209241 
Test: NullableInputConnectionWrapperTest 
Change-Id: I94e0e598274fb88b255f977f9fbd50dfbbb1ecb1

Files:

M compose/ui/ui/src/androidInstrumentedTest/kotlin/androidx/compose/ui/text/input/NullableInputConnectionWrapperTest.kt
M compose/ui/ui/src/androidMain/kotlin/androidx/compose/ui/text/input/NullableInputConnectionWrapper.android.kt

Hash: 57f58c4b80d5d8470b2aca325dfdcd55f235231e
Date: Thu Oct 24 01:25:20 2024

k....@gmail.com <k....@gmail.com> #6Dec 4, 2017 04:11PM

Many thanks again for this report. Especially for giving us a huge clue in terms of what could be going wrong. The fix is now merged and I will ask for a cherry-pick into a stable release.

[Deleted User] <[Deleted User]> #7Dec 18, 2017 08:37PM

Thank you for fixing the issue, I confirmed the fix was released in version 1.8.0-alpha05.
Do you have any concrete plan to cherry-pick the fix into current stable version (1.7.x)? We are currently waiting it.

sl...@google.com <sl...@google.com> Mar 28, 2018 06:32PM

Reassigned to nk...@google.com.

nk...@google.com <nk...@google.com> #8Mar 29, 2018 11:43PM

Marked as fixed.

Yes, this fix is planned to be included in a future 1.7.x release.