Status Update
No update yet.
Comments
su...@google.com
su...@google.com
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Are you facing an issue with this apk
Please mention the steps to be followed for reproducing the issue.
Please confirm if this issue is specific to the application or emulator .
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:
Screen record of the issue
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
Attach the file to this issue.
To Capture the issue in a screenshot Press the volume down and power buttons simultaneously. The image will appear in the picture gallery. Attach the screenshot image to this issue.
Note: Please avoid uploading directly to the issue using attachments. Please upload to google drive and share the folder to
bi...@gmail.com
I now need to upgrade WristMap to API30 to meet newer Play store requirements - now a minimum of API30 for Wear OS
At API 28, Wristmap used a custom toast view, which is not allowed at API30.
I have changed the Toast to a simple text view, as per the code in my initial report, and inline with the current Toast documentation, but the toast is blocked.
I have attached a webm of the playstore (API 28) version of WristMap showing a custom toast from a click on the Lat+Lon complication.
An equivalent video of my API30 version would look the same but without the toast showing.
bi...@gmail.com
bi...@gmail.com
bi...@gmail.com
bi...@gmail.com
su...@google.com
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
We are not able to reproduce the issue please provide a sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
We would need bug reports from the phone side AND watch, please share the same.
Steps to capture bugreport:
===========================
Android Wear devices connected to Android devices
- On you Android phone, following the instructions in this doc, under the section ‘Instructions on your companion phone or tablets (Android)’
- Launch the ‘Android Wear’ app on your phone or tablet. Tap on the three vertical ellipsis on the top right hand corner of the screen and click on “Report Wearable Bug” to capture a bug report from the watch
- On the watch, you will observe a notification card with the text “Bug report #X is being generated”. It can take up to 20 minutes for the bug report to be generated and transferred to your phone.
- Once the bug report is done, the notification card on the watch changes to “Bug report #X captured” and you will receive a notification on the phone that reads “Wearable bug report finished. Tap to send." Tap on this notification and email the bug report to a pre populated email address
Instructions on your companion phone or tablets (Android)
- On your Android device, go to Settings > About phone or About tablet.
- At the bottom of the screen, touch 'Build number' seven times in quick succession. You’ll see a message saying you’re now in developer mode.
- Press Back to go back to the main Settings screen.
- Touch Developer options.
- At the top of the screen, make sure 'Developer options' is set to ON.
- Check the box next to USB debugging.
- Check the box next to Bug report shortcut.
- Reproduce the issue or error message on your phone or tablet. It’s important that your device logs at least one occurrence of the problem.
- Immediately after seeing the issue, press and hold the power button until the power menu appears.
- Select Take bug report, then select Report in the dialog that follows.
- After a significant delay -- up to two minutes -- your phone or tablet will vibrate and display a notification saying ‘Bug report captured’. Touch the notification to open Gmail with the report attached.
- After replying to this message, you can disable developer mode and bug reports by going to Settings > Developer Options and sliding the top toggle to OFF.
su...@google.com
We're closing this issue due to not having enough actionable information. If you continue to have this issue, please open a new issue and add the relevant information along with a reference link to the earlier issue.
bi...@gmail.com
Its a bit frustrating having to re-open again soon when I can find the time
to make you a demo.
Bill
On Thu, 22 Dec 2022, 06:24 , <buganizer-system@google.com> wrote:
Description
When tapped, the complications show some extra information using a Toast.
This works fine on the API28 Wear OS emulator.
I now want to upgrade the Wear OS App from API28 to API30.
On the API30 Wear OS Emulator, despite using
Context myContext= getApplicationContext();
if (NotificationManagerCompat.from(myContext).areNotificationsEnabled()) {
Toast t = Toast.makeText(myContext, "My message", Toast.LENGTH_LONG);
t.show();
}
I get "Blocking custom toast from package com.wristmap.free due to package not in the foreground"
The toast is not shown, despite adhering to the documentation and creating a Text not custom toast and checking for notifications being enabled.
Can someone please explain if I have misunderstood the Toast docs or there is a bug in the emulator's API30 code.
I don't believe I should have to buy a physical API30 WearOS device to test with to meet new PlayStore version restrictions.