Status Update
Comments
ra...@google.com <ra...@google.com> #2
Thank you for reporting this issue. Please upload the AOSP patch following this guidance
if...@gmail.com <if...@gmail.com> #3
Change-Id: I9594ce3d2276127d2a585b9c630b672c857bede7
ra...@google.com <ra...@google.com> #4
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
if...@gmail.com <if...@gmail.com> #5
yes, the application package is iam.rebirth.breathe
if...@gmail.com <if...@gmail.com> #6
On Thu, Jan 2, 2025 at 8:38 PM <buganizer-system@google.com> wrote:
if...@gmail.com <if...@gmail.com> #7
On Thu, Jan 2, 2025 at 8:38 PM <buganizer-system@google.com> wrote:
ra...@google.com <ra...@google.com> #8
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
ra...@google.com <ra...@google.com> #9
Thanks for reporting this issue. Please confirm if the issue is still happening on the latest public Android 15 build. If yes, please provide a bug report after reproducing the issue.
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:
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.
Note: Please upload the bug report to google drive and share the folder to android-bugreport@google.com, then share the link here.
if...@gmail.com <if...@gmail.com> #10
latest public Android 15 build.
Here is the bug report after reproducing the issue:
On Thu, Jan 9, 2025 at 3:07 PM <buganizer-system@google.com> wrote:
ra...@google.com <ra...@google.com> #11
Thanks for the information. We observed that you have checked this issue on an old Android 15 build.
As mentioned in
Could you please check on this build and let us know if this issue is still reproducible.
if...@gmail.com <if...@gmail.com> #12
AP4A.250105.002, I wanted to clarify that I conducted my tests using the
Android Studio emulator.
The latest build version available on the emulator is AEZA.240806.036. I
haven't received an update to build AP4A.250105.002 on the emulator.
I'm unsure if there's another way to update the emulator to this specific
build. If there is a method, please let me know the specific steps or
provide relevant resources.
Additionally, I have a question about the fix for this issue. Is it
necessary to update the Android system version to resolve it? Many of our
users may not be able to upgrade to Android 15. Understanding if the fix is
dependent on Android 15 is crucial for us to plan accordingly.
Thank you for your time and assistance.
On Sat, Jan 11, 2025 at 5:33 PM <buganizer-system@google.com> wrote:
ra...@google.com <ra...@google.com>
rk...@google.com <rk...@google.com> #13
*Device used: *Sony XQ-AT52
Regarding your request to test on build AP4A.250105.002, I wanted to clarify that I conducted my tests using the Android Studio emulator.
Multiple users report this, not device-specific.
Hi, could you please clarify if this is an Emulator specific or also reproes on Sony and other devices?
if...@gmail.com <if...@gmail.com> #14
all have this problem. I mentioned the emulator because I don't have a
phone with Android 15, so I used the emulator to collect logs. The earliest
log I submitted before was collected on my Sony phone.
On Thu, Jan 16, 2025 at 2:07 AM <buganizer-system@google.com> wrote:
rk...@google.com <rk...@google.com> #15
Ram, please triage this into Google Play.
ra...@google.com <ra...@google.com> #16
Thanks, we have shared this with our product and engineering team and will update this issue with more information as it becomes available.
ra...@google.com <ra...@google.com> #17
Thanks for reporting this issue. Please clear the play store cache and data, then try installing the app again. If issue is still reproducible, please capture a fresh bugreport and share with us.
if...@gmail.com <if...@gmail.com> #18
the app again, but the same issue persists, with the prompt: Download
failed. Here is the latest bug report, please help investigate 🙏
On Tue, Feb 4, 2025 at 10:12 PM <buganizer-system@google.com> wrote:
if...@gmail.com <if...@gmail.com> #19
What is the progress on this issue? Please let me know if you need me to
provide more information.
On Wed, Feb 5, 2025 at 1:50 PM Zen Chan <ifallchan@gmail.com> wrote:
Description
Users can't download Breathe2Heal via Play Store mobile app, showing "Can't download Breathe2Heal. Try again..." (Log attached).
Key Observations:
Tried Solutions: