Fixed
Status Update
Comments
da...@sucharda.cz <da...@sucharda.cz> #2
One reason that makes this option better than recent tasks:
I can't take a screenshot of outside the tasks.
I can't even take screenshot of the recent tasks itself.
See here:
https://issuetracker.google.com/issues/158720125
I can't take a screenshot of outside the tasks.
I can't even take screenshot of the recent tasks itself.
See here:
jb...@google.com <jb...@google.com> #3
Thank you for the report. We’ve shared this with our product and engineering teams and will continue to provide updates as more information becomes available.
da...@sucharda.cz <da...@sucharda.cz> #4
I agree, biggest disappointment about the new power menu is the lack of the screenshot button
da...@sucharda.cz <da...@sucharda.cz> #5
Yeah bring it back please. I used it so often
jb...@google.com <jb...@google.com>
cl...@google.com <cl...@google.com> #6
I can agree that's how I take all my screenshots and it feels weird not having it there
ap...@google.com <ap...@google.com> #7
Why mark as duplicate to a place that isn't accessible to anyone?
pr...@google.com <pr...@google.com> #8
agree, please bring back screenshot button when I click power button
Description
Component used: Navigation
Version used: 2.5.1 and 2.5.2
Last known working version: 2.3.5
Devices/Android versions reproduced on: Huawei P20 Light / AN 9 (EMUI 9.1.0)
So our navigation is kinda complex so I will try to simplify the configuration. If there is a nested graph with arguments which cannot be null (and no default value is supplied) and
popUpTo
is used to remove nested graph during destination (nested) navigation it tries to recreate nested graph as a parent for the destination being navigated to.So now if the navigation is triggered like this:
It will pop fragments from back stack, but it will not change parent for
ChildFragment2
which will be set tochildNavGraph
and since it is not in the back stack anymore it will try to recreate it with default values. ButargumentLong
is not nullable and has no default value so it will crash:Note: Interesting thing is that it does not crash with non-nullable String argument for some reason (ah I see, it is because String NavType is nullable by default:
StringType: NavType<String?>
vsLongType: NavType<Long>
).Possible fixes for us:
popUpTo
to pop parent (navGraph) of a Fragment (node) from XML but usepopBackStack
from code instead.argumentLong
.Basically I am not sure if this an intended behavior or a bug. Gonna mark it as a bug because it worked in 2.3.5. I understand that Destination should have a parent but what is the reason to create a parent that does not exist and will never be displayed in this case, since it was already poped and thus it should not be displayed to the user.
At the moment two solutions come to mind:
LongType
and other types nullable same asStringType
. Again not sure if this can be done and it probably is not a proper solution (change).There might of course be other solutions that I cannot see.
Thank you for your time and help.