touch-packages team mailing list archive

[Zsombor Egri <1429899@xxxxxxxxxxxxxxxxxx>]

** Branch unlinked: lp:~zsombi/ubuntu-ui-toolkit/disable-statesaver-
from-urihandler

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to content-hub in Ubuntu.
https://bugs.launchpad.net/bugs/1429899

Title:
  StateSaver should not restore when app launched from content-hub

Status in content-hub package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Testing the messaging-app state saving ability that we've been adding from this MR:
  https://code.launchpad.net/~tiagosh/messaging-app/state-saver2/+merge/250996

  deb can be found here:
  http://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-vivid-armhf/1669/artifact/work/output/*zip*/output.zip

  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 <pidOfMessagingApp>" to kill the messaging-app and save it's state
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1429899/+subscriptions