Modify the Xcode project linker flags and Data folder on ios export. #22
Conversation
|
@timbotimbo Merge this, this is a so requested feature from people hahaha, also, i would like to know if you guys faced any issue with memory leak with unity on ios ?, i`m currently facing this problem and it is cause the app to crash |
|
@learntoflutter can you help with that ? |
|
This looks great @timbotimbo thanks for your contribution. I'm on holiday at the moment, so since this is non urgent I'll look to merge this when I get home. I'll need to take some time to understand how I need to update the README and how this impacts existing projects (I'll test this one one of my own projects) |
|
@CristovoXDGM memory leaks are a common problem in Unity, I would suggest troubleshooting your Unity project first independently of Flutter using this guide. If after that you think there is a memory leak issue with flutter_embed_unity please raise a separate issue with a minimal reproducible example and I will investigate |
|
the current project that i`m using is the example ones from yours, i just added a 2d assets and remove it and send backa. message to flutter, this should not be a problem for AR @jamesncl |
|
i also use the pauseUnity method when i`m not using unity |
Related issue
Fixes #1
Description
This automates the 2 manual steps that need to be done after each ios export.
-Wl,-U,_FlutterEmbedUnityIos_sendToFlutterUnityFrameworkI tested a fresh export using Unity 2022.3.21f1 and was able to run the example project on an iPad using Xcode 15.
Besides generic Xcode stuff like setting the signing id, the only manual step was to to add Unity-iPhone to Runner.
I wasn't able to append an existing ios export, as the export dialog always cleared the destination folder.
Therefore I haven't tested if this runs into any issues on an already edited Xcode project.