Fixed
Status Update
No update yet.
Comments
mi...@gtempaccount.com
One more detail here.
The body of navigateUp() method of NavController class (1.0.0-rc01) looks like this:
if (mBackStack.size() == 1) {
// If there's only one entry, then we've deep linked into a specific destination
// on another task so we need to find the parent and start our task from there
...
} else {
return popBackStack();
}
If I put a breakpoint on the very first line of that code and invoke this method anyhow, I can see that the size of mBackStack is actually 2 (with both root and child fragments).
So, the code doesn't consider the current case a deeplink case, but as a regular opening of the child destination.
The body of navigateUp() method of NavController class (1.0.0-rc01) looks like this:
if (mBackStack.size() == 1) {
// If there's only one entry, then we've deep linked into a specific destination
// on another task so we need to find the parent and start our task from there
...
} else {
return popBackStack();
}
If I put a breakpoint on the very first line of that code and invoke this method anyhow, I can see that the size of mBackStack is actually 2 (with both root and child fragments).
So, the code doesn't consider the current case a deeplink case, but as a regular opening of the child destination.
uc...@google.com
lf...@google.com
1c...@gmail.com
Partially agree, but my case doesn't use nested graphs at all, so my issue is just simpler.
However, the actual problem seems to be the same: the library treats absence of Intent.FLAG_ACTIVITY_NEW_TASK as it is actually set, because all 'start destinations' are still added before the actual deeplink destination (as it is explained in the documentation where the flag is set).
However, the actual problem seems to be the same: the library treats absence of Intent.FLAG_ACTIVITY_NEW_TASK as it is actually set, because all 'start destinations' are still added before the actual deeplink destination (as it is explained in the documentation where the flag is set).
be...@gmail.com
This is a regression caused by https://android-review.googlesource.com/833717 where the NavGraph destinations would always be added to the back stack (it isn't both the root and child fragments, but the root graph and the child fragment) to avoid IllegalArgumentExceptions. Unfortunately, that broke the navigateUp() behavior, which is something we'll fix :)
jm...@google.com
Project: platform/frameworks/support
Branch: androidx-master-dev
commit 781d0178da33d84f615b409b17975c8ba290401c
Author: Ian Lake <ilake@google.com>
Date: Mon Feb 25 15:38:23 2019
Fix navigateUp() logic when on another app's task
When using deep linking on another app's task,
only the final destination is created, ensuring that
hitting the system back button goes back to the
other app. The Up button, via navigateUp(), should
take users to your own task on the parent destination.
Recent changes made it so that we always add the
parent NavGraphs to the back stack, meaning the simple
check of back stack size == 1 does not properly handle
this change in behavior so instead we need to check for
the number of non-NavGraph destinations on the back
stack.
Test: new NavControllerActivityTest
BUG: 126082008
Change-Id: I7bf18d38e1cdd3818e7414ba44d84df0abd81b88
M navigation/runtime/src/androidTest/AndroidManifest.xml
A navigation/runtime/src/androidTest/java/androidx/navigation/NavControllerActivityTest.kt
M navigation/runtime/src/main/java/androidx/navigation/NavController.java
https://android-review.googlesource.com/912258
https://goto.google.com/android-sha1/781d0178da33d84f615b409b17975c8ba290401c
Branch: androidx-master-dev
commit 781d0178da33d84f615b409b17975c8ba290401c
Author: Ian Lake <ilake@google.com>
Date: Mon Feb 25 15:38:23 2019
Fix navigateUp() logic when on another app's task
When using deep linking on another app's task,
only the final destination is created, ensuring that
hitting the system back button goes back to the
other app. The Up button, via navigateUp(), should
take users to your own task on the parent destination.
Recent changes made it so that we always add the
parent NavGraphs to the back stack, meaning the simple
check of back stack size == 1 does not properly handle
this change in behavior so instead we need to check for
the number of non-NavGraph destinations on the back
stack.
Test: new NavControllerActivityTest
BUG: 126082008
Change-Id: I7bf18d38e1cdd3818e7414ba44d84df0abd81b88
M navigation/runtime/src/androidTest/AndroidManifest.xml
A navigation/runtime/src/androidTest/java/androidx/navigation/NavControllerActivityTest.kt
M navigation/runtime/src/main/java/androidx/navigation/NavController.java
le...@gmail.com
A fix will be available in Navigation 1.0.0-rc02. Thanks for reporting it and the great sample app!
v....@gmail.com
Thanks, Ian.
jm...@google.com
That's not related to adb, please file a separate bug.
cv...@gmail.com
Hello,
I close a virtual device and after a while my notebook's cpu goes to 100% then my windows 10 system crash.
Android Studio 3.4.2
Build #AI-183.6156.11.34.5692245, built on June 27, 2019
JRE: 1.8.0_152-release-1343-b01 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0
Nome do Log: System
Fonte: Microsoft-Windows-Kernel-Power
Data: 15/07/2019 17:10:22
Identificação do Evento:41
Categoria da Tarefa:(63)
Nível: Nível Crítico
Palavras-chave:(70368744177664),(2)
Usuário: SISTEMA
Computador: LAPTOP-56J1L2VC
Descrição:
O sistema foi reiniciado sem um desligamento correto primeiro. Esse erro pode ser causado quando o sistema para de responder, trava ou fica sem energia inesperadamente.
XML de Evento:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event ">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" />
<EventID>41</EventID>
<Version>6</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2019-07-15T20:10:22.180468100Z" />
<EventRecordID>7466</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>LAPTOP-56J1L2VC</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">159</Data>
<Data Name="BugcheckParameter1">0x3</Data>
<Data Name="BugcheckParameter2">0xffff8c837a293060</Data>
<Data Name="BugcheckParameter3">0xfffff8051d7f3c00</Data>
<Data Name="BugcheckParameter4">0xffff8c83808e7010</Data>
<Data Name="SleepInProgress">0</Data>
<Data Name="PowerButtonTimestamp">0</Data>
<Data Name="BootAppStatus">0</Data>
<Data Name="Checkpoint">41</Data>
<Data Name="ConnectedStandbyInProgress">false</Data>
<Data Name="SystemSleepTransitionsToOn">1</Data>
<Data Name="CsEntryScenarioInstanceId">0</Data>
<Data Name="BugcheckInfoFromEFI">false</Data>
<Data Name="CheckpointStatus">0</Data>
</EventData>
</Event>
I close a virtual device and after a while my notebook's cpu goes to 100% then my windows 10 system crash.
Android Studio 3.4.2
Build #AI-183.6156.11.34.5692245, built on June 27, 2019
JRE: 1.8.0_152-release-1343-b01 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0
Nome do Log: System
Fonte: Microsoft-Windows-Kernel-Power
Data: 15/07/2019 17:10:22
Identificação do Evento:41
Categoria da Tarefa:(63)
Nível: Nível Crítico
Palavras-chave:(70368744177664),(2)
Usuário: SISTEMA
Computador: LAPTOP-56J1L2VC
Descrição:
O sistema foi reiniciado sem um desligamento correto primeiro. Esse erro pode ser causado quando o sistema para de responder, trava ou fica sem energia inesperadamente.
XML de Evento:
<Event xmlns="
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" />
<EventID>41</EventID>
<Version>6</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2019-07-15T20:10:22.180468100Z" />
<EventRecordID>7466</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>LAPTOP-56J1L2VC</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">159</Data>
<Data Name="BugcheckParameter1">0x3</Data>
<Data Name="BugcheckParameter2">0xffff8c837a293060</Data>
<Data Name="BugcheckParameter3">0xfffff8051d7f3c00</Data>
<Data Name="BugcheckParameter4">0xffff8c83808e7010</Data>
<Data Name="SleepInProgress">0</Data>
<Data Name="PowerButtonTimestamp">0</Data>
<Data Name="BootAppStatus">0</Data>
<Data Name="Checkpoint">41</Data>
<Data Name="ConnectedStandbyInProgress">false</Data>
<Data Name="SystemSleepTransitionsToOn">1</Data>
<Data Name="CsEntryScenarioInstanceId">0</Data>
<Data Name="BugcheckInfoFromEFI">false</Data>
<Data Name="CheckpointStatus">0</Data>
</EventData>
</Event>
cv...@gmail.com
si...@gmail.com
i seem to have a different issue. i downloaded the tools and unpack it on my desktop. i can run sqlite3.exe, but i can't run any of the other .exe files. i found an app that needs a root permission to change my screen in one click to grayscale. and i need the adb.exe file to put a command into my phone.
when i click it, it briefly shows a window and then it disapears again.
i've tried a restart, compability to windows 8,7 and xp and the windows troubleshooter. i run windows 10 on a asus rog
https://www.asus.com/nl/ROG-Republic-Of-Gamers/ROG-GL502VS/specifications/
did i do something wrong?
when i click it, it briefly shows a window and then it disapears again.
i've tried a restart, compability to windows 8,7 and xp and the windows troubleshooter. i run windows 10 on a asus rog
did i do something wrong?
si...@gmail.com
okay don't worry guys. you shouldn't be clicking the adb.exe directly. you should open a comand prompt. then you can use this via the comand prompt or something. you'll find a better explanation here
https://www.xda-developers.com/install-adb-windows-macos-linux/
i can now turn my phone to grayscale with a simple click :)
i can now turn my phone to grayscale with a simple click :)
3l...@gmail.com
mo...@gmail.com
Nothing really fix the problem. I can't run the adb at all. "unable to connect to adb. check the event log"
What should we do now? go back to older versions of Android studio?
What should we do now? go back to older versions of Android studio?
mo...@gmail.com
I guess Im in wrong place it's 2 am now that;s why :)
le...@gmail.com
Delete
zo...@gmail.com
Hmmm
za...@gmail.com
Ok
ab...@hotmail.com
fr...@gmail.com
NA
jo...@gmail.com
Fu
ge...@gmail.com
Thanks
js...@gmail.com
testing
da...@gmail.com
-hotlist Google domain
+hotlist 2367385
+hotlist 2367385
[Deleted User] <[Deleted User]>
---------- ထပ်ဆင့်ပေးပို့သည့်မက်ဆေ့ချ် ----------
From: <buganizer-system@google.com>
Date: 24 ဧပြီ 2020 6:50 AM
Subject: Re:
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
<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
<https://issuetracker.google.com/issues/134613180 > where you have the role:
starred.
Unsubscribe from this issue.
<https://issuetracker.google.com/issues/134613180?unsubscribe=true >
From: <buganizer-system@google.com>
Date: 24 ဧပြီ 2020 6:50 AM
Subject: Re:
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.
*Changed*
*da...@gmail.com <da...@gmail.com> added
<
-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 <
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
<
hotlist: Reviewed (L1) <
retention: Component default
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google
IssueTracker
<
starred.
Unsubscribe from this issue.
<
[Deleted User] <[Deleted User]>
an...@gmail.com
Mmmank
aa...@gmail.com
Feedback
aa...@gmail.com
ab...@gmail.com
انتهاك خصوصية
ab...@gmail.com
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
dd...@gmail.com
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:
On Tue, Dec 15, 2020, 2:06 AM <buganizer-system@google.com> wrote:
ka...@gmail.com
حلم 95458 من مصر 🇪🇬 201551145918كرم محمد عبد العزيز عبد العال حلم حلم حلم حلم حلم حلم حلم 2021
ka...@gmail.com
حلم حلم حلم حلم حلم حلم حلم 95458 مصر 🇪🇬 محافظة الاسكندرية كرم محمد عبد العزيز عبد العال 201551145918 حلم حلم حلم حلم يارب شيك يارب mbc 2021
si...@gmail.com
I installed 29.0.1 via the SDK Manager. This problem feels fixed to me.
ab...@gmail.com
hi my name abdulrahman afghan
help me japan tool
help me japan tool
fl...@gmail.com
m....@gmail.com
good bay!
1381662341mohamadsalmanpor
در تاریخ شنبه ۱۱ سپتامبر ۲۰۲۱، ۱۶:۴۱ <buganizer-system@google.com> نوشت:
1381662341mohamadsalmanpor
در تاریخ شنبه ۱۱ سپتامبر ۲۰۲۱، ۱۶:۴۱ <buganizer-system@google.com> نوشت:
m....@gmail.com
1381662341:issu
1381662341mohamadsalmanpor
در تاریخ شنبه ۲ اکتبر ۲۰۲۱، ۲:۲۰ بعدازظهر <buganizer-system@google.com>
نوشت:
1381662341mohamadsalmanpor
در تاریخ شنبه ۲ اکتبر ۲۰۲۱، ۲:۲۰ بعدازظهر <buganizer-system@google.com>
نوشت:
mo...@gmail.com
Hjh
at...@gmail.com
My device esim update 13 on drive
ly...@gmail.com
hi
Description
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:
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.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