react-stripe-js: [BUG]: Intermittent issue with CardElement
What happened?
The issue is intermittent.
Clients have been reporting this icon in the Credit Card form.
This is the implementation:
`import { Elements, StripeProvider, CardElement, injectStripe } from ‘react-stripe-elements’;
const CheckoutForm = (props) => { const dispatch = useDispatch();
const [ isLoading, setIsLoading ] = useState(false);
const submit = async (ev) => {
setIsLoading(true);
const token = await props.stripe.createToken(
{
name: `${props.name} - ${props.email}`,
address_country: props.country,
}
).then(props.handleResult)
setIsLoading(false);
if (token.token) {
props.returnToken(token);
}
if (token.error) {
dispatch(setSnackbarMessage({
message: token.error.message,
type: 'error',
}));
}
}
return (
<>
<StripeProvider
apiKey={REACT_APP_STRIPE_US }
>
<Elements>
<CardElement />
</Elements>
</StripeProvider>
</>
);
}
export default connect(mapStateToProps, mapDispatchToProps)(injectIntl(injectStripe(withRouter(CheckoutForm)))); `
I’m trying to understand what the icon in the attached screenshot means. This is intermittent and I was never able to reproduce it, but many clients have complained.
Environment
No response
Reproduction
https://cur8.com/schedule/item/2/335105?event=80912&date=335105
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 16
@gabsfm & @ValerieMichaud this should now be resolved. Please do let us know if you continue to observe this issue happening.
(As expected, you don’t need to change anything in your integration.)
Once the issue is resolved, you should not need to make any changes to your integration.
Thanks again for the info and reports here. We’re now able to reproduce this and have identified the specific conditions for it to happen and we’re working on a resolution.
Likewise, will let you know if we find anything. Thanks @brendanm-stripe !
Thank you so much for your help! I will report back if there’s anything.
It’s possible other assets are affected, even if we haven’t yet observed that. I’d say any novel failures with the same manifestation (blocked iframe after mount with “Your organization doesn’t allow you to view this site”) are likely to be the same underlying issue.
If you have access to the page where these occur, please share the
srcURL from the blockediframeand we can add that asset to our investigation.Thanks for some insight @brendanm-stripe - does this misclassification of content happen to extend to apps using
AddressElementandPaymentElementelements in new versions of this library? We’re looking into a slightly different report and are wondering if it is all related, even if it manifests in different way in the UI?This is happening due to a change in Chrome site blocking behaviour with the release on November 19th. Some Stripe.js assets are being misclassified and blocked by default for enterprise education accounts, or administered groups with certain configurations. We’re working on resolving that misclassification.
@brendanm-stripe same scenario here.
We haven’t been able to reproduce on our side, using multiple devices and browsers.
Most of our users also come from educational institutions but some of them have reported the issue from their phones as well.
@brendanm-stripe its possible since a large cohort of our users are in education facilities, but some reports do seem to indicate personal computers used.
It’s difficult for us to know for sure since we’ve struggled to replicate the issue in-house, and communication with affected end-users is via by our clients.
We’re seeing the same issue in two completely unrelated and separate systems.