Imported package is displayed twice in Package Manager in Unity 6

My asset package ‘Timeflow Animation System’ is appearing 2 times in the Package Manager in Unity 6, listed under In Project. It is the same install - if I remove one, it removes both.

This is confusing users and making it hard for people to find the samples.

The first one is listed under Packages - Asset Store and doesn’t show the samples. I don’t know why this is being displayed and is new in Unity 6.

The second one is what I would expect to see and includes the Samples tab. This is where users need to go, but they are finding the first one above instead.

Comparing the same package to Unity 2022, there is just 1 listing for Timeflow (as it should be).

This is a hybrid UPM package. If it helps, here’s the package.json in use:

{
    "name": "com.axongenesis.timeflow",
    "version": "1.6.4",
    "displayName": "Timeflow Animation System",
    "description": "Timeflow is a powerful and flexible animation system built from the ground up, offering a new range of creative possibilities for designers and developers. With a focus on motion graphics, cutscenes, and music synchronization, Timeflow offers a robust integrated track and channel based timeline with advanced curve editing tools, procedural animations, dynamic behaviors, and much more. ",
    "author":
    {
       "name": "Axon Genesis",
       "email": "support_axongenesis.com",
       "url": "https://axongenesis.com/timeflow"
    },
    "unity": "2021.3",
    "type": "tool",
    "documentationUrl": "https://axongenesis.gitbook.io/timeflow",
    "changelogUrl": "https://axongenesis.gitbook.io/timeflow/reference/version-history",
    "keywords": [
      "animation",
      "timeline",
      "cutscenes",
      "motion graphics"
    ],
    "samples":
    [
       {
          "displayName": "Demo Built-in RP",
          "description": "A buildable demo app with example assets and scenes for the built-in render pipeline",
          "path": "Samples~/Demo_Built-inRP"
       },
       {
         "displayName": "Demo HDRP",
         "description": "A buildable demo app with example assets and scenes for the high definition render pipeline",
         "path": "Samples~/Demo_HDRP"
      },
      {
         "displayName": "Demo URP",
         "description": "A buildable demo app with example assets and scenes for the universal render pipeline",
         "path": "Samples~/Demo_URP"
      },
      {
          "displayName": "MidiJack",
          "description": "Support for live MIDI input using MidiJack with examples",
          "path": "Samples~/MidiJack"
       },
       {
         "displayName": "Minis",
         "description": "Support for live MIDI input using Minis with examples",
         "path": "Samples~/Minis"
      },
      {
         "displayName": "Spine",
         "description": "Support for Spine Animation in Timeflow with examples",
         "path": "Samples~/Spine"
      },
      {
         "displayName": "Timeline",
         "description": "Integration with Unity Timeline with examples",
         "path": "Samples~/Timeline"
      }
    ]
 }
1 Like

Could you file a bug report for this?

1 Like

Bug report IN-89725 has been filed

2 Likes

Here’s the latest on this issue. Although the bug has been confirmed, it is not going to be fixed.

Refusing to support hybrid packages even though they do work and are accepted by the asset store seems a bit absurd to me, though I don’t know what the underlying reasoning is.

Is there any other good way to provide samples that users can choose to import separately? I’m of course already aware of strategies with traditional .unitypackages, or hosting my own samples on github or cloud storage, but none of these are quite as easy for users as going to the Samples tab and importing the ones they want.

im havin the same problem. i dont understand exactly what a hybrid package is, but i noticed some assets get imported in the packages folder and some others in the assets folder