If you mean the zap or caching issues, I don't think you need an OS update for it. Probably just have to flush the cached data from your nostr app or the browser if a web client. (don't forget to backup your following etc first).

I had an issue recently when I tried to change my Alby address (on their site) from cybergrinder@ to thegrinder@. It broke zaps for about half the people who tried to zap for about two days. The other half had no issues.

At some point on the second day I went back into Alby's UI and changed it back to cybergrinder@ which minimised zap errors for others. This made me believe that we might be dealing with caching and/or updating issues across the protocol / relays.

I even pushed my changes across a vast number of relays in an attempt to just make the address change propagate faster but in the end reverting back was just more convenient than waiting around.