Uncaught Exception: TypeError: Cannot read properties of null (reading 'webContents')

[tebbsy]

Steps To Reproduce

1. Launch Bitwarden desktop application
2. The error message appears in a modal box after random amount of time, and keep reappearing

Expected Result

This message NOT to appear

Actual Result

The following error appears in a modal box that when closed keeps reappearing, and the app is unusable.
App needs to be force quit and restarted

'Uncaught Exception:
TypeError: Cannot read properties of null (reading 'webContents’)
at /Applications/Bitwarden.app/Contents/Resources/app.asar/main.js:85790:45'

Screenshots or Videos

No response

Additional Context

No response

Operating System

macOS

Operating System Version

Sonoma 14.6.1

Installation method

Direct Download (from bitwarden.com)

Build Version

Version 2024.11.1 (33298)

Issue Tracking Info

• I understand that work is tracked outside of GitHub. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

[bitwarden-bot]

Thank you for reporting this issue! We've added this to our internal tracking system.
ID: PM-15108

[cbbit]

Hi there,

I am unable to reproduce this issue, it has been escalated for further investigation. If you have more information that can help us, please add it below.

Thanks!

[tebbsy]

Hi, and thanks for your response. This is a screengrab of the error message. It tends to appear after long periods of inactivity, laptop going to sleep mode too [image: image.png] Regards, James

…

On Tue, 26 Nov 2024 at 21:22, cbbit ***@***.***> wrote: Hi there, I am unable to reproduce this issue, it has been escalated for further investigation. If you have more information that can help us, please add it below. Thanks! — Reply to this email directly, view it on GitHub <#12070 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AV35DCIALVCRLQV7QZTIAL32CTRBXAVCNFSM6AAAAABSFERWKGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBRHE2TQOJYGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[trmartin4]

@tebbsy do you have the DuckDuckGo integration enabled? If so this could be related to #12190.

[tebbsy]

Yes, I do. James

…

On Wed, 11 Dec 2024 at 02:25, Todd Martin ***@***.***> wrote: @tebbsy <https://github.com/tebbsy> do you have the DuckDuckGo integration enabled? If so this could be related to #12190 <#12190>. — Reply to this email directly, view it on GitHub <#12070 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AV35DCIOMZGBFRBEGHGCJF32E6PCHAVCNFSM6AAAAABSFERWKGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZTGQ3TSMRTGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[trmartin4]

@tebbsy can you verify if this still occurs with the 2024.12.0 release of the desktop client? We addressed some issues with the DuckDuckGo integration that could have resulted in this behavior.

[tebbsy]

Hi, looks like you’ve fixed it. It hasn’t happened again. A job well done,JamesOn 23 Dec 2024, at 18:34, Todd Martin ***@***.***> wrote: @tebbsy can you verify if this still occurs with the 2024.12.0 release of the desktop client? We addressed some issues with the DuckDuckGo integration that could have resulted in this behavior. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[trmartin4]

Closing this issue as it was addressed with better message handling for the IPC connection to DuckDuckGo in #11987.