I've now tried these steps, but issue persist... I've also tried In MS Edge where latest LP Extension is only 4.128 and there things work... I've the force edge to use the Chome Webstore version (Edge can do that) and then it also break in Chrome so there is something wrong with the version that released yesterday.
I'm a web-developer so I can tell you that websites that have had issues was create with Blazor server and Vue JS frameworks... I've also tested on Blazor Web Assembly and there there are no issues. The issue have also been noticed by a Microsoft Developer team for Blazor in this thread: https://github.com/dotnet/aspnetcore/issues/55085 (has reproduce steps if needed) + a bunch of my colleages so not a my machine only specific issue...
I can deploy a sample website that have the issue + the source code if need be
Hope you can fix this soon, or at least delay new version a bit to other extension store so other browsers can be used as workaound for now.
Hello @mail,
We appreciate your post.
At the moment, we do not have a report indicating this version of the extension is causing an issue of this sort.
As you have disabled the extension and the site works as needed, please, proceed with the following steps:
If the issue persists, update theLastPass browser extension(view downloads here), then log in to LastPass and try to perform the action again.
Thank you,
Karol | Customer Care
I've create this sample Website that reproduce the issue so it is easier for you to debug: https://lastpassbroken.azurewebsites.net/
To reproduce:
Create a new Blazor app: dotnet new blazor -int Server -ai -o TestServer
Run the app: dotnet run -lp https
Navigate to the app with Chrome browser with LastPass version 4.129.0 installed. The app creates errors. Disabling LastPass and the app does not create errors.
Using FireFox with LastPass 4.127.0 does not create problems.
Same for me, we experience loading Failures on PRTG Monitoring Sites (Hosted and OnPremis). The Site aborts loading and showing just a loading Screen forever.
I had to go back to Version 4.128, no issues.
Accounting Package: Viewpoint Spectrum - Document Imaging Window Issues
Lastpass, this is a shocker!
I've spent the whole day diagnosing my code. I wished that I had found this report earlier.
Can reproduce the error by following the steps documented by others above.
We have been LastPass customers for many years, am now re-considering that situation.
I have a blazor website, when i enable the lastpass extension i get this error:
blazor.web.js?v=2404.8.0.4:1 crit: Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100]
Unhandled exception rendering component: TypeError: Cannot read properties of null (reading 'insertBefore')
TypeError: Cannot read properties of null (reading 'insertBefore')
Unhandled exception rendering component: Error: No element is currently associated with component 1
Error: No element is currently associated with component 1
If i disable the lastpass extension i don't get any errors.
@Karol Hidalgo
Even though I'm a LastPass user and now know how to avoid the issue (by disabling LastPass), we are also running a website using Blazor and now getting large amount of issues reported by users stating 'your website doesnt work'.
The amount of work we need to do to tell customers to disable LastPass and the business we are losing is huge!
Could LastPass respond what LastPass is going to do about this? Your bug is costing us a lot of money!
Same issue here - Blazor .NET 8 and LastPass MSEdge extension v. 4.129.0
Bump
@Karol Hidalgo: Any news on this issue? As you can see in the thread, multiple people across multiple sites are affected, and now MS Edge Users are also affected as the broken Extension version was pushed to the MS Extension store... as for workarounds there seems to be none (Your Never URL system does not seem to work for this issue :-()
The first priority of an extension must be to never break the underlying sites it operates on...
I messaged with support and they gave me the usual "everything is fine, uninstall, clear everything and reinstall"-speech.
I cannot do that on the machine that has the issue - have anyone tried a procedure like that?
This is the steps:
+accept/decline any pending shares you may have (sharing center, shared with me)
+log out of the LastPass extension
+remove the LastPass extension
+clear your cache and cookies from your browser for the last 7 days
+add the LastPass extension
+log in and test it out
My patience with his "product" is growing thin...
@Ash Cannon: The Sites Server-logs should that be of interest as well:
2024-04-17 15:55:44.394 +00:00 [Warning] Microsoft.AspNetCore.Components.Server.Circuits.RemoteRenderer: Unhandled exception rendering component: TypeError: Cannot read properties of null (reading 'insertBefore')System.InvalidOperationException: TypeError: Cannot read properties of null (reading 'insertBefore')at Microsoft.AspNetCore.Components.RenderTree.Renderer.InvokeRenderCompletedCallsAfterUpdateDisplayTask(Task updateDisplayTask, Int32[] updatedComponents)
2024-04-17 15:55:44.398 +00:00 [Error] Microsoft.AspNetCore.Components.Server.Circuits.CircuitHost: Unhandled exception in circuit 'qvS7jPR_1t00_HqPN1SGJH4DDagOQm1igUV1K7KLYRI'.System.AggregateException: One or more errors occurred. (TypeError: Cannot read properties of null (reading 'insertBefore'))---> System.InvalidOperationException: TypeError: Cannot read properties of null (reading 'insertBefore')at Microsoft.AspNetCore.Components.RenderTree.Renderer.InvokeRenderCompletedCallsAfterUpdateDisplayTask(Task updateDisplayTask, Int32[] updatedComponents)--- End of inner exception stack trace ---
@mailLastPass should give you a free subscription
Finally, I've also made a video demonstrating the error here: https://1drv.ms/v/s!AkItAZiaMtwzj9UIDLIi_q9S6PhQSw?e=hCf2we
Imagine waking up and a bunch of people are opening tickets complaining my application "stopped working" while nothing new had been released, and it's working fine for everyone else. Just to figure out hours later testing in a user's machine it's an extension being excessively intrusive. No official statement or fix yet? it's been almost a week. This is unacceptable.
I have two blazor applications running in .NET 8. Both in the new - previously called - United architecture. Both can be switched between ServerSide and WebAssembly.
The one used internally completely broke. Throwing the same error Cannot read properties of null (reading 'insertBefore') mentioned by another user at startup. In both render modes.
The user-facing one is unaffected in both render modes (thank all that is holy, that would've been ugly). Both very similar in terms of using a lot of the same technologies, versions and basic DOM structure. I have no idea what's the difference between them that allows this one to run regardless. I tried diffing the DOM but reached no conclusions in the time until being completely pissed off and just telling the users to uninstall the extension.
Dear @Ash Cannon
Instead of letting us do the work... We (the people who have responded in this thread) have given you exact instructions how to reproduce this problem. Someone even made an example website which showcases the problem. I will repeat the URL for you: https://lastpassbroken.azurewebsites.net/
I've just tested it, it still shows the problem. Open this website with Chrome and LastPass extention version 4.129.0 and then YOU can gather network + console logs.
What you are asking is to let someone else do the work, while you have all the tools/means to do the research yourself. First of all: we are PAYING customers, not employees who are being paid by LastPass. Second: By asking this it looks like you are trying to delay or to make it not your problem. This IS Lastpass's problem!
Please rollback version 4.129.0 immediately, you are costing us (everyone (!!) with this type of interactive websites) a lot of money in missed visitors = revenue. This is taking WAY TOO LONG!
If you have any questions, you have my email address.
Kind regards,
Martin
@martin:-) ... I will settle for a new version that resolves the issue ... But please keep the replies civil in here... Yes this sucks, but just being angry never solved anything....
Hi @Ash Cannon... Here you go, but I also urge you to just go (pass on) to the sample website that reproduce the error: https://lastpassbroken.azurewebsites.net/ ... Here you can 100% reproduce the error and the site even refrence to the sample code that generated the sample website (aka you can gather same logs as attached from that website should you need more info)
Hi, all.
In order to investigate this issue further, it would help if you could gather network + console logs from your local device by following these instructions: https://support.lastpass.com/s/document-item?bundleId=lastpass&topicId=LastPass/console_network_logs_edge.html&_LANG=enus
Thank you.
I am angry, and frustrated. It took @Ash Cannon6(!!!) days to respond. Which would have been fine if the message was: "good news, we fixed the problem". But no, after 6 days the message is "could you send a log?" while all was available to analyze the problem.
I'm loosing quite some money over this. So, I'm not sorry for appearing angry, because I am angry.
There is an extension update (4.130.0). We were running into a similar issue (AngularJS/CookieBot) and it seems to be corrected now. Hope it helps the Blazor folks having issues.
Many users affected...
E.g.
https://github.com/dotnet/aspnetcore/issues/55085
https://github.com/dotnet/aspnetcore/issues/54842
https://www.reddit.com/r/Blazor/comments/1c607rp/blazor_server_net_8_applications_broken_by_latest/
While we are waiting on an official fix, the links posted above recently actually contains workarounds that fixes the issue:
If you find your App.razor file and find the <HeadOutlet> tag, you can add an empty <meta/> tag after that to resolve the issue [turns out it only happens if the <HeadOutlet> tag is the last of all the <head> sub-tags]
Ping @martin
@Ash CannonVersion 4.130.0 did not correct the issue with Viewpoint Spectrum's Document Imaging. Turn the extension off and issue disappears. Turn extension back on and issues. Thanks
Just tested and 4.130.0 do resolve the issue (At least for Blazor Interactive Server)
@Shawn SullivanMany thanks for letting us know!!
@mailMany thanks for all the info and work you did
@Robert HakenMany thanks for supplying all the info
@Ash CannonLastPass needs to work on their communication. Primarily the lack of communication and the not showing of commitment. Of course behind the scenes LastPass was working on a fix, it shows because a fix has been released. But communicating this to users and people affected by this problem is very important. People have spend a lot of time on how to make their websites working again, frustrated by the lack of communication how long this situation will last. Involve your customers and the community, this will make you a valuable partner.
Everybody else in the community (on reddit, github and other places): many thanks!!!
@AshC_LP Version 4.130.1 still has a few bugs. I discovered a really strange problem. When I render a page created in vue.js, it displays a blank page; however, this problem is fixed when I resize the window or switch tabs.
