Chrome Desktop with Dev iOS View - TypeError: Cannot read property 'pushNotification' of undefined

[watzak]

Description:

There is an js error when u are visiting following url = https://www.watson.ch/wirtschaft/schweiz/930659620-moebel-pfister-von-xxxlutz-gekauft-schweizer-tradition-geht-nach-oesterreich
in mobile view

TypeError: Cannot read property 'pushNotification' of undefined
at Function.getSafariNotificationPermission (PermissionManager.js:83)
at Je. (PermissionManager.js:69)
at Generator.next ()
at SubscriptionError.js:3
at new Promise ()
at Ye (SubscriptionError.js:3)
at Je.getReportedNotificationPermission (PermissionManager.js:67)
at Je. (PermissionManager.js:39)
at Generator.next ()
at SubscriptionError.js:3

Steps to Reproduce Issue:

1. https://www.watson.ch/wirtschaft/schweiz/930659620-moebel-pfister-von-xxxlutz-gekauft-schweizer-tradition-geht-nach-oesterreich
2. on mobile or with user-agent mobile on chrome developers mode
3. check console output and u will find a js error
   

Anything else:

Thanx for your help in advance ;)

[jkasten2]

@watzak Thanks for reporting.

Issue Impact - Developer Environment

Only happens when selecting an iOS device (iPhone or iPad) in the Chrome Developer tools.
Confirmed on a real iOS device in either the Chrome or Safari browser this error does not occur.

Issue - Details

Selecting an iOS device (iPhone or iPad) in the Chrome tools ends up mocking the navigator.userAgent string to an iOS device, however it does not mock window.safari so this error occurs in that testing environment.

Workaround

This is an error we will be fixing, in the meantime you can use "responsive" or an Android device in the drop down to simulate a non-iOS device to keep it from causing any issues in your mobile testing from a desktop browser.

Edit: this was fix in release 151600 on 2023/03/13

[BasileusGR]

Is the issue solved? I have the same problem.

[weroh]

Hi, I'm getting the same issue for Chrome Canary / Win10. Are there at least any workarounds for this issue?

[jkasten2]

@weroh I updated my #560 (comment) above. Let me know if that covers your question.

[ghost]

Its bug still actual.

[bfischer1121]

@jkasten2 do you think this is ever gonna be fixed?

[jkasten2]

This is now fixed in the 151600 release that went out today.