Reproduction steps:
1. Extract the attached “IN-104892_2134913-Profiling-Module-2ndary-Project-master.zip“ archive
2. Open the “Profiling-ProjectA“ and “Profiling-ProjectB“ projects from the extracted archive
3. Create an empty folder named “HttpServerData“, which is going to be used for hosting a local Http server for the Addressable Bundles
4. Open the created folder and inside create 2 folders named “ProjectA“ and “ProjectB“ respectively
5. Open the Addressables Groups window (Window > Asset Management > Addressables > Groups) using the “Profiling-ProjectA“ project
6. Build the Addressables Assets by selecting the “Build > New Build > Default Build Script“ option
7. Repeat steps 5-6 for the “Profiling-ProjectB“ project
8. Copy and paste the contents of “Profiling-ProjectA/ServerData/StandaloneOSX“ and “Profiling-ProjectB/ServerData/StandaloneOSX“ folders into the newly created “HttpServerData/ProjectA“ and “HttpServerData/ProjectB“ folders respectively
9. Start a local Http server by navigating to the “HttpServerData“ folder inside the terminal and execute “python3 -m http.server 80“ command
10. Build And Run the “Profiling-ProjectA“ project with the “Development Build“ and “Autoconnect Profiler“ options checked
11. Take a profiler capture or stop recording as soon as the square’s color changes
12. Select the “Addressable Assets” module inside the Profiler, which requests to select the proper build report
13. Load the build report from “Profiling-ProjectB“ located at “Profiling-ProjectB/Library/com.unity.addressables/BuildReports”. Make sure it has the same hash as the one shown in the Profiler
14. Observe the “Addressable Assets” Profiler module data at the bottom of the Profiler window

Expected result: The “Addressable Assets” Profiler module displays information about the addressable assets
Actual result: No information is displayed in the “Addressable Assets” Profiler module’s UI

Reproducible with: 2.4.1 (6000.1.0b13), 2.5.0 (6000.2.0b5), 2.6.0 (6000.0.51f1)
Couldn’t test with: 1.25.1 (2022.3.63f1) - after the addressable builds, the catalog is in “.json” format instead of “.bin” thus errors are thrown in the Player

Reproducible on: M1 Max MacOS 15.5 (Tested by CQA)
Not reproducible on: No other environment tested