Edgar Neto 👻

Hi! Thanks for bringing this feedback. It highlights the importance of adding a Unity API to call takeSnapshot on the native apps. We will consider adding this to the demo app. The second option is definitely what I would recommend. If for some reason the callback with the image is not activated automatically, you can just…

Thank you, this is great feedback. We will add it to future versions of the sample app.

Hi Yassine. Thanks for your contribution to the forum. Yes that's correct. You need to have cocoapods installed for the unity wrapper to work. It will try to run Cocoapods automatically as part of the postprocessing build. But this is ultimately just for convenience. If the postprocessing build is giving you any trouble,…

Hi Yassine, It looks like the output that you're getting from cocoapods are just warnings and not errors. Thanks for flagging that they behave as errors when running from the Unity post-processing build, I'll work on making them look like warnings. But if these are the messages you are getting in the Unity console, feel…

Ok let me know if that works. That field should contain the relative path between your Unity output folder and the ios wrapper folder. If you made changes to the export folder, you'll need to change that field. Also I've heard problems in the past where spaces in the path would create problems. I can see you have some…

Hello, Thanks for reaching out in the forum. We had a similar issue here: https://community.snap.com/snapar/discussion/3341/unity-sample-app-build-for-ios-stuck Is this the same problem you're having? Please check if this solves it for you. If not, please let me know here and we can discuss further.

Hi Leo, Thanks for posting your question here. This is a good catch, I don't think we tested enough on Windows. I can see that the path for where it's looking for cocoapods is looking weird: all the dots after unity-ios-export, that doesn't look right. It tries to concatenate an absolute path to a relative path, so it…