Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Chrominum does not open with new version 1.24.0 #2231

Closed
jellenche opened this issue Jul 27, 2022 · 3 comments
Closed

[BUG] Chrominum does not open with new version 1.24.0 #2231

jellenche opened this issue Jul 27, 2022 · 3 comments

Comments

@jellenche
Copy link

Context:

  • Playwright Version: [1.24.0]
  • Operating System: [Windows]
  • .NET version: [ .NET 6]
  • Browser: [Chromium]

** Code snippet**
This is a part of .csproj file where we define which packages we want to use and their versions

net6.0 disable
<IsPackable>false</IsPackable>
<ItemGroup>
	<ProjectReference Include="..\AzureStorageAccess\AzureStorageAccess.csproj" />
	<ProjectReference Include="..\DBAccess\DBAccess.csproj" />
	<ProjectReference Include="..\PageObjects\PageObjects.csproj" />
	<ProjectReference Include="..\WebAppCommon\WebAppCommon.csproj" />
</ItemGroup>

<ItemGroup>
	<None Update="appsettings.json">
		<CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
	</None>
</ItemGroup>

Describe the bug

I have some test written in PW .NET6.0 , running in headed mode. While my code was using previous version of PW 1.23.0, Chromium was opening without problems. The moment I switched to a new version, Chromium is not opening (the test seems to Be running in headless mode). The mode of running is defined in system environment variable as "HEADED = 1".
I noticed the issue has something to do with the PW version because, the moment I downgraded the solution to use 1.23.0 version instead of 1.24.0, browser was opening. Is this a known issue and how to solve it if we want to switch to a new PW version?

@mxschmitt
Copy link
Member

mxschmitt commented Jul 27, 2022

This was fixed in #2227, we'll release a new version with the fix soon. Sorry for the inconvenience.

@mxschmitt
Copy link
Member

v1.24.1 gets published right now, should be fixed then.

@jellenche
Copy link
Author

It is, thanx for your effort 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants