Audiolink in worlds built for iOS seems to get stuck on "joining"
needs more information
radovan787
It seems like when joining iOS-built worlds (Worlds that are PC-Android-iOS compatible instead of just PC-Android worlds) with audiolink in them, it visually appears that the screen gets stuck on "joining". After disabling audiolink, the world does load successfully on iOS. (The world loads fine with audiolink on on PC and Android standalone with no issues). To make sure it wasn't just my world, I entered another world that had an iOS build and audiolink in the world. (The same result of getting stuck on the "joining" screen occurs)
However, from extensive testing, if someone else is also in that instance of that world and someone on iOS joins [Me in this example]. IOS successfully does join (and can even move around, etc if they press on the controls [even if they're not visually shown on screen]) according to the other user in the instance on quest standalone. On iOS, I only see "joining" on screen. [This led to me thinking that maybe after joining, the screen stopped rendering or something maybe {if curious, rotating the screen on iOS results in a black screen. If using mental memory to exit out of VRChat on iOS when stuck on "joining" after pressing on the correct invisible buttons, it's possible to exit out of VRchat and back into the app. But trying to enter VRChat again results in a black screen until the I restart the entire app after visiting that world.]
I'm not sure if it's an audiolink issue or an issue on my side but testing the same world (with the same features with audiolink on) on PCVR and Quest Standalone does not result in this issue occurring on either platform.
Device in use for iOS: iPhone 12 Pro
Android testing: Quest 3
PCVR: Gaming laptop and Gaming Desktop PC
Log In
StormRel
needs more information
Do you have some world IDs where we can repro this?
JantsoP
Could you link some worlds where you encountered this issue? Easier that way to reproduce this issue.
If the world is your own making, maybe its a bug in the and/or audiolink itself?