-
Notifications
You must be signed in to change notification settings - Fork 75
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
Framework 'UnityFramework' not found #136
Comments
Hey @Asim313, I would recommend rebuilding the UnityFramework and making sure you set follow each step to make sure the data folder is public and the plugin/ios/callproxy.h file is set to UnityFramework. Use the steps the readme as I'm just going off the top of my head right now. All this to say, @azesmway did an amazing job outlining the steps. As someone that has ran this flow hundred of times I would encourage you to just start over and careful go through each steps. If so, should works flawless. Let me know what happens. |
@TruAmbition I have followed every single step exactly as outlined in the following. I think the issue might be related to a missing UnityFramework in unityfamework.framework folder, but I'm not entirely sure of the exact problem. |
Can you please confirm the version of Unity, MacOS and Xcode you are using? |
MacOS : 14.5 (23F79) |
We haven't officially confirmed support for Unity6 just yet. However, we have had someone confirm things are working with the latest changes we have staged to fix issues with Xcode 16. You can find that information regarding their tech stack here. Please note, these changes will be applied and released on version 1.0.11, we are in final stages of checkout after and hope to have release as early as next week. Note, this fix is not intended to work with Unity6, however it appears developers have confirmed it working without any breaking changes. Please also note his remarks about cocoa pod version. |
@Asim313 the v1.0.11 release has been published. This contains the fixed for Xcode 16. This way you can do a checkout without having to manually adjust the code to work with Xcode 16. If you would, please, confirm this all work for you and provide you stack such that we can have additional checkout done for this project working with Unity 6. I will await your response before closing the ticket, if no response, I will close the ticket here as resolved in the next week or so as to keep the fixable project issues to a minimum. kind regards, |
Okay i will give you feedback ASAP |
@TruAmbition still got same issue. |
@Asim313 Sure thing, give me a moment to test and get back to. However if the Unity framework already being zipped. Idk if I'll get a different result. If you want to frame out a project in Unity and send me the Unity project. I can see if I can get it to run in a fresh react project. If so, I can send that to you. Let me know. I'll do my best to replicate your build setup. I have both Intel and arm based Macs for checkout. |
@TruAmbition I'm so happy and deeply grateful for your thoughtful response. Your dedication and effort truly stand out, and I sincerely appreciate the hard work you put into helping me. I'm using MacBook 2019(Intel base) Here is my orignal unity project. |
@Asim313 you are more than welcome. I know exactly where you are and I've been helped by this community in such a way that I can't help but want to give back. I have the files downloaded, I'll be able to do testing and checkout later today and get you an update by tomorrow no matter what the results are. |
Okay no problem. Take your time 😊 |
Hey @Asim313, just wanted to let you know that I was able to reproduce your error after installing the necessary dependencies for the UnityView to work. I'm going to play with it more tomorrow. Been a long day so I'm pretty tired. I think I did notice in your Unity project you are missing the assets/plugins/iOS directory with all the scripts provided in the repository example directory. I don't think that was the problem you were facing though. I just created a new Unity project with the same version and a fresh react project. I got the Unity framework imported and was able to build the react native app correctly. Things didn't turn until I started installing the rest of the dependencies. Just wanted to give you a quick update, I think it's fixable for sure, just need a good night sleep before checking again. I'll be in touch, Thank you kindly for your patience. |
@TruAmbition I have added the iOS plugin (including NativeCallProxy files) under the Assets/Plugins directory and generated a build for Xcode. Following that, I created the UnityFramework build as per the instructions but encountered an error. Could you integrate the iOS plugin into the provided Unity project and complete the process for me? |
@TruAmbition I'm waiting for your response. |
Hey @Asim313 sorry, I got sick and was unable to do as much as I wanted. Originally I was hoping to get your project working. But the issue was discovered with a fresh react native project + Unity 6 project. I think for now, This will be a long running issue that we will hope to resolve. I hope that you will continue troubleshooting and share any findings with the community. I plan to do the same with a lighter week ahead. Thank you for your patience |
@TruAmbition I have created a new unity project and try to integrate with ios. |
Yes. This is the issue fixed in 1.0.11. Unfortunately we are still pending the package update to NPM. If you would like to, you can use my fork in the meantime. If so, in your package.json use this line instead: "@azesmway/react-native-unity": "github:TruAmbition/react-native-unity#v1.0.11" This will use my fork that has the 1.0.11 fix. Sorry for the inconvenience, we will try and get the NPM package updated asap. Let me know how it goes after this if you would please. Thanks |
@TruAmbition getting same issue with this updated code. error: Undefined symbol: __mh_dylib_header |
@TruAmbition Undefined symbols for architecture x86_64: |
"@azesmway/react-native-unity": "github:TruAmbition/react-native-unity#v1.0.11" Sorry, forgot the very import rebuilding of pods step. |
@TruAmbition Already tried but same error |
Are you still trying with Unity6? I would say try without unity 6 until I user Unity 2022.3.46f1 |
Yes, I'm using unity6 |
Rebuild is required |
@TruAmbition Are you available for a short meeting(zoom)? |
Hi @Asim313 I am not, Thank you for asking. Please note that the latest version 1.0.11 is not published to NPM. I hope this helps you along your journey. We plan to look more into Unity6 at the top of the year. Please share any findings you do have. kind regards, |
Facing the same issue.. @TruAmbition should we use the unity 6000 or not? |
@gyanani-ritika yes, assuming you are getting this error. This project currently hasn't been validated/updated to work with Unity 6 just yet. Please continue to use a pre-Unity6, LTS version of Unity. This should solve the issue for you as long as you have the latest version of the npm package (1.0.11) installed and Xcode 16.x I hope this helps. |
I have added the build under unity/builds/ios/ but got this issue while react native build
@azesmway Please help me with this. I have followed all the steps and instructions for iOS.
The text was updated successfully, but these errors were encountered: