https://github.com/google/gtm-session-fetcher/pull/315 deprecates GTMFetcherAuthorizationProtocol in favor of the newer GTMSessionFetcherAuthorizer. The protocols are functionally the same, but invert the required and optional methods. This change helps Swift conformers avoid implementing a selector-based callback, which is awkward. In any case, we retain that conformance as well for convenience.
Additionally, this change allow us to no longer ignore warning while pod lib linting and require us to bump our dependency on gtm-session-fetcher to 2.1.0.
@mdmathias I believe we are now encountering the nullability conflict warnings because of the AppAuth dependency of the new ObjC API test spec. Try changing this to AppAuth/Core.
https://github.com/google/gtm-session-fetcher/pull/315 deprecates
GTMFetcherAuthorizationProtocol
in favor of the newerGTMSessionFetcherAuthorizer
. The protocols are functionally the same, but invert the required and optional methods. This change helps Swift conformers avoid implementing a selector-based callback, which is awkward. In any case, we retain that conformance as well for convenience.Additionally, this change allow us to no longer ignore warning while
pod lib lint
ing and require us to bump our dependency ongtm-session-fetcher
to 2.1.0.