ory/sdk

Native iOs / Swift client

Opened this issue · 4 comments

wondering639 commented

Preflight checklist

Describe your problem

Please provide client for use on Swift

Describe your ideal solution

Please provide client for use on Swift

Workarounds or alternatives

Please provide client for use on Swift

Version

n/a

Additional Context

No response

aeneasr commented

Looks like there is a generator, not sure how good it is: https://github.com/OpenAPITools/openapi-generator/blob/master/docs/generators/swift5.md

Do you know how to publish Swift packages? Is there a central Swift repository like NPM?

jonct commented

The generator, whatever its merits, is now officially blessed. Apple's video demonstrates adding just-in-time generation directly into one's app project in Xcode.

The Swift Package Manager is largely decentralized, reading source files straight from a git repo. But registering with the Swift Package Index will help surface your official client package for anyone looking for it.

If I can help, let me know. Strong enough on containers and Swift; weak on GitHub CI.

jonct commented

Apple's native Swift based generator works fine, after one adjustment to the API spec (v1.1.39):

  • /self-service/settings has a security entry of "sessionToken" which needs to be changed to "oryAccessToken" to match an available component.

Originally I'd had two problems to resolve, but the second was introduced by my using BBEdit to reflow the JSON. That introduced a number of tab characters inside quoted strings, such as on a line like "<sp>unknown<sp><sp>Cloudflare sometimes returns an empty string." In that case the two adjacent spaces processed into a tab character and would require escaping as \t before Apple's parser would allow it. But that's not the fault of the source document; it was introduced by my external tooling.

github-actions commented

Hello contributors!

I am marking this issue as stale as it has not received any engagement from the community or maintainers for a year. That does not imply that the issue has no merit! If you feel strongly about this issue

  • open a PR referencing and resolving the issue;
  • leave a comment on it and discuss ideas on how you could contribute towards resolving it;
  • leave a comment and describe in detail why this issue is critical for your use case;
  • open a new issue with updated details and a plan for resolving the issue.

Throughout its lifetime, Ory has received over 10.000 issues and PRs. To sustain that growth, we need to prioritize and focus on issues that are important to the community. A good indication of importance, and thus priority, is activity on a topic.

Unfortunately, burnout has become a topic of concern amongst open-source projects.

It can lead to severe personal and health issues as well as opening catastrophic attack vectors.

The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.

If this issue was marked as stale erroneously you can exempt it by adding the backlog label, assigning someone, or setting a milestone for it.

Thank you for your understanding and to anyone who participated in the conversation! And as written above, please do participate in the conversation if this topic is important to you!

Thank you 🙏✌️