The pub roll is blocked by build failures

[zanderso]

The roll here #156440

Caused failures like https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8734597920760676097/+/u/run_platform_views_scroll_perf_ad_banners__timeline_summary/stdout

[2024-10-08 18:00:22.743431] [STDOUT] stdout:                Resolving dependencies of `Podfile`
[2024-10-08 18:00:22.743457] [STDOUT] stdout:                  CDN: trunk Relative path: CocoaPods-version.yml exists! Returning local because checking is only performed in repo update
[2024-10-08 18:00:22.743485] [STDOUT] stdout:                  CDN: trunk Relative path: all_pods_versions_5_9_a.txt exists! Returning local because checking is only performed in repo update
[2024-10-08 18:00:22.743515] [STDOUT] stdout:                  CDN: trunk Relative path: Specs/5/9/a/Google-Mobile-Ads-SDK/11.2.0/Google-Mobile-Ads-SDK.podspec.json exists! Returning local because checking is only performed in repo update
[2024-10-08 18:00:22.743591] [STDOUT] stdout:                  CDN: trunk Relative path: all_pods_versions_4_2_c.txt exists! Returning local because checking is only performed in repo update
[2024-10-08 18:00:22.743630] [STDOUT] stdout:                  CDN: trunk Relative path: Specs/4/2/c/FlutterMacOS/3.16.0/FlutterMacOS.podspec.json exists! Returning local because checking is only performed in repo update
[2024-10-08 18:00:22.743647] [STDOUT] stdout:                [!] CocoaPods could not find compatible versions for pod "Google-Mobile-Ads-SDK":
[2024-10-08 18:00:22.743695] [STDOUT] stdout:                  In Podfile:
[2024-10-08 18:00:22.743718] [STDOUT] stdout:                    google_mobile_ads (from `.symlinks/plugins/google_mobile_ads/ios`) was resolved to 5.2.0, which depends on
[2024-10-08 18:00:22.743859] [STDOUT] stdout:                      Google-Mobile-Ads-SDK (~> 11.10.0)

[zanderso]

Looks like the pub package roll updated google_mobile_ads from 5.1.0 to 5.2.0: googleads/googleads-mobile-flutter#1182

[zanderso]

cc @bparrishMines @christopherfujino

[stuartmorgan-g]

IIRC we've had issues before with CI machines not running pod repo update regularly. Cocoapods unfortunately uses a machine-level cache that require explicit commands to update, and the resolution is against that cache, so stale machine caches can cause problems like this.

[stuartmorgan-g]

@jmagman Do you remember how this has been addressed before? Did they get manually updated? Or did we have to add ad-hoc calls to repo update to tests?

[jmagman]

Or did we have to add ad-hoc calls to repo update to tests?

Unfortunately yes, that's what we did.

[christopherfujino]

Assigning to myself to investigate, if feasible, maybe the best thing to do would be, from the recipes, whenever we ensure cocoapods is installed, also run a repo update.

[christopherfujino]

Put out https://flutter-review.googlesource.com/c/recipes/+/60340 to fix this. When that lands, we can follow up and delete all pod repo update references from tests.