Fixed
Status Update
No update yet.
Comments
dy...@google.com
Further testing shows 11.0.0 works in this setup and 11.2.0 is the first version this appears.
wi...@gmail.com
This is expected. Both libraries have a java resource called 'protobuf.meta', which either the library authors need to stop shipping or the build author needs to pick one. See https://google.github.io/android-gradle-dsl/current/com.android.build.gradle.internal.dsl.PackagingOptions.html
However, if both libraries actually depend on that java resource you are in trouble.
However, if both libraries actually depend on that java resource you are in trouble.
ar...@google.com
bo...@google.com
bo...@google.com
I can confirm that specifying exclude or pick-first on protobuf.meta results in a successful build and no *immediate* problems. However, the contents of these two files are completely different and without understanding the purpose of these files (I assume related to protocol buffer data structure) it feels very treacherous to remove them.
bo...@google.com
ca...@google.com
Stephan, do you know what that file does and what changed that meant that it has started being bundled as a java resource in the testing support library?
de...@google.com
I see the same issue in a module referencing com.google.android.gms:play-services-location and com.google.android.gms:play-services-maps after integrating com.google.firebase:firebase-core and com.google.firebase:firebase-perf in the app.
I am running `11.6.2` of all libraries as well as Gradle 4.3.1-all and support lib 26.1.0
I am running `11.6.2` of all libraries as well as Gradle 4.3.1-all and support lib 26.1.0
Description
The bug is showed in the video. This happens only in the android emulator window.
Please Read:
Android Studio Version: Unknown
Emulator Version (Emulator--> Extended Controls--> Emulator Version): 32.1.11-9536276
HAXM / KVM Version: HVF 13.2.0
Android SDK Tools: 26.1.1
Host Operating System: macOS 13.2.1
CPU Manufacturer: Other CPU:
64-bit CPU
RAM: 16384 MB
GPU:
Build Fingerprint:
AVD Details: Name: A22_API_31
CPU/ABI: arm64
Path: /Users/projecthouse/.android/avd/A22_API_31.avd
Target: google_apis_playstore [Google Play] (API level 31)
Skin: 720x1510
SD Card: 512M
AvdId: A22_API_31
PlayStore.enabled: true
avd.ini.displayname: A22 API 31
avd.ini.encoding: UTF-8
disk.dataPartition.size: 6442450944
fastboot.chosenSnapshotFile:
fastboot.forceChosenSnapshotBoot: no
fastboot.forceColdBoot: yes
fastboot.forceFastBoot: no
hw.accelerometer: yes
hw.arc: false
hw.audioInput: yes
hw.battery: yes
hw.camera.back: virtualscene
hw.camera.front: emulated
hw.cpu.ncore: 4
hw.dPad: no
hw.device.hash2: MD5:9847239f65ec7ef3089a6320357fa7a4
hw.device.manufacturer: User
hw.gps: yes
hw.gpu.enabled: yes
hw.gpu.mode: auto
hw.initialOrientation: Portrait
hw.keyboard: yes
hw.lcd.density: 240
hw.lcd.height: 1510
hw.lcd.width: 720
hw.mainKeys: no
hw.ramSize: 6144
hw.sdCard: yes
hw.sensors.orientation: yes
hw.sensors.proximity: yes
hw.trackBall: no
image.sysdir.1: system-images/android-31/google_apis_playstore/arm64-v8a/
runtime.network.latency: none
runtime.network.speed: lte
showDeviceFrame: yes
skin.dynamic: yes
tag.display: Google Play
vm.heapSize: 80
Steps to Reproduce Bug:
The bug is showed in the video. This happens only in the android emulator window.
Expected Behavior:
Observed Behavior: