← Back to team overview

touch-packages team mailing list archive

[Bug 1542388] Re: click hook generated .application file has wrong desktop-entry value

 

Should probably modify the docs at
https://developer.ubuntu.com/en/start/platform/guides/online-accounts-
developer-guide/

to include the workaround to add the desktop-entry element

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-system-settings-
online-accounts in Ubuntu.
https://bugs.launchpad.net/bugs/1542388

Title:
  click hook generated .application file has wrong desktop-entry value

Status in The Savilerow project:
  Confirmed
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Won't Fix

Bug description:
  For a scope click pkg, when using the simplest .application file as
  recommended on [1] like this:

  <application>
    <services>
      <service id="com.ubuntu.developer.me.MyClick_MyApp">
        <description>Post your pictures to Facebook</description>
      </service>
    </services>
  </application>

  The installed version includes an incorrect desktop-entry field.
  Incorrect because it includes the pkg version [2], but the actual
  .desktop file name does not include it.  The result is Settings cannot
  find the .desktop file, so it cannot display the icon or the name for
  the account as defined in the .application file.

  The workaround is to add a desktop-entry xml element that contains the
  scope's fully qualified name (PKG_APP) in the source .application
  file. When present, the click hook apparently uses this when writing
  the generated version to the device [3]. Since it does not include the
  VERSION, it points to the actual installed desktop file, thus Settings
  can display the icon and name correctly as originally defined in the
  .application file.

  [1]
  https://developer.ubuntu.com/en/start/platform/guides/online-accounts-developer-guide/

  [2] incorrect generated desktop-entry example:
  <desktop-entry>dropbox.canonicalpartners_dropbox_0.3.8</desktop-entry>

  [3] correct entry using workaround:
  <desktop-entry>dropbox.canonicalpartners_dropbox</desktop-entry>

To manage notifications about this bug go to:
https://bugs.launchpad.net/savilerow/+bug/1542388/+subscriptions


References