mdmathias

Out of curiosity, does removing `:binary => true` succeed?

Also, fWIW, this is the diff between 1.6.1 and 1.6.2. I can't see anything there that would be the cause of this on AppAuth's side. https://github.com/openid/AppAuth-iOS/compare/1.6.1...1.6.2

We will be making and tagging a new release soon that will include a privacy manifest. That should be coming in the next month or so. Please stay tuned!

Hi all. Thank you for the issue and the comments. I appreciate your patience. :) I have begun researching what is needed for the privacy manifest, and will follow up...

@snehalvaishnav28 The screenshots in https://github.com/openid/AppAuth-iOS/pull/822 show that the privacy manifest is bundled with an app built via Swift Package Manager and CocoaPods. Please use the latest release: https://github.com/openid/AppAuth-iOS/releases/tag/1.7.3. The privacy...

I think this has something to do with how AppAuth-iOS uses `[-[NSURL standardizedURL]](https://developer.apple.com/documentation/foundation/nsurl/1411073-standardizedurl?language=objc)` in [`OIDAuthorizationService`](https://github.com/openid/AppAuth-iOS/blob/71cde449f13d453227e687458144bde372d30fc7/Source/AppAuthCore/OIDAuthorizationService.m#L112). It seems like `-[NSURL standardizedURL]` doesn't strip out the trailing `/` and so the equality...

What is the rationale and consequence of this pull request? I don't think we want to suppress warnings, but instead want to fix them.

We currently do not have a timeline for this work. `OIDAuthState` is usable in the context that you mention. [One of the sample apps in the GoogleSignIn-iOS repo](https://github.com/google/GoogleSignIn-iOS/tree/main/Samples/Swift/DaysUntilBirthday) may provide...

In the interest of keeping our issues section clean so that we can prioritize effectively, I'm going to close this issue since it seems that what is at stake here...

Per https://github.com/openid/AppAuth-iOS/issues/764#issuecomment-1622126473, it sounded to me like you were looking for help and were not reporting a bug. Apologies if that was incorrect -- I had some trouble understanding your...