Tim Schmelter

Results 22 issues of Tim Schmelter

See https://github.com/aws-amplify/aws-sdk-android/issues/1207 for the Android equivalent feature request. --- The `targetingClient`'s `updateEndpoint` flows do not expose the ability to update UserAttributes, which is supported by the Pinpoint [UpdateEndpoint](https://docs.aws.amazon.com/pinpoint/latest/apireference/apps-application-id-endpoints-endpoint-id.html#UpdateEndpoint) operation. These...

feature-request
pinpoint

*Description of changes:* Reorders the steps in the CI/CD release to start CocoaPods earlier. Generally, I tried to normalize the release flow so that documentation proceeds independently from publishing artifacts...

As @Mazyod noted in https://github.com/aws-amplify/aws-sdk-ios/issues/1535, S3 will retire support for path-style URLs in Sep 2020. We need to migrate our SDKs to use virtual-host style URLs. > **Describe the bug**...

feature-request
s3

### Description Testing issue management ### Categories - [ ] Analytics - [ ] API (REST) - [ ] API (GraphQL) - [ ] Auth - [ ] Authenticator -...

*Issue #, if available:* *Description of changes:* By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

As noted in #122, setting up AppSync debugging in a Carthage-based project is challenging. We need to provide some developer documentation around that workflow to make it easier for developers...

good first issue
feature-request
documentation

We need to add additional logging in the AppSync subscription paths, especially around connection & reconnection handling.

feature-request
pending-release

**[Originally filed by @peterfennema on https://github.com/aws-amplify/amplify-cli/issues/840].** **Describe the bug** I use Amplify iOS with GraphQL Transform and Codegen to generate a Swift api for AppSync. In the generated code I...

bug

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...

api
datastore
feature-request
p2

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`.

datastore
feature-request
p4