Fixed
Status Update
Comments
jb...@google.com <jb...@google.com>
lo...@gmail.com <lo...@gmail.com> #2
Hello
ap...@google.com <ap...@google.com> #3
Hello there,
Thank you for reporting this! However, it seems that this is the expected behavior as the method will return the valid named ranges. Would you be interested in turning this into a feature request instead? If yes, how would it impact your organization in terms of costs and productivity?
cl...@google.com <cl...@google.com> #4
Sure, please make it a feature request. It would be useful for automating the maintenance of named ranges across a large number of sheets, which is what I was trying to implement 3 years ago when I logged this issue. I don't know how much time is spent manually checking and fixing corrupted named ranges, but certainly some amount each week.
lo...@gmail.com <lo...@gmail.com> #5
Hi,
Named ranges help a lot to write dynamic scripts that do not require static range references. And it is crucial to have a good way to define, delete and manage named ranges within app scripts. Especially manage invalid named ranges.
Named ranges help a lot to write dynamic scripts that do not require static range references. And it is crucial to have a good way to define, delete and manage named ranges within app scripts. Especially manage invalid named ranges.
cl...@google.com <cl...@google.com> #6
Thank you for the details provided! I have forwarded them internally.
Best regards
Description
Component used: Navigation Version used: 2.7.7 - success 2.8.0 - failed 2.8.5 - failed 2.9.0-alpha04 - failed
Devices/Android versions reproduced on: tested API 30, 33. i think any affected
Sample project to trigger the issue. in the attachments
A screenrecord or screenshots showing the issue (if UI related). in the attachments
Issue: wildcard segment in deep link stopped work as expected since 2.8.0 and till latest 2.9.0-alpha04
spent ~2 days to understand the reason!!! when examples from internet work, but my app - not.