appid:// entries in FrequentlyUsedAppsModel are not handled correctly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity-mir (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
unity8 (Ubuntu) |
Fix Released
|
High
|
Michael Zanetti |
Bug Description
In FrequentlyUsedA
Right now this works because unity-scopes-shell doesn't recognize it as an app and passes it on to the catch-all case calling QDesktopService
* The app startup animation is not shown properly. If you launch apps from the Apps scope, you'll notice that directly on tapping the (so far white) app splash screen comes up. This doesn't happen with appid:// urls.
* Tests trying to launch them will fail anywhere else than on the phone as it most likely ends up in chrome instead of spawning the application.
I think the solution is to emit activateApplication in unity-scopes-shell with only the short-appid as parameter, and add support for the short-appid in unity's ApplicationManager.
no longer affects: | unity-scopes-shell (Ubuntu) |
affects: | unity8 → unity8 (Ubuntu) |
FWIW, we should support, and improve if possible, the url-dispatcher story, too. I.e. bring the splash screen as soon as upstart tells us this app is launching.
I know there are improvements coming to url-dispatcher / upstart-app-launch that are supposed to help with the time it takes to launch apps now.