The protocol-kit instance should refresh after a deployment has been made through the `4337pack`

[louis-md]

Description

When using the safe4337Pack, deploying a Safe does not update the protocol kit accessible at safe4337Pack.protocolKit (even if safe4337Pack.protocolKit.isSafeDeployed will correctly return true). Subsequent actions using the protocol-kit will return the error:

/node_modules/@safe-global/protocol-kit/dist/src/managers/ownerManager.js:115 throw new Error('Safe is not deployed');).

Steps to reproduce

Steps can be found in this Stack Exchange question.

Expected result

safe4337Pack.protocolKit should be refreshed after deployment, so further actions can be made without having to use safe4337Pack.protocolKit.connect(...).

[salochara]

Hi!!

Just wanted to ask if there's an estimated timeframe for tackling this?
This would be very helpful for planning purposes on my end.

All the best and thanks for your awesome work!

[dg794]

hi guys, any update on this? or reason why it's not prioritized? Thanks!