by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    eliasericsson
    @eliasericsson
    That's a little bit concerning
    erisco1
    @erisco1_gitlab
    Having a huge problem with turnaround time for testing Lambda functions (CloudFormation is slow!). Noticed Serverless has a CF bypass just for this (https://serverless.com/framework/docs/providers/aws/cli-reference/deploy-function/). Does Amplify have a solution?
    James Nguyen
    @totaland

    npm install -g @aws-amplify/cli@4.11.0
    npm WARN deprecated graphql-toolkit@0.5.18: Use @graphql-toolkit/* monorepo packages instead. Check https://github.com/ardatan/graphql-toolkit for more details
    npm WARN deprecated core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
    npm WARN @graphql-toolkit/file-loading@0.9.0 requires a peer of graphql@^14.5.8 but none is installed. You must install peer dependencies yourself.
    npm WARN relay-compiler@6.0.0 requires a peer of graphql@^14.2.0 but none is installed. You must install peer dependencies yourself.

    npm ERR! Maximum call stack size exceeded

    npm ERR! A complete log of this run can be found in:
    npm ERR! C:\Users\jnguyen\AppData\Roaming\npm-cache_logs\2020-01-15T04_17_28_278Z-debug.log

    I can't seem to install aws-amplify with npm
    anyone know why?
    Ghost
    @ghost~598a2232d73408ce4f70963e
    James Nguyen
    @totaland
    @kekkler really helpful... not even work
    @kekkler why people this day keep assuming that people didn't hit the google before asking question?
    ouan
    @alebret
    Hello guys, do you have an idea of the date of the next release ?
    PeteLatham-CothamTechnologies
    @PeteLatham-CothamTechnologies
    @totaland I seem to recall something about at least part of the Amplify toolchain needing to be installed under WSL on Windows rather than in the native operating system. I could be getting muddled and that requirement could have gone away now. Is WSL an option to try?
    PeteLatham-CothamTechnologies
    @PeteLatham-CothamTechnologies
    @willrust That doesn't mean nothing's happening with the product, though. There's probably someone covering in the interim and they may even get the role permanently but Amazon likely have a policy of advertising externally regardless. If you look at the changelog for Amplify/CLI you can see they're still making updates to the product.
    Gerald S
    @sorianog
    Is there a running list of broken links between existing AWS Mobile (iOS/Android) docs and Amplify?
    My team and I have been doing AWS Upload work recently and are not prepared for Amplify at this time. I'd also like to know when these AWS docs will be deprecated...
    Dupdroid
    @christodupreez
    I'm looking for help on how to implement pagination using Vue & Appsync. Are there any tutorials published somewhere?
    sid-rxr
    @sid-rxr
    My pinpointfunction and MFALambda keep complaining the runtime parameter of nodejs8.10 is no longer supported for creating or updating AWS Lambda functions. when I try to create a new amplify environment.
    I set the runtime to nodejs10.x on pinpoint-cloudformation-template.json and xxx--cloudformation-template.yml in my codebase, though it resets to nodejs8.10 when I do a npm run push after I add a new amplify environment. How can I ensure that this stays on nodejs10.x?
    orkuva
    @orkuva
    Hi Could someone please tell me where is the documentation for Amplify Andoid SDK to send HTTP POST requests to API Gateway? I am using Cognito User Pools as auth. Unable to find out where there is documentation that tells how to make requests to API Gateway
    Daniel S. Dantas
    @dantasfiles
    @totaland Sometimes if you just run the npm install command twice it works itself out.
    Jared Short
    @ShortJared_twitter
    Hey all, I am getting stuck with a simple Amplify React Authenticator email only signup / login
    Error: Couldn't find the label: Email, in sign up fields according to usernameAttributes!
    const signUpConfig = {
      header: 'Sat Editor',
      hideAllDefaults: true,
      defaultCountryCode: '1',
      signUpFields: [
        {
          label: 'Your Email',
          key: 'email',
          required: true,
          displayOrder: 1,
          type: 'string'
        }
      ]
    };
    const usernameAttributes = 'email';
    
    export default withAuthenticator(App, { signUpConfig, usernameAttributes });
    image.png
    ^ Cognito is also set to require and use email as the username attr
    Oh wow. It uses the label and not the key. Error was telling the truth, just confusing
    Raf
    @Rafcin
    @ShortJared_twitter switch to Firebase at this point if you can. It's not worth the hell after you get past auth
    Redgie Gravador
    @gitRedgieGravador
    hi
    PeteLatham-CothamTechnologies
    @PeteLatham-CothamTechnologies
    @Rafcin out of interest, does Firebase provide out of the box React components and support?
    Raf
    @Rafcin
    I'm not sure. But it's really easy to just make the root components you need. Amplify isn't bad also it just need a lot of work
    Gerald S
    @sorianog
    Anyone here got AWS-iOS experience and know how to message data from an invoker request in its .continue block?
    Gerald S
    @sorianog
    @orkuva Did you get help yet? I've been looking at iOS docs and have been able to find glimpse of that docs on the Amazon side but then had to keep going to the GitHub Amplify docs as well :(
    Lars Corneliussen
    @lcorneliussen
    I'm trying to get Amplify + Cognito + Federated Office 365 / Azure AD login working. Currently stuck with "Invalid login token. Issuer doesn't match providerName". Somehow the JWT ends up with an iss: "https://cognito-idp.us-east-1.amazonaws.com/XYZ" which I suppose shouldn't be prepended with https.// ?
    Would be super happy for any help
    Lars Corneliussen
    @lcorneliussen
    Figured it out. First param to await Auth.federatedSignIn is not the name of the federated identity provider in the Cognito User Pool, but instead the ARN to the pool itself:
    await Auth.federatedSignIn(
    cognito-idp.${config.cognito.REGION}.amazonaws.com/${config.cognito.USER_POOL_ID},
    { token: id_token, expires_at: expires_in }
    );
    Iain Cox
    @Iaincox
    Does anyone have an example of how to call appsync from golang
    Daniel S. Dantas
    @dantasfiles
    AWS asks "What 3 things do you want to see in Amplify this year?" Respond at https://twitter.com/undef_obj/status/1217667714413551617
    Gerald S
    @sorianog
    @dantasfiles Less broken links on https://aws-amplify.github.io/
    Alex Patterson
    @ajonp
    Hello does anyone know all the roles that are required while using Amplify? We are working with a client that will not give us Admin Access and we are hitting a role issue every time we use amplify and then have to put a HD ticket in for more acccess.
    huntecuador
    @huntecuador_twitter
    Hi guys one question whenever I try to add the @searchable directive to type, the createdAt:String does not seem to be indexed by ElasticSearch, so any query with sort:createdAt does not work ;(
    Has anybody else experienced this?
    Raf
    @Rafcin
    @PeteLatham-CothamTechnologies https://react-firebase-js.com/
    Raf
    @Rafcin
    the only thing I will say is Amplify when you have complex projects is good. Firebase is for simpler projects.
    Raf
    @Rafcin
    @ajonp can you describe the issue in more detail
    @ajonp roles aren't required because you can expose your api to public access via IAM, or Apikey. It sounds like you need to allow your role to use specific queries and mutations with inline policies.
    Raf
    @Rafcin
    Also for anyone who's hates Glitter, I made a slack if it helps. Might be easier to work on and get help if people join
    Sean Martin
    @SeanMar97695165_twitter
    Hi guys, who knows how to solve this problem.I encountered a problem when using the aws cloudformation plugin. After writing the configuration, "Failed to create stack: test-1. Reason: Detailed Message: Requires capabilities: [CAPABILITY_AUTO_EXPAND] (Service: AmazonCloudFormation; Status Code: 400; Error Code: InsufficientCapabilitiesException; Request ID: b34897e5-69f4-47db-b054-ca769208a540) "
    Dayton Yap
    @dayton.yap_gitlab
    Hi all. How can I get user's access token using federateSignIn? Currently I'm getting access token 'nil' even though userState is 'SignIn'
    eliasericsson
    @eliasericsson
    @Rafcin I guess that maybe he meant the role assigned to the Amplify CLI user, which needs some roles to create the resources. @ajonp, maybe you can be allowed to run your project in a separate AWS account? At least for a trial, then log all AWS API requests with CloudTrail to see exactly what a custom role would need to be created in the customer account.
    Gerald S
    @sorianog
    @Rafcin Just joined! Thanks for setting it up. I wonder if @AWS-Amplify on Twitter would be able to chime in on your Slack group :)
    PeteLatham-CothamTechnologies
    @PeteLatham-CothamTechnologies
    @Rafcin Thank you!
    praveensambu
    @praveensambu
    @avronyc : did you find any solution for "Connection failed: Buffer is not defined"