Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Offical apps | Community apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Package development
  3. Community app update fails when only the manifest `title` changes (`id` unchanged)

Community app update fails when only the manifest `title` changes (`id` unchanged)

Scheduled Pinned Locked Moved Package development
1 Posts 1 Posters 18 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • timconsidineT
    timconsidineT
    timconsidine
    App Dev
    wrote last edited by timconsidine
    #1

    I think I've hit what looks like either an undocumented restriction or a bug in how community app updates are validated, so I'm looking for clarification.

    Summary

    For an already-installed community app, changing only the title in CloudronManifest.json (same id, new version, same everything else) causes the update in app UI updates to fail. The docs describe title as display-only and describe id as the app's identity, so a title-only change should not break an update.

    Reproduction

    1. Community app installed on an instance from a CloudronVersions.json URL.
    2. In CloudronManifest.json, bump version and change only title (keep id identical).
    3. Publish the new version to CloudronVersions.json / host it.
    4. Attempt the update from the dashboard (or cloudron update).

    Expected: update succeeds; the app's displayed name reflects the new title

    Actual: the update fails. Reverting title to its previous value and publishing again lets the update proceed. I removed and reinstalled the app afterwards, so I no longer have the original task/box log.

    What the docs say

    The title field is documented purely as:

    "The title is the primary app title displayed on the Cloudron App Store."

    Only id is documented as identity:

    "The id is a unique human friendly App Store id."

    https://docs.cloudron.io/packaging/manifest/

    Questions

    1. Is title intended to be immutable/identity for an already-installed app, i.e. is the effective key id + title rather than just id? If so, the manifest docs should state that plainly — they currently present title as display-only.
    2. If it's not intended, is this a validation bug? The update appears to reject a manifest that differs only in a display field.
    3. Is there a supported way to rename an existing community app via the manifest? Using the dashboard app label is a workaround, not a fix — the manifest title is what new installs and the App Store use, so the installed app and the package listing then diverge.

    Want to clarify before I attempt more renames via CloudronManifest.json title.

    EDIT :
    This is not about ca.cloudron.io which accepts the title change. It's about installed app dashboard, Updates / Check for updates / update.

    Indie app dev, scratching my itches : communityapps.appx.uk, portfolio at myca.appx.uk

    1 Reply Last reply
    1

    Hello! It looks like you're interested in this conversation, but you don't have an account yet.

    Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

    With your input, this post could be even better 💗

    Register Login
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • Bookmarks
    • Search