+1
+1
+1, I'm having the same request!
+1
+1
We are closely monitoring the development of Swift Package Manager. We'll update the thread when we have something we can share. Thanks.
+1
+1
I believe Objective-C is still not supported, But has there been any talks about writing a swift version that is linux compatible. It would be really nice to be able to talk to services like DynamoDB using swift on an EC2 without having to use the low level API.
+1
+1
+1
+1
+1
+1
+1
๐
@tdouglas1313 @nzayatz14 @bobhigs @moghtaderi @ahawk66 @sekelj13 @yosuke-matsuda @satyaavasarala @futoase @tdouglas1313 @ilazakis @BrianL3 @medampudi @hervouinc @kochrt @foscomputerservices @alexch2000 @jthomas
I've alternatively released an AWS-SDK written purely in Swift. It also supports Linux and Swift PM.
https://github.com/noppoMan/aws-sdk-swift
Now I using it in our production environment.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
+1
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Please do this
I assume this would be a prerequisite to supporting Swift on Lambda... would be very nice.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
+1 to support swift package manager, it is more stable now
We are closing this request for the time being.
So, although they each have their own tradeoffs, we recommend at this time that developers continue to use either CocoaPods or Carthage as a dependency manager, or rely directly on building the SDK frameworks as part of your app.
@palpatim for many of us the intent isn't to use SPM for iOS but for server side systems on AWS.
I understand that currently this SDK is intended to be used on iOS only and that currently, from what I can tell, it is bound to Obj-C and therefor not capable server-side. On that note, I'm only stating this to voice the needs of many in the Swift community. Many of us hope that some collaboration between the AWS team and the community can spin up towards work on a server-side Swift SDK.
Thanks for the note @rex-remind101. We're investigating the request to make a server-side Swift SDK: please see #1030.
Just to add here, I wanted to write a Swift script that uses AWS stuff. So this would be very useful.
Can we get this added now that there is support for iOS apps in Xcode 11?
@w0mba7
Although we still do not have plans for server-side support, official iOS support makes this a more reasonable option now. I'm reopening this and adding it to our feature request backlog.
Awesome thanks!
+1
I'm surprised it's written in ObjectiveC and not with Swift from the start. But we really need a plain swift library so it can be used in plain linux swift projects. I was hoping I can write my project with swift but looks like I'm stuck with C no :D
@w0mba7
Although we still do not have plans for server-side support, official iOS support makes this a more reasonable option now. I'm reopening this and adding it to our feature request backlog.
The Smoke framework supports server-side Swift for AWS services. Including the Swift package manager. See here: https://github.com/amzn/smoke-aws
+1
+1
+1
+1
+1
Any updates on this?
+1
+1
+1
+1
+1
+1
+1
+1
Any updates?
+1
Hi, any updates on this? SwiftPM is definitely the standard for adding dependencies now so I'd expect AWS' SDK to support this since the demand is pretty high!
Hi @palpatim @royjit, thank you for your hard work on this SDK! Would you be able to clarify when the SwiftPM support is going to be added?
@MaxDesiatov I have not had much of an opportunity to dig into the source code. But I suspect theres some assets that are a blocker for this until swift 5.3 package resources feature.
Now is great time to start then, one could add Package.swift with 5.3 in its header, which would allow testing the package with Xcode 12.
I will echo others by saying this is something we are really looking into and would love to see some early support for this during the Swift 5.3 beta period. If there are any issues then they can be reported to Apple and hopefully fixed before release.
Google already started working on support of binary frameworks distributing via Swift Package Manager: https://github.com/firebase/firebase-ios-sdk/issues/3136
So that might be an example
+1
+1
Maybe enabling SPM support via binary targets may be a nice solution for the start.
Examples:
https://github.com/sparkle-project/Sparkle/pull/1634
https://developer.apple.com/documentation/swift_packages/distributing_binary_frameworks_as_swift_packages
So now that xcode 12 is out along with swift 5.3 can we get this updated?
+1 This would be an awesome addition. Thanks for the work guys. ๐
+1
This is very needed issue ๐
Examples Objective-C projects that did add support for Swift Package Manager:
https://github.com/amplitude/Amplitude-iOS
https://github.com/BranchMetrics/ios-branch-deep-linking-attribution
https://github.com/OneSignal/OneSignal-iOS-SDK
Probably they might be helpful for dev team to add support for Swift PM. Really hope it will be added
I can't believe this issue was opened in 2016 and it hasn't been closed yet.Please just add support for SPM
Swift Package Manager support is a key feature.
It would be an awesome addition ๐
Thanks!
Swift Package Manager support is a key feature.
It would be an awesome addition ๐
Thanks!
At this point I'd say it's a required feature. Cocoapods heavily bloats your repo. We have to pay extra for GitHub LFS because some of our dependencies ended up having files > 100mb (looks angrily at here maps)
Hello hello โณ
May as well just use Soto as it actually seems to be going the direction that the community wants.
+1
+1
Does anyone have a workaround to use this with SPM? I have a private SDK that will be distributed as a SPM lib and I need to have AWSCognitoIdentityProvider as a dependency.
Does anyone have a workaround to use this with SPM? I have a private SDK that will be distributed as a SPM lib and I need to have AWSCognitoIdentityProvider as a dependency.
As @dlbuckley mentioned above, you can use Soto (if you don't mind a wrapper around aws)
Otherwise you could always fork the dependency you need and add SPM support to it yourself.
Hi everyone, thanks for your patience.
We are currently investigating Swift Package Manager support. We have quite a few AWS SDKs so there's a lot of surface area to cover. We are prioritizing SwiftPM support on Amplify, the SDK will be prioritized according to what Amplify consumes first.
That being said, feel free to comment with the SDKs you use and are looking forward to SPM support.
Last but not least, we have no ETA but we're actively working on this and I'll keep this issue updated with the status. Also feel free to follow the progress on the Amplify repo https://github.com/aws-amplify/amplify-ios/issues/90
Hi everyone, thanks for your patience.
We are currently investigating Swift Package Manager support. We have quite a few AWS SDKs so there's a lot of surface area to cover. We are prioritizing SwiftPM support on Amplify, the SDK will be prioritized according to what Amplify consumes first.
That being said, feel free to comment with the SDKs you use and are looking forward to SPM support.
Last but not least, we have no ETA but we're actively working on this and I'll keep this issue updated with the status. Also feel free to follow the progress on the Amplify repo aws-amplify/amplify-ios#90
Great news, looking forward to it. Here are the list of libraries which we are using in our project:
Hi everyone, thanks for your patience.
We are currently investigating Swift Package Manager support. We have quite a few AWS SDKs so there's a lot of surface area to cover. We are prioritizing SwiftPM support on Amplify, the SDK will be prioritized according to what Amplify consumes first.
That being said, feel free to comment with the SDKs you use and are looking forward to SPM support.
Last but not least, we have no ETA but we're actively working on this and I'll keep this issue updated with the status. Also feel free to follow the progress on the Amplify repo aws-amplify/amplify-ios#90
Awesome.
We use AWSCore and AWSS3
@Daemon-Devarshi
AWSCognito
Please note that this SDK has been deprecated for a couple of years and will be removed altogether in December. After that time, we will no longer publish any updates to the Cognito Sync mobile SDK for iOS.
Amplify DataStore is our recommended solution for syncing data across devices, but you can also use the AppSync client
Great news that SPM work is finally starting ๐
That being said, feel free to comment with the SDKs you use and are looking forward to SPM support.
For us we are mostly concerned about AWSCore, AWSCloudwatch and AWSLogs.
We are prioritizing SwiftPM support on Amplify, the SDK will be prioritized according to what Amplify consumes first.
Ugghh, that KPI doesn't make sense to me, but regardless, this Package.swift should have no prior knowledge of what Amplify is or that it even exists.
AWSCore
AWSS3
AWSDynamoDB
~AWSMobileClient~
Most helpful comment
Any updates?