You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
After a fresh install, I cannot add my Safe Account:
After choosing network and entering the Safe's address, when adding a Name for the Save account and click on Next I get: Can't add Safe Account: an error occurred. Please try again later
When going back, trying to add the same Safe Account again I get (already on selecting the address): Can't use this address: a Safe Account with this address has been added already. Please use another Safe Account address. (Error 1101).
To Reproduce
Steps to reproduce the behavior:
Go to 'My Safe Account'
Click on 'Load Safe Account'
Select some network and address, click next
Try to enter a name
See error
Expected behavior
Should work like it did before (on android12)
Screenshots
Smartphone (please complete the following information):
Device: Fairphone 3
Android Version: Android 13, LineageoOS 20
App Version: 3.9.0
The text was updated successfully, but these errors were encountered:
We are getting new complaints for the add safe flow when Google Services are not available on the mobile device
device info from the support ticket:
Huawei Mate X3, Android 12
Describe the bug
After a fresh install, I cannot add my Safe Account:
After choosing network and entering the Safe's address, when adding a Name for the Save account and click on
Next
I get:Can't add Safe Account: an error occurred. Please try again later
When going back, trying to add the same Safe Account again I get (already on selecting the address):
Can't use this address: a Safe Account with this address has been added already. Please use another Safe Account address. (Error 1101).
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Should work like it did before (on android12)
Screenshots
Smartphone (please complete the following information):
The text was updated successfully, but these errors were encountered: