-
Notifications
You must be signed in to change notification settings - Fork 24
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
[Unity 2019.4.10f1] Get an error when exporting to Xcode. #29
Comments
「更なる問題」に関してのエラーは以下の記事にて解決しました。 「Unity-iPhone/UnityFramework/」のフォルダを右クリックで選択。 「New File...」で「Swift File」を選択し、Targetsにて全てチェックを入れて作成。 作成時にポップアップが出て「Create Bridging Header」を選択しました。 ここで作成したファイルを消すとまたエラーが再発します。 |
Hi, Thanks for reporting this. The CocoaPods building script of LINE SDK for Unity does quite a few things, including adding LINE SDK pod entry to Podfile, installing it, and also set up other necessary build settings automatically. Most of these require you have a valid Ruby environment. Your first attempt to install it in an empty exported project seems to be related to Ruby permission. The system-bundled Ruby always installs gems under a system path, which requires your password for And for your existing project, it seems that you already have other CocoaPods dependencies. LINE SDK for Unity now requires to build as framework and linked in a dynamic way, so However, if your existing pod dependencies requires to build as a library and linked in a static way, LINE SDK for Unity won't work now. In this case, maybe you can consider switching to another integrating way, Carthage, which is less invasive to your existing project:
You can find more instruction and comparison of two on the same page. To switch the dependency manager used, check the Settings for iOS export. |
私はCarthageを使用しようと思います。 操作としては、Unityの「Preferences... > LINE SDK」からiOS Dependency Managerにて「Carthage」を選択しました。 UnityでBuild and Runした際のエラーがこちらです。
|
Hey, A workaround for this has been applied in #30. Here is a beta version and maybe you can give it a try, in which the Carthage building failure should be fixed. |
私はこれを試しました。結果として成功しました。 Firebaseの件はこれと別件のIssueだと思います。新規で作成しても良いですか? |
To install LINE SDK with Firebase (or any other libraries requiring CocoaPods as a dependency manager) would be tricky. It is mainly Unity to blame for the lack of a standard dependency manager. But, yes. Feel free to open a new issue and we can check and find if there is a good solution for it. |
The changes in #30 will be contained in the 1.1.5 release soon. I am closing this now. |
最初に、バージョンについて説明します | First, I will describe the version
LINE SDK for Unity : 1.1.4
Unity Hub : 2.4.2
Unity Editor : 2019.4.10f1
Xcode : 12.4
Mac OS : Big Sur (11.2)
私が行った操作 | The operation I did
新規でUnityプロジェクトを作成し、LINE SDK for Unityのパッケージをロードし、iOS用にビルドしました。
I created a new Unity project, loaded the LINE SDK for Unity package, and built it for iOS.
私が期待した動作 | The behavior I expected
UnityからビルドしてXcodeプロジェクトが起動するのか普通だと思います。
I think it's normal to build from Unity and launch an Xcode project.
発生した現象 | Phenomenon that occurred
その結果、ビルドはエラーが出て中断されました。
Result, the build was interrupted with an error.
以下はその際のエラーです。
The following is the error at that time.
仮の解決方法?? | Temporary solution??
Unityで書き出し先に指定したフォルダにはXcodeのプロジェクトが書き出されていました。
The Xcode project was exported to the folder specified as the export destination in Unity.
そのパスを指定して
pod install
を実行することでLINE SDKをCocoaPodsで導入できました。I was able to install the LINE SDK with CocoaPods by running
pod install
with that path.実機で実行できました。
I was able to execute it on the actual machine.
更なる問題 | Further problems
一時的な解決策が分かったので既存のプロジェクトに導入しようとチャレンジしました。
I found a temporary solution, so I tried to introduce it into an existing project.
ただし
pod install
してもXcodeのビルドはエラーが出ました。However, even with
pod install
, I got an error when building Xcode.こちらが新規プロジェクトの場合のPodfileです。
Here is the Podfile for a new project.
こちらが既存のプロジェクトに追加した場合のPodfileです。
Here is the Podfile when added to an existing project.
Xcodeに出力されたエラーはこちらです。
Here is the error output to Xcode.
The text was updated successfully, but these errors were encountered: