amplify-swift
amplify-swift copied to clipboard
aws-amplify
A declarative library for application development using cloud services.
**Describe the bug** I am getting the following subscription errors in my app: `WebsocketDidReceiveMessage - {"id":"0E01CECF-6203-4A2A-8587-F1596834C125","type":"error","payload":{"errors":[{"message":"Validation error of type FieldUndefined: Field 'onCreateDeviceState' in type 'Subscription' is undefined @ 'onCreateDeviceState'"}]}} ConnectionProviderError.jsonParse;...
As noted in this code snippet https://github.com/aws-amplify/amplify-ios/blob/4cb4423a6eb3d46dc0caf4bf55392384b0e4acc8/AmplifyPlugins/Core/AWSPluginsCore/Model/Support/Model+GraphQL.swift#L48-L51 We do not currently support a "cascade save" of a graphql model--fields of type `.collection` must be saved separately from their parent. We...
Is there presently anyway to upload an image to be saved in my S3 bucket with the graphQL mutation or do I still have to do this separately? I would...
### Is your feature request related to a problem? Please describe. In Amplify Android API I can provide Cognito User Pool information via a `CognitoUserPoolsAuthProvider`. While Amplify iOS supports `AuthProviders`...
As part of this PR: https://github.com/aws-amplify/amplify-ios/pull/389 It was brought up that we should be creating our serial queues with the target field. At least two approaches are under consideration 1....
**Is your feature request related to a problem? Please describe.** The document generated with a GraphQL request makes some assumptions about which connections are loaded. It would be very helpful...
**Is your feature request related to a problem? Please describe.** Feature request to utilize the DataStore implementation (even just locally) in multiple instances in an application. Currently internal decisions (like...
It seems the dataStore configuration does not allow which apiName to specify if multiple APIs are configured. _Originally posted by @johnm555 in https://github.com/aws-amplify/amplify-ios/issues/814#issuecomment-713161491_
Current implementation of the model registry is a top level var accessible via top-level un-namespaced methods. Need to encapsulate this in a type, probably `DataStore`.
Per discussion https://github.com/aws-amplify/amplify-ios/pull/134#discussion_r349721831 We should investigate whether we can make the static `AnyModel.schema` property getter fail with a `fatalError("AnyModel.schema is not supported. Use the instance property, which reflects the schema...
Metadata
Owner
Metadata
A declarative library for application development using cloud services.