-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing iOS arm64-simulator Framework #61
Comments
Thank you for reporting this. I am looking into it, will get back to you with an update as soon as possible. |
@nassosterz-ms , great, thanks! |
Question, would the x86_64 simulator framework for you also? We have that readily available here: https://github.com/PlayFab/PlayFabParty/releases/tag/v1.10.5 |
That would only work for Mac users on Apple Silicon devices (everything made in the last 4 years) if they build in an environment that significantly increases build times. It also is not straight forward. Generally the advice for library authors is to either release binaries in the form of an .xcframework that includes all of the platforms and architectures they support or the source code. An XCFramework is just a collection of frameworks / libraries. While releasing a XCFramework would be preferred, I can build that myself with all of the prerequisites: Device Arm64, Simulator Arm64, Simulator x86. Given that MacBooks with an M1 processor came out a long time ago now, there will be fewer and fewer devs with x86 hardware going forward. |
M1+ MacBooks build for simulator on the arm64 architecture, but PlayFab is missing the arm64 simulator framework. Could PlayFab provide the arm64 simulator framework as part of the release? This can be either provided inside the existing simulator framework or separate. My end goal is to create a static xcframework that I can link against to allow my team to build for simulator on Apple Silicon devices.
When building for simulator, providing the destination "generic/platform=iOS Simulator" should be all that is needed.
The text was updated successfully, but these errors were encountered: