Inconsistent Content Hash Values from Dropbox Endpoints

Hello,

I hope you're all doing well. I've come across an issue while working with the Dropbox API, specifically related to content hash values, and I'd like to seek your insights on this matter.

1. List Folder and Thumbnail Batch Endpoints: When using the "List Folder" and "Thumbnail Batch" endpoints, I observed that the content hash value returned for a specific file remains consistent. This behavior is as expected and aligns with the file's content.

2. Search V2 Endpoint: However, when I use the "Search V2" endpoint to search for the same file, the content hash value it returns is different from what I obtained through the "List Folder" and "Thumbnail Batch" endpoints. Furthermore, it appears that all files' content hash values retrieved from the "Search V2" endpoint are the same.

These discrepancies are causing some challenges in maintaining data consistency within my application. I'm wondering if there might be any insights or explanations for this behavior. Specifically:

• Why does the "Search V2" endpoint return different content hash values for the same file compared to the "List Folder" and "Thumbnail Batch" endpoints?
• Is there any specific reason or logic behind the content hash values returned by the "Search V2" endpoint being the same for different files?

I'd appreciate any guidance or information that could help me better understand and work with these discrepancies. Thank you for your assistance!