Skip to content

Conversation

@petea
Copy link
Contributor

@petea petea commented Sep 13, 2022

With the release of GTMAppAuth 1.3.1, we're now building against GTMSessionFetcher 2.1.x by default and need to handle warnings stemming from the deprecation of GTMFetcherAuthorizationProtocol.

@petea petea added this to the 6.2.4 milestone Sep 13, 2022
@petea petea marked this pull request as ready for review September 13, 2022 18:07
Copy link
Collaborator

@mdmathias mdmathias left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we update GTMAppAuth to conform to GTMSessionFetcherAuthorizer so that we don't need to worry about the deprecation of GTMFetcherAuthorizationProtocol?

I guess that change would require a major version release of GTMAppAuth?

@petea
Copy link
Contributor Author

petea commented Sep 13, 2022

Should we update GTMAppAuth to conform to GTMSessionFetcherAuthorizer so that we don't need to worry about the deprecation of GTMFetcherAuthorizationProtocol?

I guess that change would require a major version release of GTMAppAuth?

We should consider this for our next major release of GTMAppAuth. We'll have to decide if we're comfortable dropping support for anything before GTMSessionFetcher 2.1.0.

@petea petea merged commit 8650246 into main Sep 13, 2022
@petea petea deleted the petea-warnings branch September 16, 2022 20:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants