The issue contains the listed of issues found during the full regression for 2.5.0 release candidate
List of issues :
- [x] Owners with added during the load safe flow name don't appear in the addressbook
Steps:
1. Load existed safe
2. add name for the owners during load safe flow
3. go to the Address book
Current result: Only loaded safe is listed in the addressbook
4. Check owners list in the settings
Current result: The entered during the safe loading names are used for the owners in the settings
Expected result: The named owners should be added to the addressbook
Chrome/MacOS
Background issue needs a separate task, as the component is in safe-react-components. Will be fixed here:
https://github.com/gnosis/safe-react-components/issues/118
New issues:
The name of owners in the Tx list is the one in the settings, not in the address book
UPDATE: I've check the redux and the issue is that the names of the owners and the names in the address book list they differ
Owners with added during the load safe flow name don't appear in the addressbook
@francovenica this is the same issue as you've reported in #2122, isn't it?
Creating an entry directly in the Address Book also doesn't work.
Looks like this regression is from https://github.com/gnosis/safe-react/pull/2187/commits/9a845a203922b62a5393cfb2364f9f63dab83c59
The issue goes away when I locally restore await saveAddressBook(addressBook) as it was.
@francovenica this is the same issue as you've reported in #2122, isn't it?
Yes, it was reported there already
On the release branch, the Aave v2 app does not load for me. Is this a known issue?
Also a minor and probably more of an enhancement for later: with the new cardless design we should be able to remove the grey
(semi-transparent) background behind the legal disclaimer.
On the release branch, the Aave v2 app does not load for me. Is this a known issue?
Also a minor and probably more of an enhancement for later: with the new cardless design we should be able to remove the grey
(semi-transparent) background behind the legal disclaimer.
@lukasschor Aave v2 app has a domain lock, so it will only load when used under gnosis-safe.io domain. This is known and it's expected.
About the grey background of the disclaimer I agree we should leave the grey we use on the app general background.
@lukasschor something like this?
@lukasschor we won't solve the background issue in this release. It needs changes in safe-react-components
It's reported and will likely be ready for next release:
https://github.com/gnosis/safe-react-components/issues/118
The issue reported regarding the address book is something that is already happening in production, so is not critical for this release.
The team will discuss how to deal with it, since there are other tickets that are already dealing with the address book and other storage issues.
Camera remains on constantly- #2196
Wasn't it already like this on production?
@francovenica in your gif, the URL is https://rinkeby.gnosis-safe.io.
3.5.0 has been long deployed.
Most helpful comment
@lukasschor we won't solve the background issue in this release. It needs changes in
safe-react-componentsIt's reported and will likely be ready for next release:
https://github.com/gnosis/safe-react-components/issues/118