PWA doesn't launch with Workspace
Microsoft PowerToys version
0.87.0
Installation method
PowerToys auto-update
Running as admin
No
Area(s) with issue?
Workspaces
Steps to reproduce
create a workspace with a minimum width skype window and a PWA host in Edge. Create a Desktop shortcut (and move it to Start|Programs and pin it to Start - why oh, why does Workspaces not do this? Who on Earth clutters their desktop with icon? Monsters!). Launch workspace from any shortcut or direct in Workspaces App. Skype launches, PWA does not, no Edge window appears either. PowerToysReport_2024-12-17-11-27-55.zip
✔️ Expected Behavior
PWA should launch as advertised.
❌ Actual Behavior
PWA does not launch
I have workspaces for two different PWAs, neither works as expected
Other Software
Edge Version 131.0.2903.99 (Official build) (64-bit) Skype for Desktop 8.134
We've found some similar issues:
- #34598 , similarity score: 86%
- #35251 , similarity score: 83%
- #34572 , similarity score: 82%
If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.
Note: You can give me feedback by 👍 or 👎 this comment.
Hi @mccrispy I've analysed your logs. The pwa app seems to be launched but not appearing, which is a bug somewhere. We have tested with different pwa apps, which were working. Also now I've installed the Board Game Arena pwa app under edge and it works for me. I can launch it via workspaces (from editor and via shortcat too). So as I cannot reproduce your faulty scenario, I would like to ask you for a little cooperation. A question first: you have probably installed the app long time ago? - just asking to have some idea to catch the problem.
I see, that the snapshot tool was launched in September (PT version 0.84). At that time the PWA code was not complete, so that might cause the problem. I would like to ask you to create a new snapshot with the latest 0.87 PT and try to launch it. It might actually work. If not, please send a new /bugreport and I'll give it a look again, Thanks for your cooperation.
Hi there!We need a bit more information to really debug this issue. Can you add a "Report Bug" zip file here? You right click on our system tray icon and just go to report bug. Then drag the zipfile from your desktop onto the GitHub comment box in this issue. Thanks!
Sorry about the delay in coming back - I need to fix my github notifications! My PowerTools says it's version 0.87, so I've created a new bug report. PowerToysReport_2024-12-20-10-53-44.zip
Hi @mccrispy I've analysed your logs. The pwa app seems to be launched but not appearing, which is a bug somewhere. We have tested with different pwa apps, which were working. Also now I've installed the Board Game Arena pwa app under edge and it works for me. I can launch it via workspaces (from editor and via shortcat too). So as I cannot reproduce your faulty scenario, I would like to ask you for a little cooperation. A question first: you have probably installed the app long time ago? - just asking to have some idea to catch the problem.
The PWAs were (re-)installed pretty recently, though I've been having problems removing what look like "stub" PWAs - apps that appear in the Windows "Apps" control panel (or whatever it's called now), but that won't uninstall (see screenshots). (If you have any suggestions for fixing that it would be great 😉)
Note that the yucata PWA doesn't seem to experience the problem with uninstalling, but it does have the issue with PWA launching. Note also that I have both Brave and Edge and that I have previously installed the PWAs in Brave (but believe that they are now uninstalled, but see above)
I see, that the snapshot tool was launched in September (PT version 0.84). At that time the PWA code was not complete, so that might cause the problem. I would like to ask you to create a new snapshot with the latest 0.87 PT and try to launch it. It might actually work. If not, please send a new /bugreport and I'll give it a look again, Thanks for your cooperation.
The snapshots (workspaces?) that you see in the bug report were (re-)created fresh immediately before I created the bug report. I'd previously used the command line option for the workspace to make the PWA launch successfully, so I was excited to see the new PWA support and so scrapped what I originally had done. I don't know why the bug report would say the snapshots were from an earlier version. However, I'll do what you suggest and report back.
I've recreated the workspaces and created a new bug report immediately after testing the new workspaces - which still don't launch the PWAs
I've discovered a new fact that might be pertinent. With Edge, I use a signed in profile for sync; it is the only profile configured for Edge. However, when I launch the workspace that includes a PWA, it creates a new profile "Profile 1" and that profile does not have access to the PWAs (I check via edge://apps)
@mccrispy Thanks for the feedback. We will analyse the issue, from the the edge-profile view too. I appreciate your help, thanks!
@mccrispy as you said you previously used the command line option for the workspace to make the PWA launch successfully, just a clarification, do you use any command line for the boardgamearena pwa app?
My understanding is that before 0.87 it required a CLI argument to launch the PWA, but with 0.87 Workspaces was "PWA aware" and no longer required the user to define the CLI Argument. So, up to 0.87 I used a command line, with 0.87 I stopped using one. If I do provide the CLI Argument, the PWA launches as expected. (Any CLI Argument I use is limited to that needed to launch the PWA, no other parameters are used)
@mccrispy Could you help check the pwa app's profile? You can make sure Board Game Arena's living in your desired profile when go to edge://apps, then you can check current profile by go to edge://version and check the Profile path there. To see if is 'Default'?
@mccrispy Could you help check the pwa app's profile? You can make sure Board Game Arena's living in your desired profile when go to edge://apps, then you can check current profile by go to edge://version and check the Profile path there. To see if is 'Default'?
When I'm signed in on Edge, using my "normal" profile, the following is true:
- edge://settings/profiles shows the expected account as signed in and lists an additional profile "Profile 1" as available (this profile offers a different - but expected - identity in the "choose an account" list, but it is not signed in as that account for purposes of sync)
- edge://apps lists the expected apps (including BGA) as installed apps. No apps are listed as "your available apps"
- edge://version shows the profile path as "%localappdata%\Microsoft\Edge\User Data\Profile 1"
- If I switch to Profile 1, edge://version lists the profile path as "%localappdata%\Microsoft\Edge\User Data\Default" (which seems a little odd)
- While switched to "Profile 1" (the one whose path is "Default"), no apps are listed as installed or available under edge://apps
@mccrispy Looks like you install the pwa apps in your profile(physical path is "Profile 1"), Could you configure this in workspace commandline and see if pwa launches as expected?
--profile-directory="Profile 1"
Looks like we can't get profile path from running pwa process, we have to rely on manual config for edge profile path currently. Let me know if issue persists.
Providing the profile path in the CLI works. Not surprising really, because launching "raw" Edge with the full CLI parameters for the PWA works. Thanks for figuring it out for me! I look forward to a full resolution at some time in the future.
@mccrispy I'v tried to address this in new release, we should no need to configure profile for pwa apps launch. If issue persist, could create a new issue for it, thanks
