Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[xcode11-feature] Swift Libraries (CryptoKit and RealityKit) #6239

Open
chamons opened this issue Jun 10, 2019 · 12 comments
Open

[xcode11-feature] Swift Libraries (CryptoKit and RealityKit) #6239

chamons opened this issue Jun 10, 2019 · 12 comments
Labels
enhancement The issue or pull request is an enhancement requires-swift An issue that requires swift support to fix
Milestone

Comments

@chamons
Copy link
Contributor

chamons commented Jun 10, 2019

Both CryptoKit and RealityKit are Swift-only, with no Objective-C binding.

Infrastructure to work on swift is in work but not public currently.

If we wish to support these libraries, we need to figure out what shipping a Swift library binding truly entails.

As a friendly reminder, an issue card is not a guarantee that a certain feature will be done, or done under any particular time frame. Issues allow us to document what features we do and do not have, and give the community a place to provide feedback.

@chamons chamons mentioned this issue Jun 10, 2019
5 tasks
@chamons chamons added the enhancement The issue or pull request is an enhancement label Jun 10, 2019
@chamons chamons added this to the xcode11 milestone Jun 10, 2019
@wjk
Copy link
Contributor

wjk commented Jun 10, 2019

Just a comment, if binding to Swift natively is too difficult (although it should be easier now that the ABI has been fixed), we could always write a Swift library that exposes @objc entrypoints, and then call those from C# instead. Inelegant, but workable.

@softlion
Copy link

softlion commented Oct 1, 2020

Any news on this ? Now that SceneKit is officially out, RealityKit is the way to go. And it's in swift only.

@chamons
Copy link
Contributor Author

chamons commented Jun 21, 2022

Hey folks, while not a full solution the prototype in #15315 might help resolve part of the issue, depending on what APIs you need.

@CastleSoft
Copy link

Any progress on RealityKit ?

https://developer.apple.com/augmented-reality/realitykit/

C# wrappers ?

Thanks

@chamons
Copy link
Contributor Author

chamons commented Jul 25, 2022

There is no current progress on this issue. However, using this prototype you could potentially bind the subset of the API you need yourself.

@jimjams26
Copy link

Has there been any update on this. I have tried to bind RealityKit and have been unsuccessful multiple times. I have been working on this for months due to needing to create a LiDar scanning application with Xamarin. Is there any more news on this? I just need something. Is there anyone out there that has been successful in binding the swift only framework ? I would love to know !
Or can anyone give any tips on how to implement a LiDar scanner in xamarin.
Thanks, Jimbobs

@tipa
Copy link

tipa commented Sep 1, 2023

CryptoKit is now the 3rd library (after StoreKit2 & WidgetKit) that I wanted to use, just to find out it is not supported. Really hope there will be some progress is making Swift-APIs available...

@tipa
Copy link

tipa commented Sep 1, 2023

I just found out that in .NET8, the AesGcm class is using CryptoKit under the hood (dotnet/runtime#29811), maybe the work that has been done there can be used to make CryptoKit available for direct use?

@rolfbjarne
Copy link
Member

I just found out that in .NET8, the AesGcm class is using CryptoKit under the hood (dotnet/runtime#29811), maybe the work that has been done there can be used to make CryptoKit available for direct use?

Not really, in dotnet/runtime this was partially implemented in Swift, by creating C-style functions in Swift that were then consumed from C# using DllImports.

In other words this is all custom, manually written, code. Exposing entire frameworks like this is quite labor intensive, and not feasible with the manpower we have available.

@mlancione
Copy link

Do we know whether Microsoft intends to ever support Swift Libraries? This seems quite critical to supporting the iOS platform going forward.

Xamarin as a company seemed to make it their core mission to supporting all iOS and Android functionality (with same-day OS support as well).

@dalexsoto
Copy link
Member

Yes this is on our radar and we intend to look into this in the future, I do not have a timeline for you just yet but it is something we will be actively looking into.

@mlancione
Copy link

@dalexsoto Thanks for the update. Much appreciated.

@rolfbjarne rolfbjarne added the requires-swift An issue that requires swift support to fix label Jul 3, 2024
@rolfbjarne rolfbjarne modified the milestones: xcode11, Future Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement The issue or pull request is an enhancement requires-swift An issue that requires swift support to fix
Projects
None yet
Development

No branches or pull requests

9 participants