#jgrody-Flutter
1 messages · Page 1 of 1 (latest)
from Google
Sorry, didn't specify which one. But yes, this is from Google Play and I warded off one issue by updating my privacy policy but the issue I pasted above was identified again and it was rejected for the 2nd time
flutter_stripe version 2.4.0 and it looks like that used stripe-android version 19.2.2
I found this issue: https://github.com/stripe/stripe-android/issues/4168 . Is there anywhere else could be using older version?
not that i know of
i found this command in a SO post to find what versions are being used
./gradlew app:dependencies | grep stripe
everything seems to point to 19.2.2 but there are a couple instance of com.stripe:stripe-3ds2-android:6.1.3 but i'm not sure that matters or not
+--- project :stripe_android
| +--- com.stripe:stripe-android:19.2.+ -> 19.2.2
| | +--- com.stripe:payments-core:19.2.2
| | | +--- com.stripe:stripe-core:19.2.2
| | | +--- com.stripe:stripe-3ds2-android:6.1.3
| | +--- com.stripe:paymentsheet:19.2.2
| | | +--- com.stripe:payments-core:19.2.2 (*)
| | | +--- com.stripe:payments-ui-core:19.2.2
| | | | +--- com.stripe:stripe-core:19.2.2 (*)
| | | | +--- com.stripe:payments-core:19.2.2 (*)
Can I have your account id? (acc_xxx)
acct_19bMc6E73CFYSdBf
Hey, I checked your account and can confirm newer requests are using flutter and 19.2.2. But we do see that you are using tipsi-stripe, an unmaintained third party built ReactNative library that uses non-compliant versions of the Android SDK under the hood
Google has flagged certain versions of the Stripe Android SDK as out of compliance, affecting versions prior to v9.1.0 on tipsi
Can you double check in all your track in GooglePay to see where is that tipsi version is possibly used?
I was using a package called stripe_payment previously that used tipsi-stripe and replaced it with flutter_stripe but what would I have to do here? remove all those previous releases?
Does what exactly appear in the tabs?
I just removed a draft release from the Internal Testing tab that was never used
would that have caused it?
no production releases should include any previous builds either
Could be, when you sure only newest version is in the UI, let's submit for review again