amplify-swift icon indicating copy to clipboard operation
amplify-swift copied to clipboard

A declarative library for application development using cloud services.

Results 324 amplify-swift issues
Sort by recently updated
recently updated
newest added

*Issue #, if available:* *Description of changes:* - Fixed integration test for CI/CD - Change the folder structure of Geo to match other plugins - Removed unused files *Check points:...

*Issue #, if available:* *Description of changes:* *Check points: (check or cross out if not relevant)* - [ ] Added new tests to cover change, if needed - [ ]...

*Issue #, if available:* *Description of changes:* *Check points: (check or cross out if not relevant)* - [ ] Added new tests to cover change, if needed - [ ]...

*Issue #, if available:* None *Description of changes:* Add SQLite local persistence layer to save device tracking locations. *Check points: (check or cross out if not relevant)* - [ ]...

### Describe the bug Our iOS app sometimes encounters AuthError.invalidState errors when users are attempting to sign in via Cognito. In particular there has been a spike with the release...

bug
pending-response
auth

### Is your feature request related to a problem? Please describe. The documentation allows for multiple owners of a model, buth the Amplify iOS implementation is lacking this important feature....

datastore
p2

### Describe the bug I've got a scenario in an app I'm creating where 3 objects have nested manyToMany relationships for example: 1 top level object (TestStructure1) has multiple objects...

datastore
p3

### Describe the bug Updating from 1.24.0 to 1.28.1 surfaces compiler error ` Property 'identifier' must be declared public because it matches a requirement in public protocol 'Model'` See https://github.com/aws-amplify/aws-sdk-ios/issues/4327...

datastore

we should mark this API with @discardableResult _Originally posted by @lawmicha in https://github.com/aws-amplify/amplify-ios/pull/2214#discussion_r979064215_

datastore

The macOS tests that are failing should not be blocking this PR since they were failing before and recently enabled in the pipeline. Opening an issue to track this _Originally...

datastore