Status Update
No update yet.
Comments
il...@google.com
il...@google.com
ap...@google.com
Hello,
Thank you for reaching out to us with your request.
We have duly noted your feedback and will thoroughly validate it. While we cannot provide an estimated time of implementation or guarantee the fulfillment of the issue, please be assured that your input is highly valued. Your feedback enables us to enhance our products and services.
We appreciate your continued trust and support in improving our Google Cloud Platform products. In case you want to report a new issue, Please do not hesitate to create a new issue on the
Once again, we sincerely appreciate your valuable feedback; Thank you for your understanding and collaboration.
jb...@google.com
pr...@google.com
Being able to view the available backups in console would be helpful
Description
Component used: Navigation
Version used: 2.4.0
Devices/Android versions reproduced on: This is a documentation issue rather than a software issue.
If this is a bug in the library, we would appreciate if you could attach:
The documentation for
The documentation is a bit confusing and what it says is not always the case. To quote Ian Lake, "what actually happens is that the saved state is associated with a particular ID. The saved state of an ID is restored when you navigate to that ID with restoreState as true. The tricky part is the inclusive flag on popUpTo. Ideally the ID that the saved state is saved under is the ID of the last destination you pop. I.e., if you have A -> B -> C and you popUpTo A with inclusive as false, the state would be saved under the ID of B And while we do always do that (save the state under the ID of the last thing popped), we also need to do one other thing - we save the state under the ID that you passed to popUpTo. This is how you can actually get back to the first saved state"
This part of the documentation should be removed entirely or updated to reflect how things actually work.