Closed wrbl606 closed 1 year ago
I am also experiencing this issue (not on all devices, it seems to be pretty rare)
iPhone 14 iOS 16.0.2
This issue is also mentioned here: https://github.com/aws-amplify/amplify-swift/issues/2527#issue-1431699016
This seems like an urgent issue and should receive attention immediately.
Hi @wrbl606 - sorry you are facing this issue and thank you for the detailed report. Do you believe it's the same issue from the linked Amplify Swift issue?
At the moment, we are dependent on the Amplify Swift team for any changes to the v0.x Auth libraries. It's possible this issue has been resolved in our preview release of the Dart rewrite, v1.0.0-0
, and if not, it will be much easier for our team to investigate and make changes with this version.
I understand if you're not able to use it at the moment and can leave this issue open until either the Swift issue is resolved or our Dart release becomes stable. Please continue to work with the Swift team to resolve the underlying issue and thanks for your patience.
Will the v1.0.0
have the same API for end users?
Yes, it will have the same API. We've tried to limit breaking changes to the absolute minimum. However, we have needed to make some, mostly around type refinement and improved consistency.
@wrbl606 @michaeljajou - There was a fix released for this in the underlying iOS SDK that Amplify-Flutter depends on. You should be able to get this update by running pod update Amplify AWSPluginsCore AmplifyPlugins
from your /ios dir. You can confirm that the version with the fix is being used by looking for the version of AWSCore listed in /ios/Podfile.lock. The version with the fix is v2.28.2.
Please let us know if you are still seeing this issue after updating. Thanks.
Edit: Correction - Pulling in this fix will require a new release from Amplify-Flutter. We have a PR open to pull in the new version in Amplify-Flutter.
The iOS fix for this has been published in version 0.6.10 of the library. Would those experiencing the issue be able to test on this version and confirm it is fixed?
We've released a new version of the app with updated dependency and the issue is not reported anymore 👍
That's great to hear. Thanks for confirming.
Closing this issue as resolved. Please let us know if you continue to experience issues.
Description
Users previously authenticated with Cognito started generating the error below after an application update, which wasn't related to AWS Cognito API implementation or usage.
This happens consistently, reinstalling application does not fix the issue as the logged-in state persists. It affects only iOS users, Android version works perfectly fine. The main problem is that it doesn't reproduce locally on development machines so we can't experiment nor provide much more context to this issue.
This exception is thrown during
AmplifyAuthCognitoMethodChannel.fetchUserAttributes
call (line 297 in method_channel_auth_cognito.dart
).Categories
Steps to Reproduce
No response
Screenshots
No response
Platforms
Android Device/Emulator API Level
No response
Environment
Dependencies
Device
iPhone 7 Plus, iPhone 12 Pro, iPhone14,4, iPhone SE (2nd generation), iPhone15,2
OS
iOS 16.0.2, iOS 16.0, iOS 14.7.1, iOS 15.6.1, iOS 15.7.1
Deployment Method
Amplify CLI
CLI Version
No response
Additional Context
No response
Amplify Config