Closed colinhumber closed 3 years ago
Just as a note, not asking specifically about macOS support, just that the internal dependency on UICKeychainStore be updated to remove any calls to unavailable APIs.
@colinhumber Thank you for reporting to us. I have tagged this as a feature request and added to the backlog for prioritization.
@kvasukib I would be happy to work on this. After checking the custom prefixed UICKeychainStore
code in both AWSCore
and AWSCognitoAuth
, the offending methods are already wrapped in an #if TARGET_OS_IOS
. These methods are also not called anywhere in the AWS code. In Xcode 11 there's also a new TARGET_OS_UIKITFORMAC
macro available to deal with these unavailable APIs. Of course, that can't be included until the public release, but this should be a pretty trivial change, as far as I can tell to get this working for both iOS targets and iPad apps deployed to macOS.
Hi, Any other news regarding this ?
Hoping for updates here. Is there a branch with this working?
@kvasukib Any updates on this? We're probably about a month or less from release.
@colinhumber Did you work around this somehow?
Bumping for updates
I've been waiting to get an official update, but in the meantime I have this on a branch. I might just do a PR since there's been no word as to whether this will be internally handled.
https://github.com/colinhumber/aws-sdk-ios/tree/uikit-for-mac
When we get the updated pod which is also support macCatalyst ?
Another vote for an updated pod please with support for macCatalyst
Please update
AWS for iOS still doesn't work out of the box on Catalyst because of these errors. Given how small the required change is and with Xcode 11 being released now, wouldn't it make sense to release an update?
Please update
yes please ;)
Please make this update to the pod file so that we can work with the catalyst
Bumping for updates, thanks!
Has this been resolved?
It will not work if we are using Cognito, because it includes compiled .a lib.
Another problem is SFAuthetnicationSession which is not available on Catalyst.
Please fix this.
I need a fix for this if possible. Thanks
I tried using @colinhumber 's uikit-for-mac branch, but my project needs AWSIoT, and I am running into another error when trying to build for macOS Catalyst in AWSSRWebSocket.m - the import
please fix
Now the only reason my app doesn't work on mac. PLEASE FIX ASAP AWS!!!
Any luck on this?
Going to keep asking here as this is important to us.
@nikhil-dabhade any update on this?
@royjit any update on this? Just won't build on Xcode ATM.
Please update!
Any updates?
This is blocking us from working on our Mac Catalyst app. Please update ASAP.
Why is AWS so against any sort of macOS support...since 2010 it makes cross platform Apple applications impossible
There’s nothing worse than investing your time writing against a library only to find it gets you 99% of the way there but not that last 1%. Re-wrote my app to use API calls at great expense. Won’t waste my time on an Amazon maintained library again.
can i at least get the brand of wax that jeff bezos uses for his head? thnx in advance
Any updates? I really need this update.
Sadly I don't think AWS will help us, instead, we will wait for macOS Big Sur that allows iOS apps to work directly.
@royjit @nikhil-dabhade can you please provide an update on this? Are we ever going to get this or not? So we know how to move forward.
Hi @msuzoagu, we're currently evaluating supporting other platforms, such as MacOS. Our primary goal is to add support for other platforms in Amplify iOS , we're still not sure if we'll be able to cover all the SDKs, since there's quite a bit of area to cover and also legacy code. Regardless I'll keep you posted.
In case you're working on new projects, I suggest you check if Amplify is a good fit for you.
@drochetti : Thank you for sharing the primary goal on Amplify iOS. Yeah, it is better to migrate there, but it might take time. Can you help me to clarify several things?
Many thanks, Quang.
@drochetti : Thank you for sharing the primary goal on Amplify iOS. Yeah, it is better to migrate there, but it might take time. Can you help me to clarify several things?
- Does Amplify iOS support Mac Catalyst at the moment?
- And is there any plan that AWS SDK iOS supports Mac Catalyst in the near future too? If not, I might migrate to Amplify iOS as soon as possible.
Many thanks, Quang.
It's very unlikely we will add support to anything other than iOS to the SDKs, but we are evaluating and working on a plan to support more platforms on Amplify. An issues was created recently asking for macOS support, feel free to +1 it and also leave comments about your needs. The more info we have about developers' needs, the better: https://github.com/aws-amplify/amplify-ios/issues/1124
@drochetti If you're cool with it, I'm going to close this issue as you mentioned there's a feature request already set that's a better place for people to +1.
Thanks @colinhumber, it would be great to consolidate feedback on that issue rather than splitting the conversation.
ditto for this request. Catalyst open up the possibility of using UIKit code in macOS. However, with Swift UI and Apple Multiplatform projects it is possible to write "pure" UIs that can easily run on macOS. We have a project that requires macOS support and we hit this early snag of not able to use graphql with Amplify and AppSync. Note that Apollo code compiles and run on macOS in multiplatform projects targeting macOS >= 11.0. One thing I have not tried is importing the source of AWSAppSync and Amplify not the xcframeworks.
@drochetti, you misunderstand the request. Mac Catalyst is not the same as macOS. To add this platform you need much less steps, it's almost like iOS simulator running on mac.
Describe the bug With the new UIKit for Mac support in Xcode 11 and macOS Catalina, this library is currently unable to compile the My Mac target. There are unavailable keychain APIs preventing the SDK from being compiled.
To Reproduce
Which AWS service(s) are affected?
Expected behavior The SDK should compile
Screenshots
Environment(please complete the following information):
Device Information (please complete the following information):
Additional context Add any other context about the problem here.