@Moin we’ve identified the issue, it was related to site setting naming. We have fixed it and are now deploying it for all sites soon
For now, If you go to What's New and click Check for updates and then go through the process, it should be working properly