Oculus Go: Failed Entitlement Check

[RobbyC57D]

As the title says. Recently I get this message, "Failed Entitlement Check" when I launch the app Virtual Desktop Streamer.  I have owned the app for years.  

I tried uninstalling and reinstalling the App

Factory reset the The Oculus

Even Launched the app from the phone app 

All with the same results. 

I have also noticed that the app store will not load on the Oculus. It looks like it tries to start but then shuts down right away. 

I realize this is a very old device but any help is appreciated. 

Thanks

[desiv]

That's true, but it's also not quite that simple.
For instance, you might not be able to do that with the newer MS OSes.  At least 10 and 11 have active checks for compliance, unlike older versions of Windows which just check programmatically (i.e. not checking with MS) during install.

It's not that Meta actively disabled the games.

It is that those games have a check in them (and not all games/programs do), and Meta turned off the services to respond to that check...  Which, if it is different infrastructure than check for Quest games, doesn't surprise me...

Ideally, what I think should have happened would have been for the system to be designed that at end of life for the product, those checks were no longer required.  So assuming the hardware still worked, they'd keep running; just without support.

I'm not sure whether that is a Meta thing or a developer thing....

I'm not saying Meta did the right thing here...  And it's not even a big corporation thing.

I still have my original Kindle Keyboard working.  Now, I can no longer "buy" books on it.

But I can still buy books and send them to my Kindle keyboard.  I can still use it.

This is how I think Meta and the developers should have handled this...  

Meta and the dev seem to be going more of the way of MS and the XBOX 360.  Supposedly more the 200 games are going to disappear later this year when the store goes away.  Sounds like they will stop working too.

I hope Meta and the devs reconsider; it would be great if they came up with a solution on their backed, but I am not surprised...

I'm just glad there are people in the community working on solutions for those of us that plan on keeping our Gos running as long as they can.  😉 

[TheLegend27 · Accepted solution]

Hey everyone! I've been in the works investigating reports regarding the state of launching applications on the Oculus Go, despite the hardware officially reaching end of life. I definitely understand the need for jumping back into it as soon as possible, and want to address this as transparently as possible.

I just want to reiterate that the hardware for Oculus Go is indeed at the end of its life cycle, and we appreciate the extended support and enthusiasm everyone has shown for it over the long years. Despite the status, our engineering team has given me word that they're still investigating reports of the issues.

While our team can't promise a fix or guarantee ongoing support for end of life products, your feedback is incredibly valuable to us, and the correct teams are currently being flagged to explore all possible avenues. I'll be sure to keep you all updated on any developments or insights that our team gains along the way.

Thank you for your patience and I hope to have an update for you all soon!

Update 6/22/2024:

I wanted to circle back with an update on the Oculus Go application launch issues. Our engineering team has thoroughly reviewed the situation, and after careful consideration, they’ve decided that they won't be able to take on this project.

We know how much you all love and value the Oculus Go, and it’s been amazing to see the continued support and enthusiasm for this device. However, as it’s officially reached the end of its life cycle, our team needs to prioritize our current and future products to ensure we’re delivering the best possible experience.

Your feedback has been incredibly valuable, and while we can’t guarantee fixes or ongoing support for end-of-life products, your insights are always important to us and help guide our future efforts.

Thank you so much for your understanding and patience. If there are any new developments or changes, I’ll make sure to keep you all in the loop.

[VeArGo]

I am very disappointed by the communication policy of the support. It is very, very, very unlikely that nobody from the technical team can clearly state what the problem is after 4 weeks, If they really looked into this and could not find the reason it would really scare me using Meta services. From my IT experience I estimate it would take at max one day to find the problem and restore a service (maybe some delay if it is a management decision). Meta services had major outages in the past which were restored within 2 hours.

Please state clearly what the reason is:

Was it a management decision to shut it down?

Did the server break down or was isolated from the internet?

Are you not able the restore the service (e.g. missing backup)?

Are you not willing to restore the service?

Is it any other technical problem?

[TomCgcmfc]

@RobbyC57D  Please just give it up mate.  The Oculus Go has been unsupported for over 2 years now, and it's hardly likely to be resurrected, lol!

I enjoyed mine when it it first came out.  However, after the Quest 1 came out 5 years ago, the Go became redundant, to me anyway.  Since getting the Q3, both my Q1 and Q3 are now also redundant.

All tech devices reach a similar point, so just get over it imho.  If you don't like this, maybe send a complaint to someone on your Microsoft Windows smartphone, lol!  Cheers mate.

[VeArGo]

I am still using all my VR glasses from Meta/Oculus (GO, Q1/2/3), . Everyone has its pros and cons and different application.

As I mentioned before the GO is my travel device and is the most comfortable one for me . My Q1 is my sport device (actually already quite damaged but still working). My Q2 is my standard device with most apps. My Q3 is mainly used for mixed reality outdoors. I use Q1/Q2/Q3 by turns for PCVR since the battery life is quite low of all devices and I don't like cables or additional battery packs.

I only trash devices which aren't usable anymore for anything. You are joking but my old mobiles got also a second life as podcast player, webcam, mini-server, survailance cameras, mobile hotspots. Also my old laptops get a ressource-saving Linux at some point in time and can still be used many years. Sustainability is the motto of our times.

[desiv]

@VeArGo Agreed, as do I with my Go and my Quest 2.

That said, this is not unexpected to me.  It's a digital media only device and Meta has moved on.

I would have preferred that they left that architecture in place for validation, but especially if it is different architecture than what the Quest line uses, I can totally see a point where they no longer keep that running.

I too keep many of my older devices going (The oldest probably being my Odyssey 2; I have a decent amount of older (retro) hardware..).

But at some point in time, especially with digital only devices, things will stop working.  If I want to keep using it, I rely on non-supported methods.  
As there are non-supported methods for me to get a lot of my Go games working again, I've just been using that.

I think it's the price to pay for wanting to keep an older device going.  And some things are going to stop working.  More likely a business call than a tech issue.  

And that's fine too.  It happens.  I am disappointed, but now I just move the Go into the "I need to use alternate methods to support it" territory.

Did this happen sooner than I wanted?  Yeah.  But this was kind of beta level consumer VR tech (Gear VR stuff being alpha level, I still have some of that around too 😉 ) and I'm not surprised it's ending earlier than I would like.

But it's not a brick.  I can still use it and do. I've had a lot of fun with it recently figuring out how to keep using it and setting it up again.  I've used my Go more in the last few weeks than I had in the months before.

Yes, it requires me to be a tech and do tech stuff, which luckily for me I like...

Digitally authorized media is a different beast.  

[AlmightyFalcon]

Well, apart from what is possible when hacking the device itself, Meta is doing a fair good game at doing exactly nothing and evading our tickets/suggestions.. I finally got through 2 weeks ago, entering a private mailing with support through mail (not the web thing on this board)... after several days I simply got a response that they didn`t hear back from me. After a new mail, I got the response my ticket was closed.. This is truly unbelievable..

[desiv]

@AlmightyFalcon "This is truly unbelievable.."
To be fair, the Go was end of life'd.

From the Meta store page on it:

---
We won't be shipping new features for Oculus Go, and we won't be adding new Go apps to the Oculus Store after Dec 18, 2020. We'll continue to maintain the system software with bug fixes and security patches through 2022.

---
The fact that support tickets are being closed on an unsupported product doesn't actually seem that unbelievable.

As an owner, I would love for them to just fix this and if they do that would be great; them going above and beyond (IMHO), but it hasn't been supported for a couple of years...

[sayobel]

The issue isn't them not fixing a new bug. It's them creating an issue where thousands of purchased apps have been disabled BY THEM through some backend change that neither users nor app devs can do anything about. That's a separate issue from device support expiration. 

[desiv]

No, I don't think it is different.

It's not supported.  Something happened that broke most apps.

It could have been something Meta did (turning off infrastructure that authenticates apps maybe?  Existing auth certificates expired and the infrastructure to renew them is no longer on, etc..).

If they actually pushed out something that actively broke these, then maybe.  But that's unlikely.

It's much more likely that they turned something off or something expired and can't renew.

But it's still a non-supported platform.

It would be nice if they do fix it, don't get me wrong.  

What I am saying is if they do fix it, I will be surprised, because it is not supported.