[CAF receiver] com.google.android.gms:play-services-cast-framework:18.1.0 brings in a very old version of com.google.protobuf:protobuf-lite [161831470]

Fixed

Bug

Status Update

No update yet.

Description

[Deleted User]

created issue #1

Jul 22, 2020 09:31AM

Describe the issue: expected vs. observed behavior and/or appearance.

The latest gms:play-services-cast-framework (18.1.0) brings in a very old com.google.protobuf:protobuf-lite at version 3.0.1

com.google.protobuf:protobuf-javalite:3.12.2 is the most current one and it is not binary compatible (see the rename from lite to javalite.

This causes duplicate symbol errors on apps that try to update to the latest proto libraries as gradle, on android, is not able to figure out that these two proto libraries are equivalent.

Note that other com.google.android.gms libraries do use protobuf-javalite already

The dependency is caused by com.google.android.gms:play-services-cast-framework:18.1.0 depending on com.google.android.datatransport:transport-backend-cct:2.1.0 which in turn brings in the out of date protobuf library.

Note that there is a *com.google.android.datatransport:transport-backend-cct:2.3.0 that does use the correct version of the proto library.

A workaround is to force a dependency to transport-backend-cct:2.3.0 in your gradle file:

api ('com.google.android.datatransport:transport-backend-cct:2.3.0')

List steps to reproduce the issue, if known.

Build an app that depends on com.google.android.gms:play-services-cast-framework:18.1.0 and on com.google.protobuf:protobuf-javalite:3.12.2

---- dependency tree snippet ----

|    |    |    +--- com.google.android.gms:play-services-cast-framework:18.1.0
|    |    |    |    +--- androidx.appcompat:appcompat:1.0.0 -> 1.1.0 (*)
|    |    |    |    +--- androidx.collection:collection:1.0.0 -> 1.1.0 (*)
|    |    |    |    +--- androidx.core:core:1.0.0 -> 1.3.0 (*)
|    |    |    |    +--- androidx.fragment:fragment:1.0.0 -> 1.2.5 (*)
|    |    |    |    +--- androidx.media:media:1.0.0 -> 1.1.0 (*)
|    |    |    |    +--- androidx.mediarouter:mediarouter:1.0.0 -> 1.1.0 (*)
|    |    |    |    +--- androidx.recyclerview:recyclerview:1.0.0 -> 1.1.0 (*)
|    |    |    |    +--- com.google.android.datatransport:transport-api:2.1.0
|    |    |    |    +--- com.google.android.datatransport:transport-backend-cct:2.1.0
|    |    |    |    |    +--- androidx.annotation:annotation:1.1.0
|    |    |    |    |    +--- com.google.android.datatransport:transport-api:2.1.0
|    |    |    |    |    +--- com.google.android.datatransport:transport-runtime:2.1.0
|    |    |    |    |    |    +--- androidx.annotation:annotation:1.1.0
|    |    |    |    |    |    +--- com.google.android.datatransport:transport-api:2.1.0
|    |    |    |    |    |    \--- com.google.dagger:dagger:2.22 -> 2.27 (*)
|    |    |    |    |    \--- com.google.protobuf:protobuf-lite:3.0.1

Comments

bo...@justin.tv <bo...@justin.tv> #2Aug 27, 2020 08:19PM

Thanks for the feedback on the emulator. To help us troubleshoot this issue further, we will need more information. Please share detailed reproduction steps and as much as possible of the following information:

1. Emulator version
2. Run the emulator from command line with “$ANDROID_SDK_ROOT/emulator/emulator -avd <NameOfAVD> -verbose -show-kernel” and send the resulting logs
3. Any relevant Logcat logs
4. The results of running “adb shell top” in the command line.

For more information on what’s needed and how to obtain this information please read the guide at

https://developer.android.com/studio/report-bugs#emulator-bugs.

oz...@google.com <oz...@google.com> Oct 26, 2020 06:55PM

Assigned to ar...@google.com.

ar...@google.com <ar...@google.com> #3Jan 8, 2021 08:47PM

Android Studio Ladybug Feature Drop 2024.22

Am Fr., 7. März 2025 um 16:08 Uhr schrieb <buganizer-system@google.com>:

- Show quoted text -

ar...@google.com <ar...@google.com> #4Jan 27, 2021 11:58PM

Marked as fixed.

Hi Stean, the file you attached shows

INFO | Boot completed in 62411 ms

Did the Emulator work for you when you started from the command line? Could you also attach idea.log (in Android Studio, Help > Show Log) please.

he...@gmail.com <he...@gmail.com> #5Jun 5, 2023 07:00PM

Thanks for your support.
Yes, a device popped up and for a time it seems to work, but then it shut
down.

Am Fr., 7. März 2025 um 18:57 Uhr schrieb <buganizer-system@google.com>:

- Show quoted text -

Issue 161831470