search

awslabs / aws-mobile-appsync-sdk-android

Android SDK for AWS AppSync.
https://docs.amplify.aws/sdk/api/graphql/q/platform/android/
Apache License 2.0
105 stars 58 forks source link

Ability to modify the "keep-alive" in AppSync #368

Closed mkabore closed 2 years ago

mkabore commented 2 years ago

Is your feature request related to a problem? Please describe.

We would like to have some improvements in the AppSync SDK for Android, the purpose being to reduce the data usage in the IoT devices. We are currently using the Android SDK https://github.com/awslabs/aws-mobile-appsync-sdk-android/releases , the last version. In the SDK, we are using AppSync with some mutations so we can sync some data between the devices and the cloud. Although, to keep the connection live , the SDK is automatically exchanging some data with the cloud every 15 seconds. We would like to have in the SDK, the ability to decide the frequency of that exchange, a kind of parameter "keep alive" we can set ourselves, similar to what we have with the aws mqtt sdk.

Describe the solution you'd like Give Access to the parameter "keep-alive" so the developer can decide for himself, the frequency.

Describe alternatives you've considered aws mqtt give access; but i want appsync for different project

Additional context Add any other context or screenshots about the feature request here.

sktimalsina commented 2 years ago

As communicated in separate channel, there are two requests in this issue:

  1. App sync pings every 60s : This is not changeable.
  2. Network pings every 15s : I was not able to observe any such pings when I tried to reproduce this. Could you please provide the stack trace of what method/procedure is being called every 15s. If you are using Android studio, you can do that by using profile tool and check the network profiler.
mkabore commented 2 years ago

We have provided all necessary data through AWS support team and even had a video call last week. So I don't understand why we are closing this ticket.

sktimalsina commented 2 years ago

@mkabore I am sorry for the confusion. All of the information is in separate internal ticket. Since the internal ticket has all the information and history and this one has been open without any updates, I have closed this issue here to avoid duplicate items for tracking same issue. We can reopen this in future if needed.