Your copy of Oculus Platform Command Line Utility is old

I'm getting this error both on my Oculus Developer Hub and Unity Platform Utility 

I've run the command and got a progress bar while doing so but I'm still getting this message.

In spite of this message, it uploads quest buildd with no problems but rift builds get server error messages

Your copy of Oculus Platform Command Line Utility is old.
Version 1.67.0.000001 has been released on Thu Oct 07 2021. 
Please use the following command to update it:  > Assets\Oculus\VR\Editor\Tools\ovr-platform-util.exe self-update 

The same problem, after installing the latest version, it gives an error

* Your copy of Oculus Platform Command Line Utility is old. *
* Version 1.67.0.000001 has been released on Thu Oct 07 2021. *
* Please use the following command to update it: *
*> .. \ .. \ Users \ User \ AppData \ Roaming \ odh \ ovr-platform-util.exe self-update

🙄

Anyone have a fix for this yet? Its been a week and still can't upload, becoming a major issue.

Any updates on this?

Error upon

Roaming\odh\ovr-platform-util.exe self-update *

Checking for the latest version
Already running the latest version 1.67.0.000001

On attempting to push apk bulid to alpha channel using Unity Hub. 

Yes, still seems to be broken, my guess is everyone who had an older version and upgraded in place it's probably working but those of use who are starting with the new version it's not.

OK, I submitted a ticket and after some back and forth with oculus dev support it appears this message is erroneous and can be ignored and is always output from the tool for whatever reason. The ovr-platform-util.exe is actually running and working but it failing a validation check of some kind but is not bothering to display any helpful information after the "Validating build..." message. I'm using Unity and it tends to want to add a bunch of permissions to the .\Assets\Plugins\Android\AndroidManifest.xml file used to build the apk. You could spend time figuring out which package was enabling them by looking inside various compressed files or package files or platform stuff inside of Unity itself but that's a lot of effort when you just want it to remove them. The solution I found to get the validation process to get far enough to display anything useful was to add these lines to the top of the AndroidManifest.xml file. The key was to add the tools schema so you can use the remove command below to remove the offending permission after Unity adds them. This should allow people to get some useful output from the tool and finally be able get an apk file uploaded. Hope this helps someone else.

bold is the new stuff I added to the file.

<?xml version="1.0" encoding="utf-8" standalone="no"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
android:installLocation="auto" xmlns:tools="http://schemas.android.com/tools">

<uses-permission android:name="android.permission.INTERNET" tools:node="remove"/>
<uses-permission android:name="android.permission.RECORD_AUDIO" tools:node="remove"/>
<uses-permission android:name="android.permission.MODIFY_AUDIO_SETTINGS" tools:node="remove"/>
<uses-permission android:name="android.permission.WAKE_LOCK" tools:node="remove"/>

To find out what permissions Unity built into your apk after you build it use the platform tools command appt to check.

aapt.exe d permissions <apk>