Resource bundles not linked when adding pod dependency to UnityFramework target

[santoshbagadi]

Please fill in the following fields:

Unity editor version: 2019.3.3f
Play Services Resolver version: 1.2.136 (1.2.129+)
Features in Play Services Resolver in use (Android Resolver, iOS Resolver, VersionHandler, etc.): iOS Resolver
Plugins SDK in use (Firebase, Admob, Facebook, etc.): AppLovin MAX Unity Plugin
Platform you are using the Unity editor on (Mac, Windows, or Linux): Mac
Platform you are targeting (iOS, Android, and/or desktop): iOS
Scripting Runtime (Mono, and/or IL2CPP): Mono

Please describe the issue here:

Starting from 2019.3+ Unity has added a new target (UnityFramework) to the exported project and JAR Resolver (starting 1.2.129, Related Issue: #282) always adds the dependencies to this target. This has an unintended side effect of the resource bundles not being linked to the main target. Cocoapods is correctly adding these bundles to the UnityFramework but they are not being linked to the main target.

Adding the pod dependency directly to the Unity-iPhone target fixes this issue, but currently there is no way to specify the target to which the framework needs to be added to JAR Resolver.

Please answer the following, if applicable:

What's the issue repro rate? (eg 100%, 1/5 etc) 100%



It would be great if you could provide the ability to specify the desired target in the Dependencies file under the iosPod tag.

[stewartmiles]

Yeah, sounds like a good idea to expose the Cocoapod target in the Dependencies file. We're happy to take pull requests. The Pod class is populated in IOSXmlDependencies .Read and the Podfile is generated in GenPodfile.

[santoshbagadi]

Cool, I've been trying to set up my environment to get this project running but I'm having some trouble. Is there a writeup on how to setup this project and any suggestions on an IDE to use.

[stewartmiles]

@santoshbagadi I just hack in emacs for source editing TBH, other folks use Mono Develop, Visual Studio for source editing.

The build doesn't really work through an IDE though, you need to build following these instructions:
https://github.com/googlesamples/unity-jar-resolver#building-from-source

[santoshbagadi]

Ohk, thanks! I started editing using Sublime, but wanted to double check that I was not missing something and/or making it harder on myself by not using an IDE.

[stewartmiles]

@santoshbagadi yeah no probs.

[santoshbagadi]

@stewartmiles I noticed that when reading an existing PodFile, right now the resolver is only getting pods within Unity-iPhone target. But they should be read from UnityFramework target as well right? Just wanted to make sure it is a legit bug. If so, I can add a fix in my PR.

[stewartmiles]

@santoshbagadi that does sound like a bug, nice catch.

[stewartmiles]

I guess part of the fun here is regenerating the podfile to make sure pods are added to the correct target they were parsed from.

[santoshbagadi]

Yeah, definitely. I'll update the PR accordingly

[santoshbagadi]

Updated the PR with the necessary changes.