-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Carthage doesn't download Firebase binaries on Apple M1 #7039
Comments
Hi @d-date - hope you're doing well. I'm not sure about the We can't include the simulator slice for arm64 as well as the arm64 device slice, they simply can't be put into a Sorry about that! |
Hi @ryanwilson You can ignore I see your points and it's hard to continue to use Carthage until XCFramework be supported. I think the workaround to make us to use them in Carthage is Firebase team prepares binary for Apple M1, and prepare other jsons for versioning. Since SwiftPM is also not work for us now(#6472), it seems the only way to use Firebase in M1 now is use CocoaPods. Thank you for your help! |
@d-date FYI, the Firebase does also support a binary zip packaging that as of 7.2.0 is comprised of xcframeworks for everything except FirebaseML. See the download at https://github.com/firebase/firebase-ios-sdk/releases/tag/CocoaPods-7.2.0 |
@paulb777 Thank you for your suggestion. It's also good way to introduce as pre-build binary (except versioning). |
Carthage update on plans for binary xcframework support at Carthage/Carthage#3071 (comment) |
Latest "master" branch of carthage compile xcframework correctly. |
@mmdumi thanks for pointing out that Carthage has merged support. However, it's still not in a release so we can't break all existing Carthage users until at the very least there's a release. |
Actually, I haven't seen evidence that binary support for xcframeworks has yet merged. The PR that added support for source xcframeworks explicitly says it will be addressed in a subsequent PR. |
As I understand it, no-use-binaries is useless on M1 Macs because there are no arm64 binaries. Which seems kind of silly but I think I read you must build each dependency. |
It's there now. After getting 0.37.0, it suggested I rerun with a switch to build an XCFramework, which worked, but then a dependency I am getting from SPM is failing on running in the sim because it can't find the x86 binary. Which makes no sense as I am on M1 and Xcode is not running in Rosetta? |
Carthage PR in progress at Carthage/Carthage#3123 |
Any update on this? The PR was merged |
I'm planning to investigate this week. |
I think the download link you provided doesn't include |
Correct the Swift packages are so far only available via CocoaPods and SPM. |
On further investigation, the Carthage release PR with the fix is open and not yet released. I'll follow up when 0.38.0 is available. In the meantime, if anyone wants to validate that the Firebase xcframeworks work with the pre-release, it would be appreciated. |
@paulb777 Just validated, works for me 👍 |
Thanks @dmhts! In that case we should be able to publish a Carthage xcframeworks update soon after 0.38.0 is available. |
Carthage 0.38.0 is now released. We'll work on restoring Carthage publishing sometime after the Firebase 8.0.0 release. |
[REQUIRED] Step 1: Describe your environment
[REQUIRED] Step 2: Describe the problem
Carthage doesn't download any firebase binaries on Apple M1 with Big Sur.
When running
carthage update --no-use-binaries --cache-builds --platform iOS
, the empty json has downloaded.Steps to reproduce:
Relevant Code:
The text was updated successfully, but these errors were encountered: