We were having the exact same issue, it was only failing for aab. This is a signing issue as mentioned above, which is due to the Releases signed by Google Play by default on Google play console, generates a new signing certificates. And the fingerprint details we can see in the Test and Release menu > Setup > App signing. We can see "App signing key certificate", here we can note SHA-1 certificate fingerprint and use it in,

(if you're using Firebase) Firebase console > Project Settings > General > add in SHA certificate fingerprints

And also, in Google Cloud > API & Services > Credentials > Create Credentials > Create OAuth client ID > Android > add in SHA-1 certificate fingerprint.

After adding the SHA-1 fingerprint, immediately I could see the issue is resolved. So here the point is, we should add all the respective SHA-1 fingerprints in Firebase (if applicable) and in Google cloud services too.