Why is TestFlight telling me "the SwiftSupport folder is missing"?
Wowfunhappy opened this issue · 17 comments
I'm trying to get the visionOS client loaded onto my Vision Pro. I tried following the build instructions, but for some reason, I can't get my Vision Pro to appear in the list of run destinations. The Vision Pro says that it's paired to my Mac, and the headset appears in XCode's "Manage Run Destinations" window. For some reason, however, the headset does not appear in the dropdown of the main XCode window.
The problem is likely that I'm using an Intel Mac (alongside some secret Terminal commands). Regardless, since I am able to build the app but can't seem to pair my headset, I figured I would try using TestFlight to get it into my device. I changed the name of the app and the bundle to be unique.
The app uploads to App Store Connect without issue, but a few minutes later, I consistently receive this email:
I have no idea what this means, and Google wasn't any help. I'm already using XCode 15.2, the current latest as far as I'm aware. Does anyone know if this error can be fixed?
If this is expected, or not actually related to alvr, I apologize! I was stuck and didn't know where else to ask!
This line in the Xcode project mentions version 15.3. The project was probably saved with a newer version. I don’t think an older version of Xcode will try to fix it.
Thank you. Unfortunately, I actually tried again yesterday with the Xcode 15.3 beta but kept getting the same problem.
According to Technical Note TN2435, Apple doesn't allow embedded dylib files in iOS/watchOS/tvOS, and breaking this rule causes ITMS-90426. VisionOS is not mentioned, but presumably has the same restriction.
You need to embed a .framework instead.
So somehow, ALVRClientCore needs to be compiled as a .framework instead of a .dylib. I messed around for a bit but couldn't figure out how to do this.
@Wowfunhappy I tried embedding the Rust library into a .framework in #67.
I don't have access to App Store Connect: does rebuilding with that pull request resolve the issue?
This framework does not work properly on a VisionPro
@dualist3 What happens when you build it with the framework? Does it fail to build, or does it crash on launch; if it crashes, would you be able to share the crash message? Thank you so much.
(I don't have a Vision Pro, and it works on the Simulator)
No crash, after connecting to SteamVR via ALVR and pressing the Enter button, the screen goes completely black
@dualist3 Thanks. I can't reproduce this on the visionOS Simulator, for what it's worth (connecting does work for me, and image does display); that's really weird.
alvr connection is work But there is no image and no crash inpu
Do you have a recent version of the ALVR streamer? PR #67 is based off the main branch, which requires a newer streamer version than before—and the version mismatch can manifest as a completely black screen. I'm using this nightly build: https://github.com/alvr-org/ALVR-nightly/releases/tag/v21.0.0-dev00%2Bnightly.2024.02.23
The version being used is the ALVR-nightly
I am sorry, I had to return my Vision Pro to Apple yesterday, so I am no longer able to test this. Thank you!
@dualist3 Can you confirm which nightly version you're using? Zhuowei's branch works perfectly fine for me with the build from 2024.02.23.
2024.02.27，I encountered this issue when using Zhuowei's branch to package it into an app and accessing it through tf. The tf link is located here https://testflight.apple.com/join/BXOkz2Cy
2024.02.27，I encountered this issue when using Zhuowei's branch to package it into an app and accessing it through tf. The tf link is located here https://testflight.apple.com/join/BXOkz2Cy
that testflight works but its a very old build it doesn't have the hand tracking controller support or any of the major bug fixes can anyone update that testflight with a newer build?