You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a followup to #413, which was closed nearly a year ago with no timeline or details given.
Since then, one thing that has changed is Cocoapods announced they're in a permanent maintenance mode. SPM has more or less won as the package dependency solution for iOS apps at this point; Cocoapods is for legacy projects. Meanwhile, google-mobile-ads-sdk has now supported SPM for more than 2 1/2 years.
Adding SPM support would require providing a Package.swift somewhere (maybe in this repo!), and also zipped versions of the adapters that place the .xcframework at the root (they're currently within another directory, which SPM doesn't support).
This doesn't seem like a huge lift, and would bring this corner of the Google Ads ecosystem up to modern standards. Any updates on ETA?
The text was updated successfully, but these errors were encountered:
Will just add a further update that since I filed this there's been another Cocoapods announcement. They're beginning a transition to read-only that will be complete in 2026:
This is a followup to #413, which was closed nearly a year ago with no timeline or details given.
Since then, one thing that has changed is Cocoapods announced they're in a permanent maintenance mode. SPM has more or less won as the package dependency solution for iOS apps at this point; Cocoapods is for legacy projects. Meanwhile, google-mobile-ads-sdk has now supported SPM for more than 2 1/2 years.
Adding SPM support would require providing a Package.swift somewhere (maybe in this repo!), and also zipped versions of the adapters that place the
.xcframework
at the root (they're currently within another directory, which SPM doesn't support).This doesn't seem like a huge lift, and would bring this corner of the Google Ads ecosystem up to modern standards. Any updates on ETA?
The text was updated successfully, but these errors were encountered: