Replies: 1 comment
-
Seeing a similar issue, we are using cognito and our login is on a different subdomain from our app. After the puppeteer script runs the lighthouse scan happens on the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey, I'm setting up the lighthouse-ci for a react app that behinds authentication ( which uses @azure/msal-react). The app redirects users to the MS login page and redirect users back to the app once authenticated.
According to the documentation, I've set up a puppeteer-script.js. However, when the lighthouse scans the app, it still gets stuck in the microsoft login page. And the lighthouse report says
The page may not be loading as expected because your test URL (http://localhost:61337/index.html) was redirected to https://login.microsoftonline.com/cde6*********. Try testing the second URL directly.
I passed the headless:false option into the puppeteer, but there's no chrome launched so hard to debug to verify if the puppeteer script works or not. Has anyone had experience with setting this up?
The below is my lighthouserc.js
Beta Was this translation helpful? Give feedback.
All reactions