Thank you for reporting a bug to Unity.
We have investigated the issue but were unable to reproduce it with the information provided. This can happen due to differences in environment, project setup, or steps taken.
Play Mode Script must always be set to "Use Existing Build (OSX)". Otherwise Catalogs to update will always print 0 on the Play Mode Script "Use Asset Database (faster)".
The local build data from the first build should be preserved. The Addressables rebuild will overwrite the local build data, which updates the local catalog and "Catalogs to update" will return 0. This is wrong because a shipped player build will have the original local catalog on startup, not the updated catalog.
We will close this case for now. If you're able to share additional details such as different projects, steps, hardware/software configuration, or logs - please let us know, and we'll be happy to re-evaluate.