Looks like this problem is back with Compose 2025.10, reverting back to compose 2025.09 solved my issue.