PWAs launch with blank window - need to launch it a second time

[freijon]

Description

I'm having issues launching the PWAs. Whether I launch them from the Extension or from the pinned app in the task bar (Windows), the behavior is the same:

• The first time a blank (white) window appears. The page doesn't load. I see it in the tab list but I can't click on the tab to load it.
• When I launch the app a second time shortly after, the second PWA window loads fine. I can then close the first (white) window.
• I've installed two PWAs so far (Outlook, Deezer), and both behave exactly the same way

Additional Information

• I'm using the Zen Browser (Firefox derivative). I installed it like described in your documentation with a symlink, works like a charm otherwise.
• I'm using firefoxpwa.openOutOfScopeInDefaultBrowser = true with some allowed sites, but that shouldn't be the root cause?

Environment

• Operating system: Windows 11 (22631) Enterprise
• System architecture: x86_64
• Installation method: scoop
• PWAsForFirefox extension version: 2.13.3
• PWAsForFirefox native version: firefoxpwa 2.13.3
• PWAsForFirefox runtime version: firefoxpwa-runtime 2.13.3
• Firefox version: Zen Browser 1.7.4b (Firefox 134.0.2) (64-bit)

[filips123]

Can you please check if it also happens with a normal Firefox runtime and both with and without firefoxpwa.openOutOfScopeInDefaultBrowser enabled?

[freijon]

I switched to the normal approach with the default runtime. Now, everything works fine. Upgrading the runtime with the non-default runtime was quite a hassle, I guess I'll just stick with the modified Firefox for now.

[freijon]

I've been using the default runtime for two days now and I still have strange issues...
Each morning when I start everything and launch the PWA's, a Firefox window opens with the new-tab window, not with the site that is defined in the app. Also, with a separate Firefox icon in the taskbar instead of the pinned app icon.
When I check the settings, the custom PWA settings are not present. Patching the runtime doesn't help.
Only uninstalling the runtime, and re-installing it solves the issue for the rest of the day. It's like the patched runtime somehow gets 'overwritten' by default Firefox somehow on a daily basis?

[filips123]

Please check runtime and native logs, if these files are in the runtime directory, and there in the profile directory.

[freijon]

The files are there in both the runtime directory and the profile directory.
Here is the log: firefoxpwa.log

[filips123]

When a new tab window is opened instead of the PWA, please also get the runtime logs.

[freijon]

Here you go:

1741590508887	addons.xpi	WARN	Checking C:\Users\<username>\AppData\Roaming\FirefoxPWA\runtime\distribution\extensions for addons
Warning: unrecognized command line flag -class BrowserContentHandler.sys.mjs:1567:17
Warning: unrecognized command line flag -name BrowserContentHandler.sys.mjs:1567:17
Warning: unrecognized command line flag -pwa BrowserContentHandler.sys.mjs:1567:17

[filips123]

Which distribution version is specified in %APPDATA%\FirefoxPWA\profiles\00000000000000000000000000\chrome\pwa\chrome.sys.mjs on line 21? Also, does installing a web app into a new profile fix the issue?

Also, in the native logs, there are some errors related to permissions of the runtime directory...

[filips123]

Do you still have this issue?

[freijon]

Yes. But apparently I am the only one and I have found an okay-ish workaround. It may be related to some security policy on my enterprise laptop. I think you can close the issue until someone else has it.