We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
I've followed the ios SDK for AWS Amplify using version with AWSMobileClient.
The IOS app successfully initializes the subscription and it works for about 20 minutes.
After the ios App remains idle for over 20 minutes, the subscription does not get to the following block of code to load the table view cell.
// Update Cache Data try transaction?.write(object: chatData, withKey: matchUser.matchData.chatRoomId!)
self.loadMessages(policy: .returnCacheDataElseFetch)
So loadMessages function never gets called because transaction.write code does not get to the point to get to the next block of code.
It works initially for about 20 minutes, then it stops.
Thanks
The text was updated successfully, but these errors were encountered:
Dupe of #396, tracking there.
Sorry, something went wrong.
Released on 3.1.4.
No branches or pull requests
I've followed the ios SDK for AWS Amplify using version with AWSMobileClient.
The IOS app successfully initializes the subscription and it works for about 20 minutes.
After the ios App remains idle for over 20 minutes, the subscription does not get to the following block of code to load the table view cell.
// Update Cache Data
try transaction?.write(object: chatData, withKey: matchUser.matchData.chatRoomId!)
self.loadMessages(policy: .returnCacheDataElseFetch)
So loadMessages function never gets called because transaction.write code does not get to the point to get to the next block of code.
It works initially for about 20 minutes, then it stops.
Thanks
The text was updated successfully, but these errors were encountered: