Updating to platform tools 29.0.0 results in continuous stream of adb.exe crash dialogs, at least on Windows 8.1 [134613180]

Fixed

Bug

Reviewed (L1)

Status Update

No update yet.

Description

le...@gmail.com

created issue #1

Jun 5, 2019 11:55PM

Today I updated several SDK components. I'm on the stable channel, and before today I was up to date for the stable channel. The one I believe I'm having the trouble with is the 29.0.0 platform tools. If I go back to 28.0.2, everything is fine.

When I start the Emulator (via Android Studio), I get a Windows "adb.exe has stopped working" check for solution/close program dialog. Then a couple of seconds later I get another, and another. The emulator does come up, and it's GUI is responsive, but I can't really access it from Android Studio. The stream of Windows error dialogs continues until I stop the emulator.

I can access a real test device just fine.

When I change my "platform-tools" folder back to the previous version, which I believe was 28.0.2, everything works fine. This is the workaround I'm planning on using.

I've tried this with both an AVD that I had before the update to 29.0.0 and one I created after the update. It acts the same.

I have not tried to run the emulator from the command line.

This part I can not reliably reproduce, but I've seen it several times. Sometimes, I get an error dialog after I start the emulator (via Android Studio) but before the first adb.exe crash dialog. That error dialog says something about my adb.exe being hopelessly out of date. I'm not sure who is generating that dialog, but I don't think it's Windows. Over the years I think I've seen that same error very intermittently, but ignoring it never seems to have any negative conciquences.

Since I'm not seeing too much yelling and screaming about this on the net I'm assuming I'm in a relatively small group. Windows 8.1 for one. My most non-standard thing I can think of about my system is that the android SDK folder and the android AVD folder are both on my E: drive (C: is the system drive and where my hold folder is). This is not new.

I have a very low-end Windows 10 machine that I only use in emergencies and it seems to be working fine.

Please Read:

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

Android Studio Version: 3.4.0-2

Emulator Version (Emulator--> Extended Controls--> Emulator Version): 29.0.11-5598178
HAXM / KVM Version: HAXM 7.5.1

Android SDK Tools: 26.1.1

Host Operating System: Windows 8.1

CPU Manufacturer: Intel CPU
Virtualization is supported
64-bit CPU

RAM: 16316 MB

GPU: GPU #1
Make: 10de
Model: NVIDIA GeForce 840M
Device ID: 1341

Build Fingerprint: google/sdk_gphone_x86/generic_x86:8.1.0/OSM1.180201.031/5455776:userdebug/dev-keys

AVD Details: Name: Nexus_5X_API_27_8.1_x86_Google_APIs_
CPU/ABI: x86
Path: E:\LeeExtra\Dev\.android\avd\Nexus_5X_API_27_8.1_x86_Google_APIs_.avd
Target: google_apis [Google APIs] (API level 27)
Skin: nexus_5x
SD Card: 512M
AvdId: Nexus_5X_API_27_8.1_x86_Google_APIs_
PlayStore.enabled: false
avd.ini.displayname: Nexus 5X API 27 (8.1 x86 Google APIs)
avd.ini.encoding: UTF-8
disk.dataPartition.size: 800M
fastboot.chosenSnapshotFile:
fastboot.forceChosenSnapshotBoot: no
fastboot.forceColdBoot: no
fastboot.forceFastBoot: yes
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:ae200ad6786ec467cb9067f7b46b0fd1
hw.device.manufacturer: Google

hw.device.name: Nexus 5X
hw.gps: yes
hw.gpu.enabled: yes
hw.gpu.mode: auto
hw.initialOrientation: Portrait
hw.keyboard: yes
hw.lcd.density: 420
hw.lcd.height: 1920
hw.lcd.width: 1080
hw.mainKeys: no
hw.ramSi

Comments

mi...@gtempaccount.com <mi...@gtempaccount.com> #2Jun 6, 2019 12:28PM

Project: platform/frameworks/support
Branch: androidx-master-dev

commit d0a10be065a3a629e3835f28d35804c91d8d2e4d
Author: Ian Lake <ilake@google.com>
Date: Mon Sep 14 16:10:06 2020

Mention the current destination in getBackStackEntry errors

Improve the debugging experience for "No destination
with ID..." errors in getBackStackEntry() by mentioning
exactly destination the NavController is on. This would
allow developers to know if they have called popBackStack()
to a destination they don't expect to be at or if
they have not called setGraph() at all (where the
current destination would be null).

Test: existing tests pass
BUG: 168311416
Change-Id: Ia96b6732d7caadbddf31b7f35a1a419407ff6e25

M navigation/navigation-runtime/src/main/java/androidx/navigation/NavController.java

https://android-review.googlesource.com/1427352

uc...@google.com <uc...@google.com> Jun 6, 2019 09:24PM

Assigned to lf...@google.com.

lf...@google.com <lf...@google.com> #3Jun 7, 2019 02:59PM

Reassigned to jm...@google.com.

We've updated the error message to make it more clear what destination you're currently on - this will help you determine if your call to setGraph() hasn't happened yet (you have a null current destination) or if you've popped to another destination unexpectedly.

1c...@gmail.com <1c...@gmail.com> #4Jun 7, 2019 03:17PM

Project: platform/frameworks/support
Branch: snap-temp-L69500000699825513

commit 6ada6bd039f4a28d2760f4912093abc60ab54d84
Author: Ian Lake <ilake@google.com>
Date: Mon Sep 14 16:10:06 2020

Mention the current destination in getBackStackEntry errors

Improve the debugging experience for "No destination
with ID..." errors in getBackStackEntry() by mentioning
exactly destination the NavController is on. This would
allow developers to know if they have called popBackStack()
to a destination they don't expect to be at or if
they have not called setGraph() at all (where the
current destination would be null).

Test: existing tests pass
BUG: 168311416
Change-Id: Ia96b6732d7caadbddf31b7f35a1a419407ff6e25
(cherry picked from commit d0a10be065a3a629e3835f28d35804c91d8d2e4d)

M navigation/navigation-runtime/src/main/java/androidx/navigation/NavController.java

https://android-review.googlesource.com/1436733

adb.jpg

375 KB

View

Download

be...@gmail.com <be...@gmail.com> #5Jun 7, 2019 07:04PM

Project: platform/frameworks/support
Branch: snap-temp-L62000000699827533

commit e5780347bfba28e4a500bd964d273c282c12dceb
Author: Ian Lake <ilake@google.com>
Date: Mon Sep 14 16:10:06 2020

Mention the current destination in getBackStackEntry errors

Improve the debugging experience for "No destination
with ID..." errors in getBackStackEntry() by mentioning
exactly destination the NavController is on. This would
allow developers to know if they have called popBackStack()
to a destination they don't expect to be at or if
they have not called setGraph() at all (where the
current destination would be null).

Test: existing tests pass
BUG: 168311416
Change-Id: Ia96b6732d7caadbddf31b7f35a1a419407ff6e25
(cherry picked from commit d0a10be065a3a629e3835f28d35804c91d8d2e4d)

M navigation/navigation-runtime/src/main/java/androidx/navigation/NavController.java

https://android-review.googlesource.com/1436737

jm...@google.com <jm...@google.com> #6Jun 11, 2019 07:40PM

Marked as fixed.

Project: platform/frameworks/support
Branch: snap-temp-L46100000699831674

commit 7ab7f8b1967945ba0d506120dbc070ecbfb37c13
Author: Ian Lake <ilake@google.com>
Date: Mon Sep 14 16:10:06 2020

Mention the current destination in getBackStackEntry errors

Improve the debugging experience for "No destination
with ID..." errors in getBackStackEntry() by mentioning
exactly destination the NavController is on. This would
allow developers to know if they have called popBackStack()
to a destination they don't expect to be at or if
they have not called setGraph() at all (where the
current destination would be null).

Test: existing tests pass
BUG: 168311416
Change-Id: Ia96b6732d7caadbddf31b7f35a1a419407ff6e25
(cherry picked from commit d0a10be065a3a629e3835f28d35804c91d8d2e4d)

M navigation/navigation-runtime/src/main/java/androidx/navigation/NavController.java

https://android-review.googlesource.com/1436741

le...@gmail.com <le...@gmail.com> #7Jun 11, 2019 09:06PM

Project: platform/frameworks/support
Branch: snap-temp-L91000000699844097

commit 4101ca222554fdfae678ff1e6e47b1a4ab319a56
Author: Ian Lake <ilake@google.com>
Date: Mon Sep 14 16:10:06 2020

Mention the current destination in getBackStackEntry errors

Improve the debugging experience for "No destination
with ID..." errors in getBackStackEntry() by mentioning
exactly destination the NavController is on. This would
allow developers to know if they have called popBackStack()
to a destination they don't expect to be at or if
they have not called setGraph() at all (where the
current destination would be null).

Test: existing tests pass
BUG: 168311416
Change-Id: Ia96b6732d7caadbddf31b7f35a1a419407ff6e25
(cherry picked from commit d0a10be065a3a629e3835f28d35804c91d8d2e4d)

M navigation/navigation-runtime/src/main/java/androidx/navigation/NavController.java

https://android-review.googlesource.com/1436542

v....@gmail.com <v....@gmail.com> #8Jul 14, 2019 12:02PM

Project: platform/frameworks/support
Branch: snap-temp-L34200000699848945

commit 0da3ed71fa5545646d44fb44219b31e7e5621f8f
Author: Ian Lake <ilake@google.com>
Date: Mon Sep 14 16:10:06 2020

Mention the current destination in getBackStackEntry errors

Improve the debugging experience for "No destination
with ID..." errors in getBackStackEntry() by mentioning
exactly destination the NavController is on. This would
allow developers to know if they have called popBackStack()
to a destination they don't expect to be at or if
they have not called setGraph() at all (where the
current destination would be null).

Test: existing tests pass
BUG: 168311416
Change-Id: Ia96b6732d7caadbddf31b7f35a1a419407ff6e25
(cherry picked from commit d0a10be065a3a629e3835f28d35804c91d8d2e4d)

M navigation/navigation-runtime/src/main/java/androidx/navigation/NavController.java

https://android-review.googlesource.com/1436745

jm...@google.com <jm...@google.com> #9Jul 15, 2019 08:12PM

Project: platform/frameworks/support
Branch: snap-temp-L04700000699849955

commit 12b13608ec1155b5780fe44f5ab07cdc93c5ba90
Author: Ian Lake <ilake@google.com>
Date: Mon Sep 14 16:10:06 2020

Mention the current destination in getBackStackEntry errors

Improve the debugging experience for "No destination
with ID..." errors in getBackStackEntry() by mentioning
exactly destination the NavController is on. This would
allow developers to know if they have called popBackStack()
to a destination they don't expect to be at or if
they have not called setGraph() at all (where the
current destination would be null).

Test: existing tests pass
BUG: 168311416
Change-Id: Ia96b6732d7caadbddf31b7f35a1a419407ff6e25
(cherry picked from commit d0a10be065a3a629e3835f28d35804c91d8d2e4d)

M navigation/navigation-runtime/src/main/java/androidx/navigation/NavController.java

https://android-review.googlesource.com/1436750

cv...@gmail.com <cv...@gmail.com> #10Jul 16, 2019 12:23AM

Project: platform/frameworks/support
Branch: snap-temp-L69500000699869549

commit 7204d04ad74baf9816389e27778266391fbd79a5
Author: Ian Lake <ilake@google.com>
Date: Mon Sep 14 16:10:06 2020

Mention the current destination in getBackStackEntry errors

Improve the debugging experience for "No destination
with ID..." errors in getBackStackEntry() by mentioning
exactly destination the NavController is on. This would
allow developers to know if they have called popBackStack()
to a destination they don't expect to be at or if
they have not called setGraph() at all (where the
current destination would be null).

Test: existing tests pass
BUG: 168311416
Change-Id: Ia96b6732d7caadbddf31b7f35a1a419407ff6e25
(cherry picked from commit d0a10be065a3a629e3835f28d35804c91d8d2e4d)

M navigation/navigation-runtime/src/main/java/androidx/navigation/NavController.java

https://android-review.googlesource.com/1436913

cv...@gmail.com <cv...@gmail.com> #11Jul 16, 2019 12:27AM

Project: platform/frameworks/support
Branch: snap-temp-L31300000699869852

commit 398a1fe7bb7792589189574aec5f6e77bb749229
Author: Ian Lake <ilake@google.com>
Date: Mon Sep 14 16:10:06 2020

Mention the current destination in getBackStackEntry errors

Improve the debugging experience for "No destination
with ID..." errors in getBackStackEntry() by mentioning
exactly destination the NavController is on. This would
allow developers to know if they have called popBackStack()
to a destination they don't expect to be at or if
they have not called setGraph() at all (where the
current destination would be null).

Test: existing tests pass
BUG: 168311416
Change-Id: Ia96b6732d7caadbddf31b7f35a1a419407ff6e25
(cherry picked from commit d0a10be065a3a629e3835f28d35804c91d8d2e4d)

M navigation/navigation-runtime/src/main/java/androidx/navigation/NavController.java

https://android-review.googlesource.com/1436917

si...@gmail.com <si...@gmail.com> #12Jul 16, 2019 05:12PM

Project: platform/frameworks/support
Branch: snap-temp-L53700000699921463

commit 31027c16ff20b10e78093f8de205c81fc49dfc92
Author: Ian Lake <ilake@google.com>
Date: Mon Sep 14 16:10:06 2020

Mention the current destination in getBackStackEntry errors

Improve the debugging experience for "No destination
with ID..." errors in getBackStackEntry() by mentioning
exactly destination the NavController is on. This would
allow developers to know if they have called popBackStack()
to a destination they don't expect to be at or if
they have not called setGraph() at all (where the
current destination would be null).

Test: existing tests pass
BUG: 168311416
Change-Id: Ia96b6732d7caadbddf31b7f35a1a419407ff6e25
(cherry picked from commit d0a10be065a3a629e3835f28d35804c91d8d2e4d)

M navigation/navigation-runtime/src/main/java/androidx/navigation/NavController.java

https://android-review.googlesource.com/1436920

Message last modified on Jul 16, 2019 05:15PM

si...@gmail.com <si...@gmail.com> #13Jul 24, 2019 07:13PM

Project: platform/frameworks/support
Branch: snap-temp-L25200000699921867

commit 63e58ff4f522eb70dec6c0749679fb6b963698d8
Author: Ian Lake <ilake@google.com>
Date: Mon Sep 14 16:10:06 2020

Mention the current destination in getBackStackEntry errors

Improve the debugging experience for "No destination
with ID..." errors in getBackStackEntry() by mentioning
exactly destination the NavController is on. This would
allow developers to know if they have called popBackStack()
to a destination they don't expect to be at or if
they have not called setGraph() at all (where the
current destination would be null).

Test: existing tests pass
BUG: 168311416
Change-Id: Ia96b6732d7caadbddf31b7f35a1a419407ff6e25
(cherry picked from commit d0a10be065a3a629e3835f28d35804c91d8d2e4d)

M navigation/navigation-runtime/src/main/java/androidx/navigation/NavController.java

https://android-review.googlesource.com/1436924

3l...@gmail.com <3l...@gmail.com> #14Jul 29, 2019 05:36PM

Project: platform/frameworks/support
Branch: snap-temp-L07700000699933785

commit 56fe0d47de20fb430c4280332a20eb96076dd44b
Author: Ian Lake <ilake@google.com>
Date: Mon Sep 14 16:10:06 2020

Mention the current destination in getBackStackEntry errors

Improve the debugging experience for "No destination
with ID..." errors in getBackStackEntry() by mentioning
exactly destination the NavController is on. This would
allow developers to know if they have called popBackStack()
to a destination they don't expect to be at or if
they have not called setGraph() at all (where the
current destination would be null).

Test: existing tests pass
BUG: 168311416
Change-Id: Ia96b6732d7caadbddf31b7f35a1a419407ff6e25
(cherry picked from commit d0a10be065a3a629e3835f28d35804c91d8d2e4d)

M navigation/navigation-runtime/src/main/java/androidx/navigation/NavController.java

https://android-review.googlesource.com/1436929

mo...@gmail.com <mo...@gmail.com> #15Aug 16, 2019 05:55AM

getting this error even after ensuring we are setting graph before using it..
Caused by java.lang.IllegalArgumentException
No destination with ID 2131427956 is on the NavController's back stack in HiltNavGraphViewModelLazy.kt:49) , we are using androidx.hilt:hilt-navigation-fragment:1.0.0

androidx.navigation.NavController.getBackStackEntry (NavController.kt:2204)
androidx.hilt.navigation.fragment.HiltNavGraphViewModelLazyKt$hiltNavGraphViewModels$backStackEntry$2.invoke (HiltNavGraphViewModelLazyKt.java:49)
$special$$inlined$hiltNavGraphViewModels$4.invoke (HiltNavGraphViewModelLazy.kt:49)

is there any way to prevent it?

mo...@gmail.com <mo...@gmail.com> #16Aug 16, 2019 05:56AM

Could we further improve this by indicating the name of the destination instead of just the ID number?

le...@gmail.com <le...@gmail.com> #17Sep 26, 2019 11:51PM

If you use a resource to provide the name it will already be displayed. Along with any route or label you may have added.

zo...@gmail.com <zo...@gmail.com> #18Sep 29, 2019 01:05PM

We are also getting this error even after ensuring we are setting the graph before using .popBackStack().

Is there any way to safeguard against this? I am not able to reproduce the error myself, but get a lot of errors show up in Crashlytics

za...@gmail.com <za...@gmail.com> #19Oct 13, 2019 11:32AM

I have the same problem

ke...@gmail.com <ke...@gmail.com> #20Oct 31, 2019 07:27PM

Same here. It is not fixed. Can you reopen and look again?

ko...@gmail.com <ko...@gmail.com> #21Oct 31, 2019 08:30PM

Same problem here

scripts_linux_mk-sdcard-img.sh

6.2 KB

View

Download

ab...@hotmail.com <ab...@hotmail.com> Feb 8, 2020 07:14AM

scripts_linux_mk-sdcard-img.sh

6.2 KB

View

Download

fr...@gmail.com <fr...@gmail.com> #22Feb 29, 2020 04:42PM

Same problem here

jd...@gmail.com <jd...@gmail.com> #23Mar 7, 2020 07:26AM

Same problem here

jo...@gmail.com <jo...@gmail.com> #24Apr 9, 2020 11:19PM

Same problem here, currently using version 2.7.7

ge...@gmail.com <ge...@gmail.com> #25Apr 15, 2020 11:09PM

same problem here

Message last modified on Apr 15, 2020 11:10PM

js...@gmail.com <js...@gmail.com> #26Apr 23, 2020 12:22AM

testing

da...@gmail.com <da...@gmail.com> #27Apr 24, 2020 12:19AM

-hotlist Google domain
+hotlist 2367385

Message last modified on Apr 24, 2020 12:31AM

[Deleted User] <[Deleted User]> #28Apr 24, 2020 03:40PM

---------- ထပ်ဆင့်ပေးပို့သည့်မက်ဆေ့ချ် ----------
From: <buganizer-system@google.com>
Date: 24 ဧပြီ 2020 6:50 AM
Subject: Re:

Issue 134613180

: Updating to platform tools 29.0.0 results in
continuous stream of adb.exe crash dialogs, at least on Windows 8.1
To: <b-system+591006804@google.com>
မိတ္တူ: <kok129873@gmail.com>

Replying to this email means your email address will be shared with the
team that works on this product.

https://issuetracker.google.com/issues/134613180

*Changed*

*da...@gmail.com <da...@gmail.com> added

comment #27

https://issuetracker.google.com/issues/134613180#comment27>:*

-hotlist Google domain +hotlist 2367385

_______________________________

*Reference Info: 134613180 Updating to platform tools 29.0.0 results in
continuous stream of adb.exe crash dialogs, at least on Windows 8.1*
component: Android Public Tracker > App Development > Android Studio >
Emulator <

https://issuetracker.google.com/components/192727>
status: Fixed
reporter: le...@gmail.com
assignee: jm...@google.com
cc: bo...@google.com, jm...@google.com, le...@gmail.com
type: Bug
priority: P1
severity: S2
duplicate issue: 134627083
<

https://issuetracker.google.com/issues/134627083>
hotlist: Reviewed (L1) <

https://issuetracker.google.com/hotlists/712415>
retention: Component default

Generated by Google IssueTracker notification system

You're receiving this email because you are subscribed to updates on Google
IssueTracker

issue 134613180

https://issuetracker.google.com/issues/134613180> where you have the role:
starred.
Unsubscribe from this issue.
<

https://issuetracker.google.com/issues/134613180?unsubscribe=true>

[Deleted User] <[Deleted User]> #29May 10, 2020 12:12PM

29 ေဖ 2020 11:12 PM တွင် <buganizer-system@google.com> ရေးခဲ့သည်မှာ။ ။

- Show quoted text -

an...@gmail.com <an...@gmail.com> #30May 31, 2020 06:37AM

Mmmank

ou...@gmail.com <ou...@gmail.com> #31Jul 7, 2020 11:08AM

TITsovneMakara@gmail.com

Message last modified on Jul 7, 2020 11:09AM

aa...@gmail.com <aa...@gmail.com> #32Oct 5, 2020 02:09PM

Feedback

aa...@gmail.com <aa...@gmail.com> #33Oct 5, 2020 02:10PM

aaireill111@gmail.com

ab...@gmail.com <ab...@gmail.com> #34Nov 19, 2020 12:49AM

انتهاك خصوصية

ab...@gmail.com <ab...@gmail.com> #35Dec 15, 2020 07:06AM

My privacy was violated by an unidentified person, opening several web pages with all my personal data, and I have a forged and incorrect user agreement for my account. I ask you to block the unknown person and help me update my data.

Please help me to modify the privacy of my account to private privacy and not to participate categorically and the presence of security for privacy and not tampering with it.

za...@gmail.com <za...@gmail.com> #36Dec 15, 2020 07:14AM

On Wed, Nov 18, 2020, 6:50 PM <buganizer-system@google.com> wrote:

- Show quoted text -

dd...@gmail.com <dd...@gmail.com> #37Dec 16, 2020 06:01AM

What is this and why am I in this can someone please explain

On Tue, Dec 15, 2020, 2:06 AM <buganizer-system@google.com> wrote:

- Show quoted text -

06...@gmail.com <06...@gmail.com> #38Dec 28, 2020 02:05PM

https://console.aws.amazon.com/support/home?#/case/?caseId=7795210011&displayId=7795210011&language=en

ka...@gmail.com <ka...@gmail.com> #39Jan 27, 2021 04:17AM

حلم 95458 من مصر 🇪🇬 201551145918كرم محمد عبد العزيز عبد العال حلم حلم حلم حلم حلم حلم حلم 2021

ka...@gmail.com <ka...@gmail.com> #40Jan 27, 2021 04:20AM

حلم حلم حلم حلم حلم حلم حلم 95458 مصر 🇪🇬 محافظة الاسكندرية كرم محمد عبد العزيز عبد العال 201551145918 حلم حلم حلم حلم يارب شيك يارب mbc 2021

si...@gmail.com <si...@gmail.com> #41Mar 19, 2021 01:36PM

I installed 29.0.1 via the SDK Manager. This problem feels fixed to me.

to...@gmail.com <to...@gmail.com> #42Apr 23, 2021 07:45PM

https://drive.google.com/file/d/0B8TBbCbAQEhJVDJYWmtpMm1GSkU/view?usp=drive_web (225)

ab...@gmail.com <ab...@gmail.com> #43Sep 11, 2021 12:11PM

hi my name abdulrahman afghan
help me japan tool

fl...@gmail.com <fl...@gmail.com> #44Sep 11, 2021 10:53PM

On Sat, Sep 11, 2021, 8:11 AM <buganizer-system@google.com> wrote:

- Show quoted text -

m....@gmail.com <m....@gmail.com> #45Sep 12, 2021 02:10AM

good bay!

1381662341mohamadsalmanpor

در تاریخ شنبه ۱۱ سپتامبر ۲۰۲۱،‏ ۱۶:۴۱ <buganizer-system@google.com> نوشت:

- Show quoted text -

mi...@gmail.com <mi...@gmail.com> #46Oct 2, 2021 10:50AM

https://drive.google.com/file/d/1IdB9_C-qvVKHshc-xekJws6oo-FScA15/view?usp=drive_web (Backup-codes-miwavaso.txt)

m....@gmail.com <m....@gmail.com> #47Oct 2, 2021 11:03AM

1381662341:issu

1381662341mohamadsalmanpor

در تاریخ شنبه ۲ اکتبر ۲۰۲۱،‏ ۲:۲۰ بعدازظهر <buganizer-system@google.com>
نوشت:

- Show quoted text -

mo...@gmail.com <mo...@gmail.com> #48Oct 4, 2021 11:51AM

Hjh

at...@gmail.com <at...@gmail.com> #49Dec 25, 2022 11:26AM

My device esim update 13 on drive

Message last modified on Dec 25, 2022 11:34AM

ly...@gmail.com <ly...@gmail.com> #50Oct 30, 2023 10:16PM

mi...@gmail.com <mi...@gmail.com> #51Nov 29, 2023 10:35PM

El sáb., 11 de septiembre de 2021 8:11 p. m., <buganizer-system@google.com>
escribió:

- Show quoted text -

Issue 134613180

Description

Issue summary

Comments

mi...@gtempaccount.com <mi...@gtempaccount.com> #2Jun 6, 2019 12:28PM

uc...@google.com <uc...@google.com> Jun 6, 2019 09:24PM

lf...@google.com <lf...@google.com> #3Jun 7, 2019 02:59PM

1c...@gmail.com <1c...@gmail.com> #4Jun 7, 2019 03:17PM

be...@gmail.com <be...@gmail.com> #5Jun 7, 2019 07:04PM

jm...@google.com <jm...@google.com> #6Jun 11, 2019 07:40PM

le...@gmail.com <le...@gmail.com> #7Jun 11, 2019 09:06PM

v....@gmail.com <v....@gmail.com> #8Jul 14, 2019 12:02PM

jm...@google.com <jm...@google.com> #9Jul 15, 2019 08:12PM

cv...@gmail.com <cv...@gmail.com> #10Jul 16, 2019 12:23AM

cv...@gmail.com <cv...@gmail.com> #11Jul 16, 2019 12:27AM

si...@gmail.com <si...@gmail.com> #12Jul 16, 2019 05:12PM

si...@gmail.com <si...@gmail.com> #13Jul 24, 2019 07:13PM

3l...@gmail.com <3l...@gmail.com> #14Jul 29, 2019 05:36PM

mo...@gmail.com <mo...@gmail.com> #15Aug 16, 2019 05:55AM

mo...@gmail.com <mo...@gmail.com> #16Aug 16, 2019 05:56AM

le...@gmail.com <le...@gmail.com> #17Sep 26, 2019 11:51PM

zo...@gmail.com <zo...@gmail.com> #18Sep 29, 2019 01:05PM

za...@gmail.com <za...@gmail.com> #19Oct 13, 2019 11:32AM

ke...@gmail.com <ke...@gmail.com> #20Oct 31, 2019 07:27PM

ko...@gmail.com <ko...@gmail.com> #21Oct 31, 2019 08:30PM

ab...@hotmail.com <ab...@hotmail.com> Feb 8, 2020 07:14AM

fr...@gmail.com <fr...@gmail.com> #22Feb 29, 2020 04:42PM

jd...@gmail.com <jd...@gmail.com> #23Mar 7, 2020 07:26AM

jo...@gmail.com <jo...@gmail.com> #24Apr 9, 2020 11:19PM

ge...@gmail.com <ge...@gmail.com> #25Apr 15, 2020 11:09PM

js...@gmail.com <js...@gmail.com> #26Apr 23, 2020 12:22AM

da...@gmail.com <da...@gmail.com> #27Apr 24, 2020 12:19AM

[Deleted User] <[Deleted User]> #28Apr 24, 2020 03:40PM

[Deleted User] <[Deleted User]> #29May 10, 2020 12:12PM

an...@gmail.com <an...@gmail.com> #30May 31, 2020 06:37AM

ou...@gmail.com <ou...@gmail.com> #31Jul 7, 2020 11:08AM

aa...@gmail.com <aa...@gmail.com> #32Oct 5, 2020 02:09PM

aa...@gmail.com <aa...@gmail.com> #33Oct 5, 2020 02:10PM

ab...@gmail.com <ab...@gmail.com> #34Nov 19, 2020 12:49AM

ab...@gmail.com <ab...@gmail.com> #35Dec 15, 2020 07:06AM

za...@gmail.com <za...@gmail.com> #36Dec 15, 2020 07:14AM

dd...@gmail.com <dd...@gmail.com> #37Dec 16, 2020 06:01AM

06...@gmail.com <06...@gmail.com> #38Dec 28, 2020 02:05PM

ka...@gmail.com <ka...@gmail.com> #39Jan 27, 2021 04:17AM

ka...@gmail.com <ka...@gmail.com> #40Jan 27, 2021 04:20AM

si...@gmail.com <si...@gmail.com> #41Mar 19, 2021 01:36PM

to...@gmail.com <to...@gmail.com> #42Apr 23, 2021 07:45PM

ab...@gmail.com <ab...@gmail.com> #43Sep 11, 2021 12:11PM

fl...@gmail.com <fl...@gmail.com> #44Sep 11, 2021 10:53PM

m....@gmail.com <m....@gmail.com> #45Sep 12, 2021 02:10AM

mi...@gmail.com <mi...@gmail.com> #46Oct 2, 2021 10:50AM

m....@gmail.com <m....@gmail.com> #47Oct 2, 2021 11:03AM

mo...@gmail.com <mo...@gmail.com> #48Oct 4, 2021 11:51AM

at...@gmail.com <at...@gmail.com> #49Dec 25, 2022 11:26AM

ly...@gmail.com <ly...@gmail.com> #50Oct 30, 2023 10:16PM

mi...@gmail.com <mi...@gmail.com> #51Nov 29, 2023 10:35PM

Add comment

Issue metadata