StateSaver should not restore when app launched from content-hub
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| content-hub (Ubuntu) |
In Progress
|
High
|
Unassigned | ||
| ubuntu-ui-toolkit (Ubuntu) |
Incomplete
|
High
|
Zsombor Egri | ||
Bug Description
Testing the messaging-app state saving ability that we've been adding from this MR:
https:/
deb can be found here:
http://
The problem is, when the app is launched from the content-hub, the StateSaver still tries to restore it's previously saved state, but it should not and this causes problems. It should clear the state, the same way it does when launched via url-dispatcher. According to Ken, there are content-hub signals that StateSaver will need to listen to in order to know when the app is being launched by content-hub.
To reproucde:
1) install the messaging-app deb from above
2) open messaging-app, swipe from bottom to create a new message
3) type some names in the recipient field, and type some message in the send field
4) do "kill -2 <pidOfMessaging
5) open camera-app and go to the photo roll
6) press "Share" from toolbar and select messaging-app from the list
Expected results:
- messaging-app should be displayed with a new page showing the photo as an attachment, and nothing else
Actual results:
- messaging-app shows the restored state from when it was last run (the values entered in Step 3 above)
Related branches
- Ubuntu SDK team: Pending requested
-
Diff: 433 lines (+175/-42)8 files modifiedmodules/Ubuntu/Components/plugin/statesaverbackend_p.cpp (+41/-22)
modules/Ubuntu/Components/plugin/statesaverbackend_p.h (+6/-6)
modules/Ubuntu/Components/plugin/ucstatesaver.cpp (+8/-9)
modules/Ubuntu/Components/plugin/ucurihandler.cpp (+38/-2)
modules/Ubuntu/Components/plugin/ucurihandler.h (+6/-1)
tests/unit_x11/tst_statesaver/UriHandlerApp.qml (+41/-0)
tests/unit_x11/tst_statesaver/tst_statesaver.cpp (+33/-1)
tests/unit_x11/tst_statesaver/tst_statesaver.pro (+2/-1)
| Changed in ubuntu-ui-toolkit (Ubuntu): | |
| importance: | Undecided → High |
| Changed in ubuntu-ui-toolkit (Ubuntu): | |
| assignee: | nobody → Zsombor Egri (zsombi) |
| Zsombor Egri (zsombi) wrote | #1 |
| Changed in ubuntu-ui-toolkit (Ubuntu): | |
| status: | New → Incomplete |
| Bill Filler (bfiller) wrote | #2 |
| Changed in ubuntu-ui-toolkit (Ubuntu): | |
| status: | Incomplete → Confirmed |
| Ken VanDine (ken-vandine) wrote | #3 |
| Changed in ubuntu-ui-toolkit (Ubuntu): | |
| status: | Confirmed → In Progress |
| Changed in content-hub (Ubuntu): | |
| assignee: | nobody → Ken VanDine (ken-vandine) |
| status: | New → In Progress |
| importance: | Undecided → High |
| Zsombor Egri (zsombi) wrote | #4 |
| Cris Dywan (kalikiana) wrote | #5 |
| Changed in ubuntu-ui-toolkit (Ubuntu): | |
| status: | In Progress → Incomplete |
| Changed in content-hub (Ubuntu): | |
| assignee: | Ken VanDine (ken-vandine) → nobody |
I need more details on this: was this also happening on RTM (Qt 5.3.x)? Or only on Vivid (Qt 5.4)? Had there be any changes in the way ContentHub invokes Application (i.e. not thru UriHandler, the URI is passed over the application later than it si launched, etc).