Forum Discussion

🚨 This forum is archived and read-only. To submit a forum post, please visit our new Developer Forum. 🚨

2 Replies

Replies have been turned off for this discussion
  • dan-gx's avatar
    dan-gx
    Explorer
    5 years ago

    +1 this is important for being able to implement a decent deployment pipeline that can handle rollback with Oculus Platform Utility cli.
    Can sort-of workaround this by intentionally failing setting an unused channel with a very old build in it and parsing the error.
    e.g. to get the current release bundle version:

     

    $ ./ovr-platform-util.exe set-release-channel-build --app_id <app_id> --app_secret <app_secret> source-channel ALPHA --destination-channel RELEASE > out.txt

     

    Then regex parse the version code from out.txt
    "ERROR: You are trying to add an APK with version code 12 to a release channel, but the previous APK on this channel has version code 80. The version code must be higher than the previous version code."

     

  • twistedpixel_bob's avatar
    twistedpixel_bob
    Expert Protege
    2 years ago

    Do you still use this workaround?  Hard to believe there's no API for this.  It seems like the ovr-platform-util now doesn't care if you set a build to an older version - so it won't return the latest build number.