I'm testing the performance of my website with Lighthouse DevTool but I can't score 100% in Best Practices because keeps showing this as a problem:
Does anybody know what this means? How could I solve it?
You can find the specific errors in the "Issues" tab where the "Console" output is.
Also getting this, so you're not alone. Wondering if it was a recent Chrome bug I tried here - https://www.webpagetest.org/ and got the same useless error.
After a bit more digging, I found this closed issue on the lighthouse github repo.
https://github.com/GoogleChrome/lighthouse/issues/14233
So, it's been fixed, but only in version 10. Chrome 105 seems to be using lighthouse 9.6.2 and npm at the present time seems to install 9.6.7 (which has the same bug).
You can run the latest version by pulling the repo from github, building and running on the command line. See instructions here
https://github.com/GoogleChrome/lighthouse#develop
Note, the build doesn't work on an M1 mac, due to i386 specific build tools. I had to dig out my old macbook to get this working.
Related
when I try installing build tools using sdkmanager on window using this command below
C:\all-things-flutter\flutter-installation\android\cmdline-tools\bin>sdkmanager.bat "build-tools;30.0.0" --sdk_root=../
I keep getting this error
Warning: IO exception while downloading manifest
please this is not a duplicate question, cus I didn't find the answer I needed.
this has been bugging me for days so how can I get it right
So since I could not get an answer after 8 months, I have decided to share how I did it and other kinds of solutions people have suggested but not from here.
How i did it
I downloaded android studio (even tho i was not going to use it), then i use android studio to download the recommended SDK i will need, after that i added the SDK folder path to my system variable, that way i can continue the flutter installation and run flutter doctor, which did ditect my SDK path.
Other people Suggesttion
From my research online, I saw people saying that you need a much slower internet connection because if your internet connection is faster, it will skip some downloads, which can cause the SDK to not work well.
but my response to that is "yer good luck with that".
I've been developing blazor wasm apps in vscode for the past few months without incident. All of a sudden, I can't debug via F5 any longer. I'm literally starting with a brand new app (dotnet new blazorwasm) and when I hit F5 I get the following error:
I've uninstalled/reinstalled vscode, chrome, updated .net core 5, tried Edge put things into my launch and launchsettings.json that have helped others and plenty of other things things that I can't recall. Even created a new account on my computer to eliminate possible plugins or settings, same problem.
One thing that does work is that I can debug the old way where I would run Chrome from the command line: open /Applications/Google\ Chrome.app --args --remote-debugging-port=9222
Then you can hit Cmd+Shift+D in Chrome to start debugging within Chrome. This is a stop gap, but I'd really like to figure out how/why this just stopped working.
I created repo that reproduces it on my machine.
I'm not finding a lot of ways to gather diagnostic details that might help me determine the cause, so would appreciate any tips that would help me solve this.
Using latest chrome and vscode, even tried the insider build. No luck. I'm not sure what I did or how to fix it. Any help is greatly appreciated!
This is todo with omnisharp update. I get the same. You can downgrade omnisharp as a test and it will work again. I am investigating.
I made a stackoveflow account just to post about this since it's been bothering me for 3 days time (tinkering after work so not much time every day). And this is my first post so please be forgiving if I break a few rules :)
My problem is that after I have installed and configured everything and I have followed the official guide I get these errors thrown by VS
I have researched as much as I can and still nothing. Things I have tried:
Reinstalling VS
Reinsatlling and manually installing the Windows 10 SDK
Adding all the sdk folders to the Path Env. Variable
Rebuilding the project
Building a new project
Changing the version of the UWP
Has anyone else had this issue or know a way to fix it? I really want to start developing for MR after doing a ~10 page documentation on why its the most promising technology...
I hit a problem very early on in the official tutorial for using Flutter. Specifically, when I run Flutter Doctor I get this error message:
X Downloaded executables cannot execute on the host.
See https://github.com/flutter/flutter/issues/6207 for more information
When I follow that link there is nothing there that looks relevant. (It is mostly about LINUX problems)
Can anyone advise me on what I should do?
I have come across a really strange issue that has kept me busy for over a week which i believe to be a bug with the GoogleAdMob SDK, Xcode 8.2, cocoapods or a combination of those.
I am posting it here, in hopes an engineer can confirm the bug and point our team in the right direction to resolution.
The problem goes like this:
Create an empty Xcode project
Add/Install GoogleAds-IMA-iOS-SDK-For-AdMob pod
Commit everything and delete the repository from local machine
Check out repository again
Hit Build. Project will fail to build with error ld: framework not found GoogleMobileAds
To fix, comment out the GoogleAds-IMA-iOS-SDK-For-AdMob pod and run pod update, then uncomment it again and run pod update again, project will build.
If you try to commit at this point, git will pick up no changes
Repeat steps 3 and 4, and you will be back at step 5
I have created a repository here https://github.com/piterwilson/testAdmob where the bug can be reproduced.
The 'fix' that i have found will not work for our team as we commit our code and send it to a Jenkins server that creates a lot of builds with different code signatures required by our business.
The Jenkins build always fails with ld: framework not found GoogleMobileAds
Extra information : This has only happened starting this year. Maybe because of Xcode 8.2 (?) but we can't be sure where the problem is exactly.
I created a PR that resolves the issue in a reliable manner: https://github.com/piterwilson/testAdmob/pull/1
The repository was missing the GoogleAdMobs binary. It's a rather large file (38M), so perhaps the submitter of the question has some local configuration that automatically ignores large files? The binary should have been in this commit: https://github.com/piterwilson/testAdmob/commit/a0834a4d2f2b82da98add1bc3c49d8c0c28ffd86 (at least that's when it appeared for me when I tried to reproduce the issue.)