Infeasible
Status Update
Comments
ra...@google.com <ra...@google.com> #2
Information redacted by Android Beta Feedback.
le...@google.com <le...@google.com>
le...@google.com <le...@google.com>
ds...@google.com <ds...@google.com> #3
From the bug report, we could see that there are no more [Dialer-related logs] and also you have tested the issue in the Dialer version v151, and now v152+ is now available in the Play Store.
So, we request you check the issue in the latest Dialer version and help us with the new bug report and video recording of the issue to investigate further.
While capturing the bug report, please refer to
If the device is not set to Developer mode, Please follow the below path to enable developer options and capture the bug report accordingly.
- Navigate to Settings > Click on About Phone > Click on Software Information > Click 7 times on Build Number continuously. This will allow you to Enable the Developer options
- Navigate to Developer Options and Select Logger sizes per log buffer to maximum available in the device.
- Click on the bug report option and select Full Report and click on Report.
- After a moment, you get a notification that the bug report is ready
- Please share the bug report accordingly.
Description
First, please search through existing issues to ensure that the bug has not already been reported. You can start the search here:
If the issue has already been reported, you can click the star next to the issue number to subscribe and receive updates. We prioritize responding to the issues with the most stars. You can also comment on the issue to provide any details of your experience with it.
If your issue has not been reported, please provide all of the following:
-----------------------------------------------------------------------------------------------------------------------------
A short description of the issue:
A small code sample that reliably reproduces the issue. The sample should run as-is or with minimal setup, without external dependencies.
What steps will reproduce the problem?
1.
When I type a name in create topics api, if the last character is a spacing character (' ') , a topic is created that cannot be used in the classroom.
=> I think team Google needs to apply trim() to name of create topics api.
2.
3.
What is the expected output? What do you see instead? If you see error messages, please provide them.
Please provide any additional information below, such as number of users impacted, IDs, or whether you have been able to find a workaround.