Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Using specific Chrome profile
See original GitHub issueWorking on docs for authenticated usages of LH (#1418). Want to make sure I’m not overlooking something - unclear if this is meant to work already.
Looks like our usage of chrome-launcher always makes a new user data dir, and thus a new profile, and deletes it every run. To actually use an existing profile I think we need to pass “userDataDir: false” to ChromeLauncher.launch.
Was it expected that just using chrome-flags="--profile-directory=..." would work? With existing LH, I think you’d need to spin up Chrome yourself and pass a port to LH?
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Opening because we should do what Patrick says.
dupe of https://github.com/GoogleChrome/chrome-launcher/issues/172