A successful logcat - https://storage.cloud.google.com/chromeos-autotest-results/79324255-chromeos-test/chromeos4-row6-rack9-host1/cheets_NotificationTest/sysinfo/var/log_diff/logcat?_ga=1.100222686.1749862190.1403573766

10-04 20:24:03.165   284   284 D ArcNotificationsService: onNotificationPosted(0|org.chromium.arc.testapp.notification|12345|null|10041)
===

and failed one shows the notification was filtered out - https://storage.cloud.google.com/chromeos-autotest-results/79372987-chromeos-test/chromeos4-row6-rack9-host14/cheets_NotificationTest/sysinfo/var/log_diff/logcat?_ga=1.37414368.1749862190.1403573766


10-05 00:50:48.360   307   307 D ArcNotificationsService: Notification is filtered (0|org.chromium.arc.testapp.notification|12345|null|10041)
10-05 00:50:48.361    24   339 D audio_hw_primary: out_set_parameters: kvpairs routing=2
10-05 00:50:48.391    24   339 D audio_hw_primary: out_add_stream: output stream created.
10-05 00:50:48.490   307   361 D NotificationSQLiteLog: Pruned event entries: 0

Hi Xiyuan,

It seems the problem is in ArcNotificationsService.showNotificationEvenIfUnprovisioned() returning false in this case.
Feel free to assign to the right arcnotificationservice owner if you are not.

showNotificationEvenIfUnprovisioned() returning false is expected since the package name for the test apk is "org.chromium.arc.testapp.notification".

The problem seems to be |mDeviceProvisioned| flag is false. Looks like there is a racing of when |mDeviceProvisioned| flag is set via ContentObserver of settings and the test starts to create notifications. I don't know why this has regressed tho.