XPC alerts not working in Chrome Canary |
||
Issue description58.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.
,
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
,
Feb 28 2017
,
Feb 28 2017
,
Mar 2 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/49e0de872b7361e0e9514da93f7f1358de344b0c commit 49e0de872b7361e0e9514da93f7f1358de344b0c Author: miguelg <miguelg@chromium.org> Date: Thu Mar 02 09:49:09 2017 Rename the XPC identifier use the framework bundle This allows the XPC service to be named the same for all channels BUG= 696493 TBR=mark@chromium.org Review-Url: https://codereview.chromium.org/2727003002 Cr-Commit-Position: refs/heads/master@{#454221} [modify] https://crrev.com/49e0de872b7361e0e9514da93f7f1358de344b0c/chrome/browser/notifications/notification_platform_bridge_mac.mm [modify] https://crrev.com/49e0de872b7361e0e9514da93f7f1358de344b0c/chrome/browser/ui/cocoa/notifications/xpc-Info.plist [modify] https://crrev.com/49e0de872b7361e0e9514da93f7f1358de344b0c/chrome/installer/mac/sign_versioned_dir.sh.in
,
Mar 7 2017
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]
,
Mar 7 2017
Re: #6: can you split that out into a new bug? Thanks. It looks like we also need to set this up with Crashpad.
,
Mar 7 2017
Filed Isse 698911
,
Mar 7 2017
Ugh * Issue 698911 -> http://crbug.com/698911 |
||
►
Sign in to add a comment |
||
Comment 1 by miguelg@chromium.org
, Feb 27 2017