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
{{ message }}
This repository has been archived by the owner on Nov 10, 2023. It is now read-only.
Issue:
After the Spending limit module is enabled, any future spending limit creation should just create the "Allowance" for the owner to use tokens, but the tx is trying to enable the module again
Steps:
Create a new safe with a "2 owners" policy
Create a spending limit with ETH
Check that the owner is listed in the spending limit table
Delete that spending limit
Try to create another spending limit for any owner
Expected result:
The app should check whether the spending limit module is enabled
If yes, just the set allowance, no need to enable the module again.
if no, the module first needs to be enabled.
Current result:
The tx has the action to enable the module again
Issue:
After the Spending limit module is enabled, any future spending limit creation should just create the "Allowance" for the owner to use tokens, but the tx is trying to enable the module again
Steps:
Create a new safe with a "2 owners" policy
Create a spending limit with ETH
Check that the owner is listed in the spending limit table
Delete that spending limit
Try to create another spending limit for any owner
Expected result:
The app should check whether the spending limit module is enabled
Current result:
The tx has the action to enable the module again
Check this safe, that has the tx in Queue where is trying to enable the module again, then check also the "Advanced" settings, where the module for spending limit can be seen already active:
https://pr2535--safereact.review.gnosisdev.com/rinkeby/app/#/safes/0x2733739C73DaFe449BBd4d962CbE270221A85944/transactions
The text was updated successfully, but these errors were encountered: