visionOS AWSS3StoragePlugin Compilation Issue about amplify-swift

[harsh62]

@LarissaKim Thanks for bringing this issue to our attention. We have a fix ready that is being verified internally. Once deployed, we will update the ticket.

[thisisabhash]

Hello @LarissaKim, We have put in a fix to the visionos-preview branch. Please update/refresh your package dependencies and let us know if you still face any issues.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[LarissaKim]

@harsh62 @thisisabhash I appreciate the prompt update.

I removed the package, cleaned the build folder, restarted Xcode, then re-installed Amplify and AWSS3StoragePlugin.

The errors regarding the missing files has resolved, however, I still can't run the project in the simulator due to the following Command SwiftCompile failed with a nonzero exit code errors (still happens for both visionOS 1.0 and 1.1 set as minimum deployment):

• /Users/REDACTED/Library/Developer/Xcode/DerivedData/REDACTED/SourcePackages/checkouts/amplify-swift/AmplifyPlugins/Storage/Sources/AWSS3StoragePlugin/Support/Internal/Attempt.swift:16:68 Cannot convert value of type '(any Error) -> Void' to closure result type '()'
• /Users/REDACTED/Library/Developer/Xcode/DerivedData/REDACTED/SourcePackages/checkouts/amplify-swift/AmplifyPlugins/Storage/Sources/AWSS3StoragePlugin/Support/Internal/Attempt.swift:32:65 Cannot convert value of type '(any Error) -> Void' to closure result type '()'`

Is AWSPluginsCore a required "plugin", by any chance? I didn't see it mentioned in the documentation.

[harsh62]

@LarissaKim Can you please try resetting your package cache and updating. If you see the linked PR, it has the fix for the error you are seeing.

Xcode, File-->Swift Packages-->Reset Package Caches.

[thisisabhash]

Are you able to see the latest commit bcd7602 in your Xcode like above?
If not, please try the steps mentioned above by @harsh62.

[LarissaKim]

@harsh62 @thisisabhash Ah indeed it was still the old commit. I can confirm bcd7602 has fixed the errors. Thank you!