Status Update
Comments
an...@gmail.com <an...@gmail.com> #2
Androidx.activity actually doesn't do anything with those APIs and this behavior comes from the framework. Moving it to that component.
pu...@google.com <pu...@google.com>
je...@google.com <je...@google.com> #3
Thank you for letting me know. Then which subject should we have instead of Android Public Tracker > App Development > Jetpack (androidx) > Activity ?
pa...@amexgbt.com <pa...@amexgbt.com> #4
Android Public Tracker > Framework is the correct component for framework issues.
ol...@gmx.net <ol...@gmx.net> #5
Please provide the following additional information:
Please mention the steps to be followed for reproducing the issue with the given sample apk.
Android bug report capturing
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory.
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Screen record of the issue, for clarity
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.
er...@quipper.com <er...@quipper.com> #6
1 - If you click on "click me" button in the 1st Activity, 2nd Activity will start with option bundle. 2 - If you search in searchView, button in the 2nd Activity will be gone. 3 - click on device home button and then resume the app again, button in 2nd activity becomes visible which is unexpected. 4 - if you search again, click on device home button and resume the app again, button in the 2nd Activity will be gone as expected. (Unexpected behavior happens just in the 1st search)
Bug report capturing :
Screen recording :
Sample code :
APK :
an...@gmail.com <an...@gmail.com> #7
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
mw...@gmail.com <mw...@gmail.com> #8
ms...@cadence.com <ms...@cadence.com> #9
en-US-Neural-J
en-US-Wavenet-D
en-US-Studio-M
en-US-Polyglot-1
en-US-Neural-C
en-US-Wavenet-C
en-US-Studio-O
en-US-Neural-*
Please re-enable these voices for text-to-speech UI.
Thanks you.
pa...@gmail.com <pa...@gmail.com> #10
Any updates please? It's been 2 weeks now, and we still haven't heard any updates. We appreciate for any updates. Thank you.
er...@quipper.com <er...@quipper.com> #11
Our production is being severely affected by this bug. Any update you can share would be greatly appreciated. Thank you in advance.
Description
Does anyone know if this is a temporary measure or a permanent one.. This is extremely concerning for us as we use these voices all the time?