Ian Saultz

Thanks for opening this request @mamouneyya. We'll update here with any new information.

Thanks for opening this issue @sskavthekar. This may have been addressed in v3.6.0. Can you confirm if you're still experiencing this after updating?

## TODO - [ ] Confirm that this change doesn't degrade customer experience pulling Amplify in as a dependency. - Does the buildtool plugin run when a client app builds?...

## Clean build comparison errors and warnings. | Branch | Errors | Warnings | | ----------- | ----------- | ----------- | | `dev-preview` (97a2bac5d6d7d27fc9934a0f5271acd42aa7b6f9) | 0 | 217 | |...

## Clean build time comparison Using `xcodebuild -showBuildTimingSummary` _building Amplify-Package, which includes Amplify + all plugins_ **time in seconds** | Step | `dev-preview` | `chore/lint` | Δ seconds | Δ...

## Client app experience ### UX After pulling in Amplify as a dependency (targeting `chore/lint`), the first client app build generates this popup dialog. Not exactly the most reassuring message...

The linting warnings don't show up in a client app's issue navigator, but they are available in the build logs. It looks like the addition of the `--cache-path` speeds up...

The goal of this is to add SwiftLint as a SPM buildtool plugin that runs when Amplify is built standalone (by developers working on Amplify), but never when Amplify is...

The only alternative I can think of at this point is removing the plugin as part of our CI/CD release process. While that would certainly work, it feels brittle and...

### Failures per test in the last 11 runs | Test | Failures | |---|---| | analytics-integration-test | 8 | | api-integration-test | 1 | | auth-integration-test | 2 |...