@jayanthtn - this should now be fixed in production, so if you rebuild your app (expo build:android --no-publish) then you should be able to submit it to Google Play with no problems.
The issue was due to the fact that in our revamped Payments module for SDK 30, we added the following problematic line to AndroidManifest.xml in order to support Android Pay:
<meta-data android:name=“com.google.android.gms.wallet.api.enabled” android:value=“true”/>
Unfortunately, it seems that Google Play flags new apps (but not updates to existing apps) that include this line and we did not catch this. We’ve adjusted things so that this line is no longer included by default, and Android Pay is instead opt-in on ExpoKit apps.
Many apologies for the trouble, and thanks again for the timely report!