The management UI interface cannot be opened in the new version of Chrome.

[skyaxu]

Description

Chrome version ---144.0.7515.0 and Version 144.0.7512.4 (Official Build) dev (64-bit) , When the UI management interface is opened, it always stays in the loading state and cannot be successfully opened.

Steps to Reproduce

Chrome version ---144.0.7515.0 and Version 144.0.7512.4 (Official Build) dev (64-bit) , When the UI management interface is opened, it always stays in the loading state and cannot be successfully opened.

Which browsers did you test this on?

Chrome

Affected browser versions

No response

Affected SmartProxy versions

No response

Screenshots of the problems or steps to reproduce

Chrome version ---144.0.7515.0 and Version 144.0.7512.4 (Official Build) dev (64-bit) , When the UI management interface is opened, it always stays in the loading state and cannot be successfully opened.

Any additional context

Chrome version ---144.0.7515.0 and Version 144.0.7512.4 (Official Build) dev (64-bit) , When the UI management interface is opened, it always stays in the loading state and cannot be successfully opened.

[salarcode]

I only support the main stable channel and that is on version 142.0.7444.135. Reports of broken functionally on non-stable channels is not new. I'll check again once 144 is released

[yfdyh000]

The issue has been reproduced in Edge 144.0.3719.11 (正式版本) beta (64 位) and caused the entire extension to break (popup, settings UI, and the functionality of the extension).

SmartProxy 1.8

Uncaught TypeError: s.api.runtime.getBrowserInfo is not a function
    at i.runtimeGetBrowserInfo (settingsPage.js:2:100089)
    at ./src/lib/PolyFill.ts (settingsPage.js:2:102036)
    at r (settingsPage.js:2:306893)
    at ./src/core/Settings.ts (settingsPage.js:2:34384)
    at r (settingsPage.js:2:306893)
    at ./src/core/definitions.ts (settingsPage.js:2:73329)
    at r (settingsPage.js:2:306893)
    at ./src/ui/code/CommonUi.ts (settingsPage.js:2:129994)
    at r (settingsPage.js:2:306893)
    at settingsPage.js:2:307318

s.environment.chrome is false now, since the browser is now available in Chromium. https://groups.google.com/a/chromium.org/g/chromium-extensions/c/4txWvDW55hU "Launching the browser namespace by default, as an optional alternative to chrome"

https://github.com/salarcode/SmartProxy/blob/75f3565f6a234d909499255e8b0d533b55c552f5/src/lib/environment.ts#L64