New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 696493 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Feb 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug

Blocking:
issue 571056



Sign in to add a comment

XPC alerts not working in Chrome Canary

Project Member Reported by miguelg@chromium.org, Feb 27 2017

Issue description

58.0.3025.0 inlcudes an XPC service in charge of delivering notifications of type alert.

If you are not in the right finch trial this can be triggered by forcing the run time flag (chrome://flags/#enable-native-notifications). After that you cand a notification of type alert (for example from https://tests.peter.sh/notification-generator/#requireInteraction=true) 

Unfortunatelly you will notice that nothing gets displayed.

This works perfectly fine in chromium builds (and also locally built branded chrome builds) I have been unable to verify it on Chrome Dev (because it has not yet been updated) or in a locally built version of Chrome Canary (since I can't seem to find a way to build it).

Our suspicion right now is that because the bundle identifier is "com.google.Chrome.canary" instead of "com.google.Chrome" Chrome is unable to find the XPC service.



 
The XPC client is looking for the XPC
service in com.google.Chrome.canary.AlertNotificationService which
does not exist. Instead it should be looking into
com.google.Chrome.AlertNotificationService.
I think this is an artifact of how Chrome Canary is built and I am almost 100% sure that it will not affect Dev or any other channel.
Project Member

Comment 2 by bugdroid1@chromium.org, Feb 28 2017

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome/src-internal.git/+/ff1fe8bb6c75aa345594b67ffdfed9435a58d677

commit ff1fe8bb6c75aa345594b67ffdfed9435a58d677
Author: Miguel Garcia <miguelg@chromium.org>
Date: Tue Feb 28 09:28:08 2017

Status: Fixed (was: Assigned)
That landed in branch 3029, but since then (branch 3030, 3032) I've been getting crash reports appearing in Console.app for AlertNotificationService in Canary

Process:               AlertNotificationService [5159]
Path:                  /Applications/Google Chrome Canary.app/Contents/Versions/59.0.3030.0/Google Chrome Framework.framework/Versions/A/XPCServices/AlertNotificationService.xpc/Contents/MacOS/AlertNotificationService
Identifier:            AlertNotificationService
Version:               1.0 (1)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           Google Chrome Canary [25045]
User ID:               175663

Date/Time:             2017-03-06 16:41:21.714 +1100
OS Version:            Mac OS X 10.12.3 (16D32)
Report Version:        12
Anonymous UUID:        5313859F-D86B-7AB0-1EE5-41584053948F


Time Awake Since Boot: 1600000 seconds

System Integrity Protection: enabled

Crashed Thread:        1  Dispatch queue: com.apple.NSXPCConnection.user.25045

Exception Type:        EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes:       0x0000000000000001, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Illegal instruction: 4
Termination Reason:    Namespace SIGNAL, Code 0x4
Terminating Process:   exc handler [0]
AlertNotificationService_2017-03-06-164122_tapted-macpro2.crash
40.6 KB Download
AlertNotificationService_2017-03-07-103710_tapted-macpro2.crash
3.2 KB Download
Re: #6: can you split that out into a new bug? Thanks. It looks like we also need to set this up with Crashpad.
Filed Isse 698911

Sign in to add a comment