[FR] Generate :podspec parameter in Podfile using iOSResolver XML?

[camphongdinh]

[REQUIRED] Please fill in the following fields:

• Unity editor version: 2019.4
• External Dependency Manager version: 1.2.165
• Source you installed EDM4U: .unitypackage (.unitypackage or Unity Package Manager)
• Features in External Dependency Manager in use: iOS Resolver (Android Resolver, iOS Resolver, VersionHandler, etc.)
• Plugins SDK in use: Firebase, Ironsource Mediation (Firebase, Admob, Facebook, etc.)
• Platform you are using the Unity editor on: Mac (Mac, Windows, or Linux)

[REQUIRED] Please describe the question here:

Hi, due to the need of using old AdMob version (v7.69), I am trying to modify a released Pod "IronSourceAdMobAdapter" so it can be compatible with a higher version of "IronSourceSDK". I have downloaded and edited "IronSourceAdMobAdapter.podspec.json" as below:

{
  "name": "IronSourceAdMobAdapter",
  "version": "4.3.19.4",
  "summary": "AdMob Adapter",
  "description": "Use this adapter to show AdMob ads",
  "homepage": "http://www.is.com/",
  "license": {
    "type": "Commercial",
    "text": "https://platform.ironsrc.com/partners/terms-and-conditions-new-user"
  },
  "authors": {
    "IronSource": "http://www.is.com/contact/"
  },
  "source": {
    "http": "https://raw.githubusercontent.com/ironsource-mobile/iOS-adapters/master/admob-adapter/4.3.19/ISAdMobAdapter4.3.19.zip"
  },
  "source_files": "ISAdMobAdapter/ISAdMobAdapter.framework/**/*.{h,m}",
  "public_header_files": "ISAdMobAdapter/ISAdMobAdapter.framework/**/*.h",
  "preserve_paths": "ISAdMobAdapter/ISAdMobAdapter.framework",
  "platforms": {
    "ios": "9.0"
  },
  "requires_arc": true,
  "vendored_frameworks": "ISAdMobAdapter/ISAdMobAdapter.framework",
  "dependencies": {
    "IronSourceSDK": [
      "= 7.1.6.1" 
    ],
    "Google-Mobile-Ads-SDK": [
      "= 7.69.0"
    ]
  }
}

Now it comes the tricky part. When I am trying to use "path" in Dependencies.xml , it didn't work as Cocoapods didn't try to get the "http" . However, when changing :path to :podspec in Podfile, it worked.

My question is, how do I generate the :podspec parameters using Dependencies.xml instead of having to edit Podfile manually? I tried as below but it didn't work.

<iosPods>
    <iosPod name="IronSourceAdMobAdapter" podspec="./100/Data/Raw/IronSourceAdMobAdapter.podspec.json">
    </iosPod>
  </iosPods>

Thanks

[a-maurice]

I think what you are looking for is the sources tag, so it would look something like:

<iosPods>
  <iosPod name="IronSourceAdMobAdapter">
    <sources>
      <source>"./100/Data/Raw/IronSourceAdMobAdapter.podspec.json"</source>
    </sources>
  </iosPod>
</iosPods>

For another example, see this sample:

unity-jar-resolver/sample/Assets/ExternalDependencyManager/Editor/SampleDependencies.xml

Lines 82 to 92 in 30b4f92

	<iosPod name="Google-Mobile-Ads-SDK" path="../google-mobile-ads-sdk" version="~> 7.0" bitcodeEnabled="true"
	minTargetSdk="6.0" addToAllTargets="false">
	<!-- Set of source URIs to search for this Cocoapod spec.
	By default Cocoapods will attempt to fetch the pod specs from:
	* $HOME/.cocoapods/repos
	* https://github.com/CocoaPods/Specs
	-->
	<sources>
	<source>https://github.com/CocoaPods/Specs</source>
	</sources>
	</iosPod>

I'm not sure if that will work with a relative path, so you might need the full path. Please give it a try, and let us know if that solves the issue.

[camphongdinh]

Thanks for the suggestion. I have tried using source tag . However, the result is not as expected:

The generated Podfile doesn't include :podspec option. It just leave the pod as empty, while adding some source at the top of the Podfile

source './100/Data/Raw/IronSourceAdMobAdapter.podspec.json'

...
pod 'IronSourceAdmobAdapter'
...

After doing pod install , pod doesn't understand the source

Unable to add a source with url `./100/Data/Raw/....

You can try adding it manually in `/Users/Admin/.cocoapods/repos` or via `pod repo add`

From my understanding, source is used to define a repo , not the podspec itself. To load a local podspec file, the Pod documentation says to use :podspec specifically for this scenario:
https://guides.cocoapods.org/syntax/podfile.html#pod

From a podspec outside a spec repository, for a library without podspec.
If a podspec is available from another source outside of the library’s repository. Consider, for instance, a podspec available via HTTP:

pod 'JSONKit', :podspec => 'https://example.com/JSONKit.podspec'

Is there a way for me to set the :podspec parameter from iOSResolver XML ?

Thanks

[chkuang-g]

Hi @camphongdinh

I actually tried you sample and path actually works. TL;DR; I think you might assume path is a relative path from the Assets folder but it is actually from the root of the project folder. See this doc. If 100/Data/Raw/IronSourceAdMobAdapter.podspec.json is under Assets folder, try to use path="Assets/100/Data/Raw/IronSourceAdMobAdapter.podspec.json" instead.

Here is my experiment that works:

• In an empty Unity project, I created Assets/Editor/TestDependencies.xml

  <dependencies>
    <iosPods>
      <iosPods>
        <iosPod name="IronSourceAdMobAdapter" path="PodSpec/IronSourceAdMobAdapter.podspec.json">
        </iosPod>
      </iosPods>
    </iosPods>
  </dependencies>
  

• Then I created PodSpec/IronSourceAdMobAdapter.podspec.json with the content you gave in the original post. Note that this is relative path from the ROOT of the Unity project.
• Build the project. It generated a Podfile like the following (I was using Unity 2017 BTW)

  target 'Unity-iPhone' do
    pod 'IronSourceAdMobAdapter', :path => '/Users/myusername/Workspace/Unity/EmptyProject/PodSpec/IronSourceAdMobAdapter.podspec.json'
  end
  use_frameworks!
  

  Also the Podfile.lock is like the following:

  - IronSourceAdMobAdapter (4.3.19.4):
    - Google-Mobile-Ads-SDK (= 7.69.0)
    - IronSourceSDK (= 7.1.6.1)
  

Perhaps you can try to verify if your path is correct? Otherwise, could you post the content of your Podfile?

[camphongdinh]

Hi @chkuang-g ,

Yes, the :path seems to work at first glance, and Podfile can generate Pods without errors. However, during testing, the IronSource Mediation didn't find the included AdMobAdapter. After looking around, I found that in the generated Pods.proj, those Pods that were used with :path is only empty Pods. You can open the .xcworkspace project to see the Pods.proj . It will look like this:

Pods.proj:
| -- Development Pods
| ------ IronSourceAdMobAdapter
| ------------- but without ISAdmobAdapter.framework

My assumption is that when using :path , Cocoapods assumes that all files of that Pod is included in the :path , so it doesn't download files from source -> http .

The ISAdmobAdapter.framework is actually inside the ISAdMobAdapter4.3.19.zip , in "source" -> "http":

...
  "source": {
    "http": "https://raw.githubusercontent.com/ironsource-mobile/iOS-adapters/master/admob-adapter/4.3.19/ISAdMobAdapter4.3.19.zip"
  },

When trying with :podspec param, Cocoapods will fetch the podspec information from the IronSourceAdMobAdapter.podspec.json and print out these lines:

Fetching podspec for `IronSourceAdMobAdapter` from `/Volumes/Data/Users/Shared/...../Data/Raw/IronSourceAdMobAdapter.podspec.json`

This resulting a Pods.proj with complete structure:

Pods
| -- Pods
| ----- IronSourceAdMobAdapter
| ---------- Frameworks
| ---------------- ISAdMobAdapter.framework

This is the expected result . Without ISAdMobAdapter.framework , the generated Pod doesn't work.

Please let me know if you need further details. I will get more.

Thanks
Phong

[chkuang-g]

@camphongdinh

I see. Thanks for including extra details.

Seems like neither path and source would work for your case. EDM4U does not support podspec now but I think it should be pretty straightforward to add.

Basically:

• Add "podspec" here.
  ...and hey, that's it. That property should be automatically injected to Podfile here.

I will change this to FR. Feel free to send us a Pull Request and we can include this in the next release sooner. :)

[camphongdinh]

@chkuang-g

Thank you for the fix!

In fact I am not quite familiar with Github Pull Request nor I have experience working with Github yet. Currently I am using the External Dependency Manager v1.2.165 , in which there is iOSResolver v1.2.165.dll . I guess I will be waiting for the next release of iOSResolver to use it then.

Thank you.