fetchUserAttributes function cause toomanyrequestexception about amplify-flutter HOT 8 OPEN

@mettamdaica0909

I did. But seems the network inspector can not detect the request in v0.6, it can detect the request in v1+. I think the network inspector can not detect the request that is executed in the native code.

I'm more interested in the amount of requests being sent from your V1 project. It's easiest to grab that info from web if you have that platform enabled in your project. Let us know how many requests you see and we can continue to debug.

It means the lib always performs a network request for the user's information. correct?

Correct. This is by design. You're welcome to cache it yourself, as we will always fetch from remote when you call the API.

btw, can we change the limitation (120 requests per sec) to a higher value?

Where are you seeing this limit?

from amplify-flutter.

Hi @mettamdaica0909, sorry to hear you ran into an issue during migration.

Can you confirm if you're using the Authenticator UI component? Or are you using the Auth category directly?

from amplify-flutter.

I'm using the Auth category directly. I checked both version and seem there's an update for the fetchUserAttributes function.

Ver 0.6.0

@override
  Future<List<AuthUserAttribute>>  #fetchUserAttributes(
      {FetchUserAttributesRequest? request}) async {
    try {
      final List<Map<dynamic, dynamic>>? data =
          (await (_channel.invokeListMethod(
        'fetchUserAttributes',
        <String, dynamic>{
          'data': request != null ? request.serializeAsMap() : {},
        },
      )));
      if (data == null)
        throw AmplifyException(
            AmplifyExceptionMessages.nullReturnedFromMethodChannel);
      return formatFetchAttributesResponse(data);
    } on PlatformException catch (e) {
      throw castAndReturnPlatformException(e);
    }
  }

Ver 1.6.1

Future<List<AuthUserAttribute>> fetchUserAttributes({
    FetchUserAttributesOptions? options,
  }) async {
    final tokens = await stateMachine.getUserPoolTokens();
    final resp = await _cognitoIdp
        .getUser(
          cognito.GetUserRequest(
            accessToken: tokens.accessToken.raw,
          ),
        )
        .result;
    return [
      for (final attributeType in resp.userAttributes)
        attributeType.asAuthUserAttribute,
    ];
  }

My understanding is 1.6.1 version is hitting the server for the attributes via cognito.GetUserRequest. is that correct?

from amplify-flutter.

Hi @mettamdaica0909, that's a correct observation, the implementation has changed between major versions.

In v0.6, we were calling into the native platform libraries to perform the API call. For example, on iOS devices the Amplify Swift library would handle to request through the method channel.

In v1+, we perform the entire fetchUserAttributes() call in Dart using Amplify Flutter's Dart API category.

There is also no cache. Each call to the API will perform a network request. This was also the behavior in V0.6.

As for the error you're seeing, I can not reasonably reproduce it. If I throw fetchUserAttributes() in a loop and call it 100 times, they all succeed. Bumping that number up to 500 I start to see failures. In either case, that amount of calls seems unlikely in a normal app.

I suspect something else is going on. Can you confirm the following:

1. Using a network inspector, how many requests are made before you see this exception?
2. Does this happen on any device/OS?
3. Can you reproduce it on a fresh project? If so, please provide the reproduction steps.

from amplify-flutter.

Hi @Equartey, Thanks for your quick response.

Using a network inspector, how many requests are made before you see this exception?
-> I did. But seems the network inspector can not detect the request in v0.6, it can detect the request in v1+. I think the network inspector can not detect the request that is executed in the native code.

There is also no cache. Each call to the API will perform a network request. This was also the behavior in V0.6.
-> It means the lib always performs a network request for the user's information. correct?

from amplify-flutter.

btw, can we change the limitation (120 requests per sec) to a higher value?

from amplify-flutter.