Obsolete
Status Update
Comments
en...@google.com <en...@google.com>
ro...@gmail.com <ro...@gmail.com> #2
This is a critical bug for our App. We have a medical (EMR) application that relies on toasts to convey important workflow feedback to the user. The information is not actionable, which is why we chose to use toasts instead of alerts. Please consider this a plea for some kind of feedback on the issue - even if it's just to let us know that it won't be fixed anytime soon. That way, we can get started on a workaround if necessary. Although, obviously, we'd like to see it just fixed :)
sk...@gmail.com <sk...@gmail.com> #3
I have the same issue with my app. Is there any update? How about a way to programatically set the Application setting "Show notification"?
na...@gmail.com <na...@gmail.com> #4
Same issue with my app too. From what i have gathered there's no way to enable the notifications programatically.
le...@googlemail.com <le...@googlemail.com> #5
This is appalling. If intentional, it should minimally be made clear to the user that they are also disabling toasts!
Pent
Pent
ia...@justeattakeaway.com <ia...@justeattakeaway.com> #6
The worst part is the UI design of the application settings sticks the 'Enable Notifications' option right beneath the 'Force stop' button.
It took ages to figure out why toasts were not showing when a QA engineer accidentally disabled notifications when force closing the app.
It took ages to figure out why toasts were not showing when a QA engineer accidentally disabled notifications when force closing the app.
de...@gmail.com <de...@gmail.com> #7
Ok, this is the death of Toast messages. Not going to support it anymore.
al...@gmail.com <al...@gmail.com> #8
This appears to be intentional according to the comments in frameworks/base/services/java/com/android/server/NotificationManagerService.java (i.e. stuff like "Suppressing toast for package by user request"). The framework checks whether or not the user has enabled notifications by calling the areNotificationsEnabledForPackage() method and only enqueues the toast if the user has checked the notifications enabled check box in the system settings.
Link:https://android.googlesource.com/platform/frameworks/base/+/refs/heads/master/services/java/com/android/server/NotificationManagerService.java
Link:
be...@gmail.com <be...@gmail.com> #9
Is the assumption that an app would only want to launch Toasts when it is not the active app? I could understand this behavior then, but then I would want an alternate for when a user IS using my app and I want to display a short message that goes away after a second that would work even if notifications are disallowed for my app.
de...@gmail.com <de...@gmail.com> #10
Really Its a bug of android why they also disabled the Toast message as well.. aur app work flow get effected with this.
ge...@gmail.com <ge...@gmail.com> #11
Same Issue , I dont want toast to display user but I am using it as primary debugging solution and not null check on intent pass also.
please give programatic way to enable toast if notficatios disabled
please give programatic way to enable toast if notficatios disabled
ar...@gmail.com <ar...@gmail.com> #12
Same Issue
na...@gmail.com <na...@gmail.com> #13
Thank you for this issue
I am a beginner and i had spent much time to find it
it's very blocked bug
I am a beginner and i had spent much time to find it
it's very blocked bug
ba...@gmail.com <ba...@gmail.com> #14
It looks like this is not just Jellybean. If I Block all notifications on Marshmallow I also don't see the toasts when the app is in the foreground. This is crazy!!!!
ra...@gmail.com <ra...@gmail.com> #15
i'm so crazy about this too
ub...@gmail.com <ub...@gmail.com> #16
Any updates from the official side about this?
ou...@gmail.com <ou...@gmail.com> #18
CANONDi think we can use this custom toast as alternative solution for this problem.
https://github.com/kamikat/toast-compat
an...@gmail.com <an...@gmail.com> #19
Hey!
Is it possible to have an update about this issue? It's still exist in API 26/27, please give any news at least....
Is it possible to have an update about this issue? It's still exist in API 26/27, please give any news at least....
ro...@gmail.com <ro...@gmail.com> #20
I am facing this issue in android 8.1.0 device name Nokia 2.1 please suggest its urgent.
sa...@google.com <sa...@google.com> #21
Thank you for your feedback. We have tried our best to address the issue reported, however our product team has shifted work priority which doesn't include this issue. For now, we will be closing the issue as "Won't Fix (Obsolete)". If this issue still currently exists, we request that you log a new issue along with the latest bug report here: https://goo.gl/TbMiIO and reference this bug for context.
to...@steadfastinnovation.com <to...@steadfastinnovation.com> #22
Tested this issue on a Pixel 4XL Android 11 Beta 3.5
With notifications for the app turned OFF:
- Toasts still appear in the app
- Toasts DO NOT appear if the app is in the background
With notifications for the app turned ON:
- Toasts still appear in the app
- Toasts still appear if the app is in the background
Overall, I think this issue is fixed and should be marked as such. The only problem is that this behavior is not documented anywhere that I can find. The
sh...@gmail.com <sh...@gmail.com> #23
Restart the device or change notification permission to your app, this is now working in my case.
ma...@gmail.com <ma...@gmail.com> #24
ma...@gmail.com <ma...@gmail.com> #25
Sounds like a good idea to me. If users don't want to see your toasts because they are annoying, then they have every right to hide them. If you are a developer, you would know that your job is to serve the users' needs. Its not our job to make sure that you are getting "feedback" if we decide to block your annoying notification spam.
Description
A very bad and unwanted side effect is that once notifs are disabled, Toast messages are also disabled, even when the user is running the app!
You encourage to use Toast in your design guidelines, but who will want to use it if the users have the possibility to remove them, especially if the toasted message is an important feedback to display to the user...
I understand at least that Toasts could be disabled when the app is in background, but not if it is the foreground Activity.