Forum Discussion
"Multiple Devices Can't Access This App At The Same Time" Error for my App with Latest QuestFirmware
In-house Quest 2 headsets started getting this error ("Multiple Devices Can't Access This App at the Same Time") as soon as they got the new firmware today, whenever more than one person (logged into the same developer account on multiple Quests) launched the application at the same time. This hasn't been an issue for us in the past. I assume there's some permission flag we need to set to allow this, but I'm struggling to find it. Does anyone have any guidance?
Thanks!
-Eric
13 Replies
Hi Eric! Just to confirm, did you enable "App-sharing" for your app? What is your app ID/name? Feel free to create a ticket with us too: https://developer.oculus.com/contact
Furthermore, I wouldn't recommend using one developer account to login/test an app on multiple devices. As far as I know, I don't think this was ever really supported. To access your app on different devices concurrently, please use a different developer account or Test Users https://developer.oculus.com/resources/test-users/
Indeed, i'll echo what others are saying. This is a complete mess. We are on project #3 with a massive cultural institution, the first 2 projects we did some interesting single-device work to visualize a new museum being built. Now we've built a beautiful VR tour of a key gallery that is going to be shared with school classes, as a preview of the eventual real location. And everything is at risk because it's logistically impossible to serve up our app to multiple devices in a convenient way. Asking a museum team to navigate many multiple facebook account creation for something shared with hundreds of kids. Wow. From my perspective, advocating the use of VR was getting to be a real thing that I want to promote. This takes it all the way back to my groundhog days of 2 hrs sleep every night in the 3 weeks development lead up, and no sleep for 4 days running shaky demos of Sundance Film VR projects in 2017. It's 2022. Shouldn't be this way. We need a solution!
michellaneous is there any progress on resolution to this issue? we are having the same problem
michellaneous Hi, thanks for your reply to ericliga's question. We're having the same issue and it's causing quite a problem for our shop. We're an enterprise software shop and our clients are not tech-savvy, so one of the issues is that having a customer manage 10 headsets with 10 different logins is a non-starter for our customers. Is there a way, from a development standpoint, to allow multiple headsets, logged into the same account to run the software at the same time?
Hi Eric,
I feel your pain! We are having the same issue and we are losing business because of it. We have 20+ clients in the Education sector using our app during workshops with multiple simultaneous users. Since our clients have used the same Facebook account on all devices, all simultaneous users but one are getting the same message. This makes deployment effectively impossible and clients had to cancel many sessions, often as those had already started. For obvious reasons, the proposed solution is much too time-consuming for our clients as it would take about 30 mins per device and some have litterally hundreds. Creating test users via a Developper Account is also not a viable option. I cannot stress enough how critical an issue this is.
Could you please make us aware of any plans to solve this challenge? If so could you please email me at chris@bodyswaps.co?
100% michellaneous this is ridiculous that you've implemented this prompt. You say you're "Pioneering an Immersive Learning Ecosystem" but this prompt has essentially made it impossible to use Quest 2's in any enterprise use case where there are a set of Quests 2's being used. We work with schools, and it's not scalable to have a separate test account for 30 individual headsets. Surely it is possible to make the distinction between free, and paid apps, and prevent this prompt from appearing for free apps?
This will provide a viable workaround whilst you are refining the Quest for Business offering!
Absolutely agree. For example, we're partnered with ENGAGE which is a VR social platform specifically aligned to education, training and enterprise use. The app itself is free because they have their own subscription service model. They have expressed frustration with this new change, as clients have been coming to them for assistance.
If they could, ENGAGE would happily turn off this additional check if that power were placed into the hands of its developers rather than it being forced onto all apps.
Have anyone found a way to fix it I’m trying to play population one and keeps saying this
What's up with this issue? For a while there we had it solved by checking "Inherit organization entitlements" on our studio test user. But as of v38 that does not seem to remedy things at all, and now our entire studio fleet is just unusable unless we set up test user accounts for every headset which can quickly become a configuration nightmare. Making sure to invite each and every account to the right BETA release channels etc.
michellaneous Is there anything you can offer? It's obviously technically possible to make the distinction between free and paid apps given this prompt never used to appear. I can't comprehend why you are just leaving all enterprise customers in the lurch until you release Quest for Business? Based on your blog post Quest for Business will not be available until 2023.
If you remove this prompt for free apps, it will make the Quest 2 usable once again in an education/enterprise context while you work towards releasing your new business offering. And no, it's not viable to factory reset every single Quest 2 and use an individual test account on each one.
It seems I have found a workaround for now...
1. in your organization, allow the role your client is on to share apps. Go to your organisation dashboard>members> roles>edit the role you wish to have this enabled on>app>app sharing
2. Make sure that on ALL headsets sharing the same account the settings>users>share library feature is turned OFF. If one of the headsets that shares the app has that turned on all of them will get the message.
Why you have to turn it on on the dashboard but turn it off in the headset I do not know.
