Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

All mutations hadn't been executed after internet connection type change #108

Closed
DeMoss15 opened this issue Jan 30, 2019 · 11 comments
Closed

All mutations hadn't been executed after internet connection type change #108

DeMoss15 opened this issue Jan 30, 2019 · 11 comments
Assignees
@scb01
Labels
bug Something isn't working closing-soon pending-response Issue is pending response from the issue requestor

Comments

@DeMoss15
Copy link

SDK version: 2.11.0
AppSync version: 2.7.6

It's hard to reproduce this issue.
Steps to reproduce looks like:
execute few mutations -> wait about 15 min -> switch internet connection -> mutations doesn't work
Logs looks like something wrong with queue or AppSyncOfflineMutationManager

Log of creating mutation and adding in to queue here:
SWITCH INTERNET CONNECTION ISSUE.txt
@scb01 scb01 self-assigned this Jan 30, 2019
@scb01 scb01 added AppSync question General question labels Jan 30, 2019
@scb01
Copy link
Contributor

scb01 commented Jan 30, 2019

@DeMoss15
I see this repeated in the log each time the Mutation processor is triggered to start executing mutations off the queue

2019-01-30 11:46:13.100 5193-5258/com.moja V/AppSyncOfflineMutationManager: Thread:[7687]: Internet wasn't available. Exiting

It looks like the device has not gotten back on the network. When the mutation processor is triggered, it checks to ensure that there is network connectivity (see link below for where the network check is made) before starting to process mutations. If there is no network connectivity, the processing is stopped. The mutation processor is triggered periodically by the SDK to ensure that it doesn't get stuck, which is why we see multiple instances of "Internet wasn't available" message in the log.

aws-mobile-appsync-sdk-android/aws-android-sdk-appsync/src/main/java/com/amazonaws/mobileconnectors/appsync/AppSyncOfflineMutationManager.java

Line 173 in 22dc07c

if (info != null && !info.isConnected()) {

I have seen this happen in my local testing on simulators, but not on real devices. In the case of simulators, restarting the simulator usually fixes the issue.

Are you facing this issue on simulators or on real devices?

@scb01 scb01 added the pending-response Issue is pending response from the issue requestor label Jan 30, 2019
@DeMoss15
Copy link
Author

DeMoss15 commented Jan 30, 2019 •
edited

Our QA specialist got this issue on a real device three times.
First time he used proxy to emulate bade internet connection, second and third times he used wi-fi without proxy connection.
In all cases, while he was trying to execute mutations, Internet connection was available (he checked it in browser and other applications). But mutations didn't work.
First two times app restart helped. But third time only cache cleaning helped.
Logs we caught I've attached to the issue

@scb01
Copy link
Contributor

scb01 commented Jan 30, 2019

@DeMoss15

Thanks for the context. In the log you have attached, I don't see any mutation being executed at all. Every time the mutation processor is triggered, it exits immediately.

 2019-01-30 11:44:23.003 5193-5258/com.moja V/AppSyncOfflineMutationManager: Thread:[7687]: Internet wasn't available. Exiting
 2019-01-30 11:44:23.425 5193-5258/com.moja V/AppSyncOfflineMutationManager: Thread:[7687]: Internet wasn't available. Exiting
 2019-01-30 11:44:33.013 5193-5258/com.moja V/AppSyncOfflineMutationManager: Thread:[7687]: Internet wasn't available. Exiting
 2019-01-30 11:44:43.015 5193-5258/com.moja V/AppSyncOfflineMutationManager: Thread:[7687]: Internet wasn't available. Exiting
 2019-01-30 11:44:53.023 5193-5258/com.moja V/AppSyncOfflineMutationManager: Thread:[7687]: Internet wasn't available. Exiting
 2019-01-30 11:45:03.034 5193-5258/com.moja V/AppSyncOfflineMutationManager: Thread:[7687]: Internet wasn't available. Exiting
 2019-01-30 11:45:13.043 5193-5258/com.moja V/AppSyncOfflineMutationManager: Thread:[7687]: Internet wasn't available. Exiting
 2019-01-30 11:45:23.054 5193-5258/com.moja V/AppSyncOfflineMutationManager: Thread:[7687]: Internet wasn't available. Exiting
 2019-01-30 11:45:33.064 5193-5258/com.moja V/AppSyncOfflineMutationManager: Thread:[7687]: Internet wasn't available. Exiting
 2019-01-30 11:45:43.074 5193-5258/com.moja V/AppSyncOfflineMutationManager: Thread:[7687]: Internet wasn't available. Exiting
 2019-01-30 11:45:53.083 5193-5258/com.moja V/AppSyncOfflineMutationManager: Thread:[7687]: Internet wasn't available. Exiting
 2019-01-30 11:46:03.092 5193-5258/com.moja V/AppSyncOfflineMutationManager: Thread:[7687]: Internet wasn't available. Exiting
 2019-01-30 11:46:13.100 5193-5258/com.moja V/AppSyncOfflineMutationManager: Thread:[7687]: Internet wasn't available. Exiting

The logs you've attached only span for a couple of minutes. Could you perhaps have the QA engineer capture the logs for the entire duration (You mention 15 minutes) and attach them here? I can look through that to see if that provides any insights.

@DeMoss15
Copy link
Author

DeMoss15 commented Feb 8, 2019 •
edited

@cbommas Sorry for long pause. It took a lot of time and efforts to catch this logs.
Here it is:
2019-02-08T15_59_19.177+02_00.txt

@stale stale bot removed the closing-soon label Feb 8, 2019
@ukevgen
Copy link

ukevgen commented Feb 12, 2019

@cbommas any updates?

@lexmakali
Copy link

lexmakali commented Feb 13, 2019 •
edited

@ukevgen Sorry for the delayed response.

@DeMoss15 Thank you for the detailed response. I scrolled through the logs and found that the mutations are canceled. I find several
occurrences of the following event in the logs. Do you explicitly cancel the mutation based on any condition?

02-08 16:00:33.492  2511  3142 V AppSyncOfflineMutationManager: Thread:[3215]: Handling cancellation for mutation [com.moja.ba@b9f6eaa]
02-08 16:00:33.492  2511  3142 V AppSyncOfflineMutationManager: Thread:[3215]: Mutation being canceled is the one currently in progress. Handling it

@DeMoss15
Copy link
Author

DeMoss15 commented Feb 14, 2019 •
edited

@cbommas
@kvasukib Yes. We are cancelling mutation when it needed. But it doesn't matters

Please pay your attention for this log:
FROM EXECUTED MUTATION TO FAIL.txt

Let's look at it closer:

Here we can see the last executed mutation:

02-08 16:17:14.983  2511  4668 V AppSyncOfflineMutationInterceptor: Thread:[3340]: Processing mutation.
02-08 16:17:14.983  2511  4668 V AppSyncOfflineMutationInterceptor: Thread:[3340]: First, checking if it is a retry of mutation that encountered a conflict.
02-08 16:17:14.983  2511  4668 V AppSyncOfflineMutationInterceptor: Thread:[3340]:Nope, hasn't encountered  conflict
02-08 16:17:14.985  2511  4668 V AppSyncOfflineMutationManager: Thread:[3340]:  Added mutation[02918de8-1789-489b-91e9-3e85b32741fb] to inMemory Queue
02-08 16:17:14.985  2511  4668 V S3ObjectManagerImplementation: Thread:[3340]: Looking at Key [buyerStorefrontId] of type [j]
02-08 16:17:14.985  2511  4668 V S3ObjectManagerImplementation: Thread:[3340]: Looking at Key [sellerStorefrontId] of type [j]
02-08 16:17:14.985  2511  4668 V S3ObjectManagerImplementation: Thread:[3340]: Looking at Key [withShipping] of type [Boolean]
02-08 16:17:14.985  2511  4668 V S3ObjectManagerImplementation: Thread:[3340]: Looking at Key [shippingAddress] of type [String]
02-08 16:17:14.989  2511  4668 V PersistentOfflineMutationManager: Thread:[3340]:addPersistentMutationObject: Adding mutation[02918de8-1789-489b-91e9-3e85b32741fb]: d 
02-08 16:17:14.989  2511  4668 V PersistentOfflineMutationManager: {"query":"mutation Checkout($buyerStorefrontId: StorefrontId, $sellerStorefrontId: StorefrontId!, $withShipping: Boolean!, $shippingAddress: String, $status: OrderStatus) {  checkout(buyerStorefrontId: $buyerStorefrontId, sellerStorefrontId: $sellerStorefrontId, withShipping: $withShipping, shippingAddress: $shippingAddress, status: $status) {    __typename    ...CheckoutRemote  }}fragment ItemRemote on Item {  __typename  userId  createdAt  updatedAt  variations {    __typename    ...ItemVariation  }  title  categories {    __typename    ...ItemCategory  }  photos {    __typename    ...ItemPhotoRemote  }  description  available  version  author {    __typename    ...StorefrontProfileRemote  }}fragment ItemVariation on ItemVariation {  __typename  id  title  price  photos {    __typename    ...ItemPhotoRemote  }  available  shippingAvailable  negotiable}fragment ItemCategory on ItemCategory {  __typename  id  name}fragment ItemPhotoRemote on ItemPhoto {  __typename  position  image}fragment CheckoutRemote on Order {  __typename  orderId  userId  storefrontId  buyer {    __typename    ...UserProfileRemote  }  buyerStorefront {    __typename    ...StorefrontProfileRemote  }  buyerType  createdAt  updatedAt  finalPrice  totalPrice  shippingAddress  comment  orderItems {    __typename    ...OrderItemRemote  }  withShipping  status}fragment OrderItemRemote on OrderItem {  __typename  userId  item {    __typename    ...ItemRemote  }  quantity  createdAt  updatedAt  variationId}fragment UserProfileRemote on UserProfile {  __typename  userId  name  street  city  about  profileImage  coverImage  version}fragment StorefrontProfileRemote on StorefrontProfile {  __typename  about  city  coverImage  createdAt  name  offeringDescription  profileImage  shippingDescription  street  fromTrustedNetwork  updatedAt  userId  version}","variables":{"buyerStorefrontId":{"userId":"d730091d-162b-4d1c-9511-4eeaf88c17cd","createdAt":"2019-02-07T16:45:19.814Z"},"sellerStorefrontId":{"userId":"b8f336ba-dd1d-4b85-ad5d-a920c52a6daa","createdAt":"2019-02-08T07:26:23.853Z"},"withShipping":true,"shippingAddress":"We Have, Thanks For, Ghana"}}
02-08 16:17:14.999  2511  4668 V AppSyncOfflineMutationManager: Thread:[3340]: Added mutation[02918de8-1789-489b-91e9-3e85b32741fb] to Persistent Queue. No S3 Objects found
02-08 16:17:15.000  2511  4668 V AppSyncOfflineMutationManager: Thread:[3340]: Created both in-memory and persistent records. Now going to signal queue handler.
02-08 16:17:15.000  2511  3001 V QueueUpdateHandler: Thread:[3169]: Got message to take action on the mutation queue.
02-08 16:17:15.000  2511  3001 V QueueUpdateHandler: Thread:[3169]: Got message to process next mutation if one exists.
02-08 16:17:15.001  2511  3001 V AppSyncOfflineMutationManager: Thread:[3169]:Persistent mutations queue is EMPTY!. Will check inMemory Queue next
02-08 16:17:15.001  2511  3001 V QueueUpdateHandler: Thread:[3169]: Setting mutationInProgress as true.
02-08 16:17:15.001  2511  3001 V AppSyncOfflineMutationManager: Thread:[3169]: Processing next from in Memory queue
02-08 16:17:15.001  2511  3001 V InMemoryOfflineMutationManager: Thread:[3169]:Executing mutation [02918de8-1789-489b-91e9-3e85b32741fb]
02-08 16:17:15.001  2511  3001 V InMemoryOfflineMutationObject: Thread:[3169]: Executing mutation by proceeding with the chain.
02-08 16:17:15.001  2511  3001 V S3ObjectManagerImplementation: Thread:[3169]: Looking at Key [buyerStorefrontId] of type [j]
02-08 16:17:15.001  2511  3001 V S3ObjectManagerImplementation: Thread:[3169]: Looking at Key [sellerStorefrontId] of type [j]
02-08 16:17:15.001  2511  3001 V S3ObjectManagerImplementation: Thread:[3169]: Looking at Key [withShipping] of type [Boolean]
02-08 16:17:15.002  2511  3001 V S3ObjectManagerImplementation: Thread:[3169]: Looking at Key [shippingAddress] of type [String]
02-08 16:17:15.002  2511  3001 V AppSyncComplexObjectsInterceptor: Thread:[3169]: No s3 Objects found. Proceeding with the chain
02-08 16:17:15.003  2511  5056 V InterceptorCallback: Thread:[3353]: onFetch()
02-08 16:17:15.005  2511  5066 D RetryInterceptor: Retry Interceptor called
02-08 16:17:15.005  2511  5066 D AppSyncSigV4SignerInterceptor: Signer Interceptor called
02-08 16:17:15.974  2511  5066 I RetryInterceptor: Returning network response: success
02-08 16:17:16.087  2511  5066 V InterceptorCallback: Thread:[3361]: onResponse()
02-08 16:17:16.089  2511  5066 V AppSyncOfflineMutationInterceptor: Thread:[3361]: Dispose called for mutation [com.moja.d@600d3d].
02-08 16:17:16.089  2511  5066 V AppSyncOfflineMutationManager: Thread:[3361]: Handling cancellation for mutation [com.moja.d@600d3d]
02-08 16:17:16.089  2511  5066 V AppSyncOfflineMutationManager: Thread:[3361]: Mutation being canceled is the one currently in progress. Handling it 
02-08 16:17:16.089  2511  5066 V PersistentOfflineMutationManager: Thread:[3361]:Removing mutation [02918de8-1789-489b-91e9-3e85b32741fb] from persistent store
02-08 16:17:16.093  2511  5059 D RetryInterceptor: Retry Interceptor called
02-08 16:17:16.093  2511  5059 D AppSyncSigV4SignerInterceptor: Signer Interceptor called
02-08 16:17:16.105  2511  5066 V QueueUpdateHandler: Thread:[3361]: Setting mutationInProgress as false.
02-08 16:17:16.105  2511  5066 V AppSyncOfflineMutationInterceptor: Dispose called
02-08 16:17:16.105  2511  5066 V PersistentOfflineMutationManager: Thread:[3361]:Removing mutation [02918de8-1789-489b-91e9-3e85b32741fb] from persistent store
02-08 16:17:16.106  2511  5066 V QueueUpdateHandler: Thread:[3361]: Setting mutationInProgress as false.
02-08 16:17:16.106  2511  5066 D InterceptorCallback: Thread:[3361]: onCompleted()
02-08 16:17:16.106  2511  3001 V QueueUpdateHandler: Thread:[3169]: Got message to take action on the mutation queue.
02-08 16:17:16.106  2511  3001 V QueueUpdateHandler: Thread:[3169]: Got message to process next mutation if one exists.
02-08 16:17:16.107  2511  3001 V AppSyncOfflineMutationManager: Thread:[3169]:Persistent mutations queue is EMPTY!. Will check inMemory Queue next
02-08 16:17:16.107  2511  3001 V AppSyncOfflineMutationManager: Thread:[3169]: In Memory mutations queue was EMPTY!. Nothing to process, exiting

than we have a log of internet connection status change:

02-08 16:30:06.111  2511  3001 V QueueUpdateHandler: Thread:[3169]: Got message to take action on the mutation queue.
02-08 16:30:06.111  2511  3001 V QueueUpdateHandler: Thread:[3169]: Got message to process next mutation if one exists.
02-08 16:30:06.112  2511  3001 V AppSyncOfflineMutationManager: Thread:[3169]:Persistent mutations queue is EMPTY!. Will check inMemory Queue next
02-08 16:30:06.112  2511  3001 V AppSyncOfflineMutationManager: Thread:[3169]: In Memory mutations queue was EMPTY!. Nothing to process, exiting
02-08 16:31:31.164  2511  3000 D AppSyncOfflineMutationManager: Thread:[3168]: Internet DISCONNECTED.
02-08 16:31:31.322  2511  3000 D AWSAppSyncDeltaSync: Delta Sync: Network Down detected.
02-08 16:31:32.831  2511  3001 V AppSyncOfflineMutationInterceptor: Thread:[3169]: processing Mutations
02-08 16:31:32.831  2511  3001 V QueueUpdateHandler: Thread:[3169]: Got message to take action on the mutation queue.
02-08 16:31:32.831  2511  3001 V QueueUpdateHandler: Thread:[3169]: Got message to process next mutation if one exists.
02-08 16:31:32.831  2511  3001 V AppSyncOfflineMutationManager: Thread:[3169]: Internet wasn't available. Exiting

and here is the first failed mutation:

02-08 17:33:42.341  2511  6468 V AppSyncOfflineMutationManager: Thread:[3409]:  Added mutation[5543e750-6367-4d2f-92e3-7fa7a4929faf] to inMemory Queue
02-08 17:33:42.342  2511  6468 V S3ObjectManagerImplementation: Thread:[3409]: Looking at Key [name] of type [String]
02-08 17:33:42.349  2511  6468 V S3ObjectManagerImplementation: Thread:[3409]: Looking at Key [street] of type [String]
02-08 17:33:42.354  2511  6468 V S3ObjectManagerImplementation: Thread:[3409]: Looking at Key [city] of type [String]
02-08 17:33:42.355  2511  6468 V S3ObjectManagerImplementation: Thread:[3409]: Looking at Key [about] of type [String]
02-08 17:33:42.357  2511  6468 V S3ObjectManagerImplementation: Thread:[3409]: Looking at Key [expectedVersion] of type [Integer]
02-08 17:33:42.363  2511  6468 V PersistentOfflineMutationManager: Thread:[3409]:addPersistentMutationObject: Adding mutation[5543e750-6367-4d2f-92e3-7fa7a4929faf]: bc 
02-08 17:33:42.363  2511  6468 V PersistentOfflineMutationManager: {"query":"mutation UpdateProfile($name: String, $street: String, $city: String, $about: String, $profileImage: S3FileInput, $coverImage: S3FileInput, $expectedVersion: Int!) {  updateUserProfile(name: $name, street: $street, city: $city, about: $about, profileImage: $profileImage, coverImage: $coverImage, expectedVersion: $expectedVersion) {    __typename    ...UserProfileRemote  }}fragment UserProfileRemote on UserProfile {  __typename  userId  name  street  city  about  profileImage  coverImage  version}","variables":{"name":"Gleb","street":"We Have","city":"Thanks For","about":"Thanks for the invite but I will not be able to make that work for your company to get e have","expectedVersion":1}}
02-08 17:33:42.456  2511  6468 V AppSyncOfflineMutationManager: Thread:[3409]: Added mutation[5543e750-6367-4d2f-92e3-7fa7a4929faf] to Persistent Queue. No S3 Objects found
02-08 17:33:42.456  2511  6468 V AppSyncOfflineMutationManager: Thread:[3409]: Created both in-memory and persistent records. Now going to signal queue handler.
02-08 17:33:42.457  2511  3001 V QueueUpdateHandler: Thread:[3169]: Got message to take action on the mutation queue.
02-08 17:33:42.457  2511  3001 V QueueUpdateHandler: Thread:[3169]: Got message to process next mutation if one exists.
02-08 17:33:42.457  2511  3001 V AppSyncOfflineMutationManager: Thread:[3169]: Internet wasn't available. Exiting

I think something strange is happening beyond this log:

02-08 17:33:19.789  2511  3001 V QueueUpdateHandler: Thread:[3169]: Got message to process next mutation if one exists.
02-08 17:33:19.790  2511  3001 V AppSyncOfflineMutationManager: Thread:[3169]: Internet wasn't available. Exiting
02-08 17:33:22.802  2511  2511 V PhoneWindow: DecorView setVisiblity: visibility = 0, Parent = ViewRoot{e28e02e com.moja/com.moja.flow.main.MainActivity,ident = 5}, this = DecorView@4800773[MainActivity]
02-08 17:33:22.878  2511  6472 I System.out: port:8888
02-08 17:33:22.927  2511  2511 D Surface : Surface::allocateBuffers(this=0x7bc0e99000)
02-08 17:33:22.948  2511  2595 D Surface : Surface::connect(this=0x7bc0e99000,api=1)
02-08 17:33:23.270  2511  6501 D RetryInterceptor: Retry Interceptor called
02-08 17:33:23.270  2511  6501 D AppSyncSigV4SignerInterceptor: Signer Interceptor called
02-08 17:33:23.384  2511  6472 I System.out: [OkHttp] sendRequest<<
02-08 17:33:23.400  2511  2511 W glide-disk-cach: type=1400 audit(0.0:3690): avc: denied { search } for name="clients" dev="debugfs" ino=44 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:debugfs_ion:s0 tclass=dir permissive=0
02-08 17:33:23.410  2511  2511 W glide-disk-cach: type=1400 audit(0.0:3691): avc: denied { search } for name="clients" dev="debugfs" ino=44 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:debugfs_ion:s0 tclass=dir permissive=0
02-08 17:33:23.746  2511  2511 D CognitoCachingCredentialsProvider: Loading credentials from SharedPreferences
02-08 17:33:23.759  2511  2511 D CognitoCachingCredentialsProvider: Clearing credentials from SharedPreferences
02-08 17:33:23.760  2511  2511 D CognitoCachingCredentialsProvider: Clearing credentials from SharedPreferences
02-08 17:33:23.761  2511  6466 D CognitoCachingCredentialsProvider: Loading credentials from SharedPreferences
02-08 17:33:23.761  2511  6466 D CognitoCachingCredentialsProvider: No valid credentials found in SharedPreferences
02-08 17:33:23.768  2511  6466 I System.out: port:8888
02-08 17:33:23.783  2511  6501 I System.out: port:8888
02-08 17:33:24.262  2511  6466 I System.out: [OkHttp] sendRequest<<
02-08 17:33:24.489  2511  6466 D CognitoCachingCredentialsProvider: Saving credentials to SharedPreferences
02-08 17:33:24.491  2511  6466 D CognitoCachingCredentialsProvider: Saving identity id to SharedPreferences
02-08 17:33:24.564  2511  6466 I System.out: [OkHttp] sendRequest<<
02-08 17:33:24.659  2511  2511 V AppSyncOfflineMutationInterceptor: Dispose called
02-08 17:33:24.661  2511  6501 W RetryInterceptor: Encountered IO Exception making HTTP call [java.io.IOException: Canceled]
02-08 17:33:24.768  2511  6466 D CognitoCachingCredentialsProvider: Saving credentials to SharedPreferences
02-08 17:33:24.942  2511  6500 V AppSyncOfflineMutationInterceptor: Dispose called
02-08 17:33:24.942  2511  6622 V AppSyncOfflineMutationInterceptor: Dispose called
02-08 17:33:24.944  2511  6499 V AppSyncOfflineMutationInterceptor: Dispose called
02-08 17:33:24.962  2511  6625 V AppSyncOfflineMutationInterceptor: Dispose called
02-08 17:33:26.377  2511  6625 V AppSyncOfflineMutationInterceptor: Dispose called
02-08 17:33:26.395  2511  6499 V AppSyncOfflineMutationInterceptor: Dispose called
02-08 17:33:28.791  2511  6501 D RetryInterceptor: Retry Interceptor called
02-08 17:33:28.791  2511  6501 D AppSyncSigV4SignerInterceptor: Signer Interceptor called
02-08 17:33:28.808  2511  6925 D RetryInterceptor: Retry Interceptor called
02-08 17:33:28.809  2511  6925 D AppSyncSigV4SignerInterceptor: Signer Interceptor called
02-08 17:33:29.224  2511  6501 I RetryInterceptor: Returning network response: success
02-08 17:33:29.284  2511  6501 V AppSyncOfflineMutationInterceptor: Dispose called
02-08 17:33:29.578  2511  6925 I RetryInterceptor: Returning network response: success
02-08 17:33:29.636  2511  6925 V AppSyncOfflineMutationInterceptor: Dispose called

Unfortunately, I don't understand what exactly. But it seems next line says that network is OK:

02-08 17:33:29.578  2511  6925 I RetryInterceptor: Returning network response: success

@DeMoss15
Copy link
Author

@cbommas @kvasukib Any updates?

@frankmuellr frankmuellr removed the pending-response Issue is pending response from the issue requestor label Feb 19, 2019
@DeMoss15 DeMoss15 mentioned this issue Feb 21, 2019
Closed
@scb01
Copy link
Contributor

scb01 commented Feb 26, 2019

@ukevgen @DeMoss15

While I wasn't able to reproduce this locally, I made some tweaks to the network checking logic to be more resilient. Can you give the latest version, 2.7.8, a try and see if that resolves the issue?

@scb01 scb01 added bug Something isn't working pending-response Issue is pending response from the issue requestor and removed question General question labels Feb 26, 2019
@DeMoss15
Copy link
Author

DeMoss15 commented Mar 4, 2019

@cbommas
We can't reproduce it anymore. Thank you!

@DeMoss15 DeMoss15 closed this as completed Mar 4, 2019
@asyschikov
Copy link

I am having the same issue:

01-06 12:10:27.059 28290 28309 V AppSyncOfflineMutationInterceptor: Thread:[41618]: processing Mutations
01-06 12:10:27.061 28290 28309 V QueueUpdateHandler: Thread:[41618]: Got message to take action on the mutation queue.
01-06 12:10:27.061 28290 28309 V QueueUpdateHandler: Thread:[41618]: Got message to process next mutation if one exists.
01-06 12:10:27.063  6780  8477 D ConnectivityService: filterNetworkStateForUid() uid: 10131, pid: 28290
01-06 12:10:27.064  6780  8477 D ConnectivityService: filterNetworkStateForUid() uid: 10131, pid: 28290, networkInfo: [type: MOBILE[LTE], state: DISCONNECTED/BLOCKED, reason: (unspecified), extra: (none), failover: false, available: true, roaming: false]
01-06 12:10:27.067 28290 28309 V AppSyncOfflineMutationManager: Thread:[41618]: Internet wasn't available. Exiting

And this keeps going on and on, I am 100% sure that the phone is connected to the internet. One thing I suspect is that maybe Samsung somehow blocked internet access for my app for some security/optimisation reasons, but I can't find any indication of it in the logs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@scb01 scb01

Labels
bug Something isn't working closing-soon pending-response Issue is pending response from the issue requestor
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@asyschikov @scb01 @frankmuellr @lexmakali @ukevgen @DeMoss15