Forum Discussion

Razalghuul's avatar
Razalghuul
Protege
12 months ago

Hey META we need to improve the way updates of the SDKs are made

First of all thank you Meta for the hard work to improve the SDK with a lot of frequency BUT can we please find a way to make the SDKs updates less horrible? 50% of the time after an update from the package manager something breaks in the project, and I dont mean incompatibly, I mean stuff with the packages, library folder etc

I was so excited to try the new Depth API with v67, but I had to rollback everything to v66 because I couldn't get rid of an error not finding OVR Input.

Its amazing to have a rapidly evolving environment for Quest but please lets make this in a better way, starting by updating the version number on ALL packages, make it as easy as update the main package and that it updated all the dependencies.

Error
package manager
SDK
Unity
updates

15 Replies

  • CerebralFixAdmin's avatar
    CerebralFixAdmin
    Honored Guest
    12 months ago

    I think they just haven't (forgot?) to rollout The MetaXRInteraction SDK to v67. It looks like there is an update for it, but it's only currently available in the all-in-one sdk.

    Hopefully it will rollout soon as we're also blocked on the same feature.

  • Mikyjax's avatar
    Mikyjax
    Protege
    12 months ago

    Hello Razalghuul CerebralFixAdmin Could one of you help me please?

    How do you update those sdk? I'm in 2022.3.31f1 in the package manager.

    I select packages: In Project and I can see all of my meta package are on 66.0.0.

    They all have the checkmark with means up to date I think. When I refresh they don't show the 67 version and I have only the Remove option, not the Update.

    Am I missing something?

    Thanks a lot for your help.

     

    • florian.buchholz.1988's avatar
      florian.buchholz.1988
      Expert Protege
      12 months ago

      There is an update visible for V67 on some SDKs, which you can see if you directly select it. But if you installed them via the All-in-One, they are probably not showing up as “Update”, since that should be done by the AIO.

      And I totally agree, the Quality-Control of Meta regarding the SDKs is the absolute worst. They just push without testing it in existing, larger projects.

      In the last 4 versions, it destroyed the Grabbable because they didn't bother to check how to dynamically replace it with the new version, right now on V66 the Simulator is broken (White screen). I am just afraid of what breaks with V67.

    • Razalghuul's avatar
      Razalghuul
      Protege
      12 months ago

      On almost all packages if you go to version tab, you will the v67 update button 

  • stevenlinton's avatar
    stevenlinton
    Protege
    12 months ago

    I found that you can update MetaXRInteraction sdk to 67 manually by downloading it from

    Meta NPM Server for Oculus Developers

    And then manually update in package manager.

    This gets rid of the OVR Input errors. It's not a great solution, but probably beats waiting a month for the next update.

    • florian.buchholz.1988's avatar
      florian.buchholz.1988
      Expert Protege
      12 months ago

      How is that version any different to the one in the unity asset store? You can download each of the asset packages alone, and you don't need to use the NPM Server to do it.

       

  • iByte's avatar
    iByte
    Member
    12 months ago

    Someone at Meta has made some mistakes. Both the com.meta.xr.sdk.all and com.meta.xr.sdk.interaction.ovr show on the Meta website as version 67 but they are only available via the package manager as version 66. This mess happened a few versions ago as well. Someone at Meta please look into this.

    I think because it is still at v66 at com.meta.xr.sdk.interaction.ovr (even though the meta website says it is at 67) the com.meta.xr.sdk.all cannot be moved to v67

    • florian.buchholz.1988's avatar
      florian.buchholz.1988
      Expert Protege
      12 months ago

      Again, you can download the Version V67 for some of the packages in the Package Manager, you just have to know how:
      If you go to Version History, you have the option to see the newest version, if you are using AiO.

      There you can download directly.

      And yes, you HAVE to go to version history to see it.

       

      • iByte's avatar
        iByte
        Member
        12 months ago

        I was already well aware of the work around, thanks anyway. The point of my (and others) post was to hopefully get somebody at Meta to do their job. This is not the first time these releases are getting messed up. Is it really  too much to ask?

  • shaji.926391's avatar
    shaji.926391
    Explorer
    12 months ago

    Thank you, Meta, for your continuous efforts to enhance the SDK with frequent updates—your work is truly appreciated. However, I wanted to share some feedback regarding the update process, which has been a bit challenging for many of us.

    Often, after updating the SDK via the package manager, we encounter issues where parts of our projects break. This isn't just about compatibility but also involves issues with package references and library folders. For instance, I recently encountered a problem with the new Depth API introduced in v67. Despite my eagerness to try it out, I had to revert to v66 because of an error related to OVR Input that I couldn’t resolve.

    To improve the experience, could we consider a few adjustments? First, updating the version numbers on all related packages consistently could help ensure that dependencies are properly aligned. It would also be fantastic if the update process could handle these dependencies automatically, making it as seamless as updating the main package.

    We all appreciate the rapid advancements and the innovations you're bringing to the Quest environment. Streamlining the update process could significantly enhance our development experience and reduce the frustration associated with these frequent changes.

    • neuroathlete.2023's avatar
      neuroathlete.2023
      Explorer
      11 months ago

      Same here, some scripts where suddenly missing on the sample prefabs. Solved it by deleting the Library Folder and all the stuff that gets recreated like assemblys and so on.
      After this all was good again. Can't tell if a complete reimport would have been enough.

      hope this helps anybody.

      Cheers Christian

       

  • azhar.328866's avatar
    azhar.328866
    Explorer
    12 months ago

    Thanks for the feedback! I understand how frustrating frequent updates can be, especially when they break things. Your suggestion to streamline versioning and dependency management is spot on. I’ll pass this along to the team to help improve the update process. Thanks for your patience and support.

    • r.g.jones.5's avatar
      r.g.jones.5
      Honored Guest
      12 months ago

      Whoever fixed this at Meta - Thank you v67 is now available to download as part of the all in one and the Interaction SDK version issue was also fixed.