Is there a way to roll back this situation? The initialize function is also not functioning as expected.
You once said in this article(Problem with UUPS Proxy Upgrade: UUPSUnauthorizedCallContext Error When Using `upgradeToAndCall` in OpenZeppelin 5.0.0 - #6 by ericglau) like this.
The only possible recovery that I can think of might be to call your
initializefunction via the proxy to set yourself as the owner in the 5.0.0 storage layout (otherwise the owner is the zero address due to the different storage layouts). Then callupgradeToAndCallto revert back to the old implementation, which will go back to the 4.x.x storage layout. However, this might not work or cause some fields to be rewritten if your initializer also writes to your own storage.
But calling initialize funcion in this case is not working at all. Can you please guide me to go through this problem. I need your help.