I don’t think so. It was reported by a member and @jane worked on it and fixed it at that time. I tested it myself. But for some reason it came back again. I noticed it because this is the second issue raised these couple of weeks for the same update issue.
See this post
@tatiang
This is a long standing issue but see my comments in the last few posts