Snap title in the store listing does not inherit the `title` field from the snap
Expected behaviour
When the snap sets the title field and the metadata has not overridden the value of the title field is applied to the snap's "Title" field in the store listing
Steps to reproduce the problem
- Set up a snap repository with the
titlefield set - Set up BSI with the repository
- Browse the snap listing page after the snap is published
Specs
- URL: https://snapcraft.io/snap_identifier/listing
- Operating system: Ubuntu 18.04 AMD64
- Browser: Mozilla Firefox 65.0.1
Any progress on this @Lukewh ?
I wouldn't mind taking a shot at this myself but I can't find where this metadata is imported into the store.
I just promoted the OpenJFX Snap to the stable channel with the "Update metadata on release" setting enabled for the first time.
It looks as if the Title: in the store listing is being picked up from the name: top-level metadata in the snapcraft.yaml file. In this case, that was the "openjfx" lower-cased name. It should be getting the Title: in the store listing from the title: metadata in the snapcraft.yaml file, which is the properly-cased "OpenJFX" name.
I'll update the store listing manually until this is fixed.
Update 1: Actually, it seems I'm now unable to fix the title. I updated it manually to "OpenJFX" in the listing details form, but the store listing still shows "openjfx" for the title.
Update 2: And now it's fixed. There seems to have been a delay despite the message saying, "Updates to this information will appear immediately on the snap listing page."
Any progress on this? This issue is still present today.
We'll discuss this with the store team in our weekly meeting this afternoon. It appears to be an issue with inconsistent extraction from name and/or title fields. I'll add a comment to this issue later after the meeting.
The issue has been raised with the store team, who will be prioritising the issue in their next sprint (starting next week).
Hi,
I can confirm the title is being changed to the name when releasing a new revision to stable with Update metadata on release enabled
We are working on a fix.
Cheers
The fix is live on production, please let us know if it doesn't work as expected.
Cheers
Thanks @verterok closing this issue.
Please reopen if needed anyone!