touch-packages team mailing list archive

[Ken VanDine <ken.vandine@xxxxxxxxxxxxx>]

Is it the content-hub-service that crashes?  Or the app?  If the service
doesn't crash, the cached file should still get cleaned up with the
service exits.

The problem with APP_ID=fake is we need the APP_ID to be parse-able by
libubuntu-app-launch, plus it needs to be unique.  I wish setting
applicationName in the MainView would be enough to set the runtime
APP_ID, but it isn't.

-- 
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/1483558

Title:
  Content-Hub crash with an invalid app-id after transfer and doesn't
  clean up temp files

Status in content-hub package in Ubuntu:
  New

Bug description:
  The idea would to have at least a fake APP_ID for developping and
  testing/iterating on desktop. The import functionality itself works,
  but the crash doesn't give a good developer experience.

  Maybe we can decide on having an APP_ID=fake in the developer default
  template, and then, content-hub let that ID pass even if not
  installed?

  Note that one of the side effect of this crash after transfer is that
  the tmeporary files under HubIncoming aren't cleaned up.

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