iOS Build Environment Help Center
Hello,
I have this error when building with Cocoapods:
/usr/local/bin/bash: line 68: base64: command not found
gunzip: (stdin): unexpected end of file
Full log: https://pastebin.com/gZm2RUy1
OS : Windows 10 64 bit
Unity Version : 2020.3.12f1
iOS Builder : 3.35.4
iOS SDK : 14.5
In Unity I have imported Firebase 9.0.0.
Thanks!
I have created a question on StackOverflow too.
Hello
From what I read of your various posts (including the first one that you deleted), you don't understand what you are doing and are trying things at random like if you were in a hurry. This just won't lead you anywhere.
The CocoaPods subsystem is a FreeBSD-based virtual machine. All CocoaPods commands are executed in this subsystem, where a BSD userland quite similar to macOS' one (and much more similar than WSL's) is available.
The problem is here that, unfortunately, it appears that the "base64" command used by your "BoringSSL" pod is very macOS-specific and doesn't exist in the base FreeBSD userland.
I take note to fix that by adding a compatible implementation in the next version of the CocoaPods daemon.
*edit* version 3.49 of the builder will have it. I haven't tested whether other tools are necessary though.
Thanks a lot for your detailed replies here and on my other posts too!
“you don't understand what you are doing and are trying things at random like if you were in a hurry.”
Yes. Exactly. :)) It's very new to me.
I installed Ubuntu on my Windows and installed base64 on this Ubuntu to make bash work, but as I understand now, the daemon uses its own OS, so this won't help.
Do you have any recommendations on what can I try?
Do you think injecting Firebase can help? Or there will be conflict anyways?
Or is there a way to not use OpenSSL to avoid conflict?
The general rule of thumb is, when for a dependency of your project a precompiled version exists, by all means try to use it instead of relying on CocoaPods to rebuild it each time. This will save you a lot of time and skip a lot of potential trouble, as explained in the builder's help file.
Pier-Marie,
“I take note to fix that by adding a compatible implementation in the next version of the CocoaPods daemon.”
Do you have rough estimations about this?
I can send you the new version of the CocoaPods daemon by mail, if you want to try it. Contact me at pm at this domain.
Such great news!!!
I have sent you the email.
The problem with the BoringSSL pod is fixed.
You have other Pods that are written in Swift (namely "FirebaseSharedSwift"), the builder hints you to use the precompiled versions of the Firebase pods. This is what you need to do to have your project to build on Windows.
The procedure is roughly :
- Identify all the Firebase pods in your podfile, and their version number
- Collect each of them (from the Firebase GitHub releases page) - see the README.md file in each Firebase release for the version number of each component
- Read the programmer's documentation/release notes of each to find out whether they need a particular linker flag (such as -ObjC) to be added (Firebase typically does). Firebase also typically requires you to provide a GoogleServicesInfo.plist file with your Google ID in it (if you don't provide it, your app will crash).
- Inject these frameworks in your project using the "Add extra framework" button and remove them from your podfile
- Build and resolve potential compiler/linker errors by reading the messages and providing the missing dependency libraries/frameworks until no more errors.
- Deploy and run your project : if you get a crash, see the cause in the debug console, and fix what's missing as appropriate.
- Once you get a running build configuration, *save it* on disk.
If you're stuck on any of these steps (after reasonable effort), ask here for help.
Please upgrade your builder to the latest version. I see you're using version 3.35.4 which is very old, but version 3.48 has a fix that your project may require (undeclared call to sched_yield() in UnityWebRequest.mm).
Moderators: Pierre-Marie Baty