Since I upgraded to MacBook Pro with M2 Max chip, I have been having issues with your LastPass Google Chrome extension.
Every time I want to click on the small icon, modify, it generates a bug and it goes into an infinite loop.
Here is the bug that is returned in the console:
siteDialog.js:1 Uncaught TypeError: Cannot read properties of undefined (reading '_data') at SiteDialog.open (siteDialog.js:1:8371) at dialogs.js:1:5043 at DialogLoader.d (dialogs.js:1:3108) at dialogs.js:1:3206 at Array.t (dialogs.js:1:831) at HTMLScriptElement.<anonymous> (dialogs.js:1:545)
If you could fix this, because it's really inconvenient, and I'm forced to constantly use my phone...
Also, I noticed that some passwords
Thank you LastPass team. I wish you a good day.
Thanks for notifying us. Would you mind reporting this through our support? I would like to make sure that all the information is collected before a dev team can pick this up.
Please go to https://support.lastpass.com/ in order to get in touch with our support colleagues.
Hello, this bug still persists even after a complete reinstallation of my macOS on a new session! Could someone please take care of this issue, thank you.
The error message Cannot read properties of undefined (reading '_data') usually means that you're trying to access the _data property on an object which does not exist at the moment your script is trying to read it. The object could be undefined or null because it is not properly initialized, or the object's creation might be asynchronous, and it's not ready by the time you're trying to access it.
In your case, it appears that either e.vaultItem or e.vaultItem._sharedGroup could be undefined at the point of execution.
You could prevent the error by checking if the objects are defined before trying to access their _data properties.
In many other places in the code, you check before using the correct shared group:
this._sharedGroup ? this._sharedGroup : null
this._sharedGroup = e ? e.getSharedGroup() : null
This problem still exists, even after completely removing the extension, and then completely uninstalling Chrome, the problem seems to be indeed in the extension. Will you ever fix this issue, which is just irritating and makes your tool unusable?