Comment 1 for bug 1570922
Revision history for this message
| Michael Terry (mterry) wrote Re: Initial notifications never shown and not destroyed until unity8 is stopped | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Are you sure that you're testing was actually observing the voice mail notification?
My *guess* is that the voice mail notification happened too early for unity8 to see it, so it just went to the void. And the notification you're seeing is actually the "placeholder" notification. Which unity-notification creates and is just an empty notification with the "placeholder" type.
"What the heck is a placeholder notification?" I hear you ask. Very good question. I'm not 100% sure. It *seems* to be a hack to move the notifications lower on the screen? But I don't know why that's not done in the UI layer instead of in the notification model... Honestly, I don't know if it has any good purpose. I didn't know about it until I looked into this bug.
So... it might be confusing your testing.
You can debug this a bit by adding more info into your onCompleted print: like "summary", "body", and "type". If type == 0, it's a placeholder (and summary and body will be empty). And you can ignore it if so.