SDK file size too big

[josh....@buzzfeed.com]

As noted in the changelog, the file size of the GMA SDK for iOS is now much larger than before, due to a change in the build configuration.

This is causing problems with our project.  The new binary file size is just over 100MB, which is the limit GitHub places on files.  So I can't check my project in, after updating.  

Can you revert the build configuration so we can go back to having somewhat reasonable file sizes for the frameworks?

Thanks,

Josh Walker

BuzzFeed

[mobileadssdk-a...@google.com]

Hi Josh,

Could you confirm if you are including the SDK when you are pushing to your Github repository? If so, you might consider ignoring the Mobile Ads SDK framework when pushing by adding it in your Git ignore file (please refer to this link for reference). It should be enough to push just your Xcode project and the Podfile in your Github repository, similar on how we manage our sample apps in this repository.

Regards,

Steven Balan

Mobile Ads SDK Team

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

--

---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.
To post to this group, send email to google-admob-ads-sdk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/09e42121-33da-4870-b34a-42ad196e40a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[josh....@buzzfeed.com]

Hi Steven,

Thank you for your response, however our current workflow is to not use gitignore and to check Cocoapods builds into our git repo.  This is consistent with what Cocoapods recommends https://guides.cocoapods.org/using/using-cocoapods#should-i-check-the-pods-directory-into-source-control

Thanks,

Josh Walker

BuzzFeed

[mobileadssdk-a...@google.com]

Hi Josh,

I will check this with the rest of the team and I will update you for any feedback. 

Regards,

Steven Balan

Mobile Ads SDK Team

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads-sdk+unsubscrib...@googlegroups.com.

To post to this group, send email to google-admob-ads-sdk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/09e42121-33da-4870-b34a-42ad196e40a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.
To post to this group, send email to google-admob-ads-sdk@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/0f4e3a36-6c6e-4ae2-8f80-9e961b3ab1ed%40googlegroups.com.

[Steven Peterson]

Steven,

Is there an update on this? I'm encountering this too and the SDK has essentially broken my development process. As Josh mentioned, checking dependencies into source control is the recommended workflow, and because the latest version of Firebase requires the new SDK as a dependency, I'm stuck.

Thanks,

Steven

[mobileadssdk-a...@google.com]

Hi Steven, 

My name is Jon and I'm a support engineer on the Mobile Ads team. From the link provided https://guides.cocoapods.org/using/using-cocoapods#should-i-check-the-pods-directory-into-source-control, 

it does not look like Pods recommends checking in the pods to source control, rather that there are pros and cons to both approaches. It specifically highlights space savings as a benefit to leaving pods out of source control, so that would be my suggestion. If you are attempting to use a continuous integration product, you should be able to include a shell script that installs the pods after every checkout. Thanks so much. 

Jon

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/0f4e3a36-6c6e-4ae2-8f80-9e961b3ab1ed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.
To post to this group, send email to google-admob-ads-sdk@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/98c24fc3-ac5d-4a00-b541-5775587f258c%40googlegroups.com.

[Steven Peterson]

Jon,

This is what it says: “We recommend that you keep the Pods directory under source control, and don't add it to your .gitignore.” I’ve been following this advice for many years, and I’m not the only one. Every big company I’ve worked at has adhered to this approach.

It seems unreasonable to me that Google would require everyone who is using the recommended approach to modify our workflows solely to accommodate AdMob. Repeatability of builds is the reason why many of us check in our dependencies, since we have no control over third parties, and if we need to go back to troubleshoot a specific release, there is no guarantee that the dependencies will still be available.

I’m interpreting your response as an indication that Google has no intention of resolving this, and that all users of your SDK will have to change their setups. Is that correct?

Thanks,
Steven

[mobileadssdk-a...@google.com]

Hey I'm sorry Steven I did miss that line, but what I meant was that it doesn't look like removing your pods from source control should have any adverse affects according to their documentation, and that they specifically mention repo size as one of the reasons to consider leaving them out. I understand you lose the ability to restore specific versions if they are removed from Pods, but Github recommends against checking in dependencies anyway. https://help.github.com/articles/what-is-my-disk-quota/. So either way you're violating someone's recommendation. 

Unfortunately, Google does not currently have any plans to reduce the size of the Mobile Ads SDK. 

What I would suggest is removing the pods from your git repo and making backups of the project which do include the dependencies on something outside of Github for every release that you make, perhaps as part of a deployment pipeline. 

In the mean time, I've passed your concerns on to our engineering team so they know we have users who are unhappy about the size of the SDK breaking their development flow. Please let me know if there's anything else I can answer for you. Thanks.

Jon

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

--

---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.
To post to this group, send email to google-admob-ads-sdk@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/28332052-7043-40d9-b138-6a998092ce82%40googlegroups.com.