iām finishing up a UnityAds extension for OpenFL, i already have it working on android, but iām having some problems with iOS. in this case, the test app i built crashes (not the build of the extension itself, that works perfectly) why is missing the UnityAds.bundle file with the following message in the xCode console:
Please move the UnityAds.bundle into the Resource Directory of your Application!
i already tried using the tag <dependency> in the include.xml of the extension but doesnāt work. plus, i have <compilerflag value="-F../frameworks/"/> in the build.xml, where .framework and .bundle files are.
I use a .bundle in an Mopub extension, all I had to do is manually adding the file in the Ressources folder in xcode. Didnāt find anyway to do it automaticaly with project.xml so youāll have to do it every time you use update.
i donāt have a assets folder in the extension ( the idea is to set something in the extension that would make available for the project that use it, like it does with .framework for example )
just for reference, even if you include the .bundle file in the assets folder in the final project, still doesnāt work. it must be drag and drop on Resources in xCode.
My ressources files needs to be in the Resources folder, if I put them in assets they are in Resources/atssets , so the native lib iām using doesnāt find its resources . In my case I could change the lib source code to change the path used, but there is other extension where you canāt change sources.
Iām currently trying to do the changes the xcodeproj template and lime tools need so that the file in Resources and Classes folder are added to the project when using update, but I donāt know how ressources files ID work and get a corrupted .xcodeprojā¦ Why would someone use such a complicated format to store project structure >.<
I know, itās ridiculous. I tried doing the same for the āResourcesā folder, but I think I canāt let files copy to the āResourcesā directory (maybe it doesnāt like Resources/Resources?) and instead these need to be manually added, one file at a time, to the generated Xcode project
This is tough, though, because sometimes it seems like it treats certain things as localization strings, and therefore generates other code for itā¦ itās a little bit of a nightmare, but itās probably not impossible