#shane_error
1 messages · Page 1 of 1 (latest)
đź‘‹ Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đź”— This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1316430012471050272
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
here's the error we see
Hi there đź‘‹ I'm taking a look through our github repo and internally to see if anyone has run into this before.
The fact that you're only seeing this sometimes on iOS feels odd. Do you have any sense of whether there is any sort of pattern there? I'm curious if your users who are running into this didn't grant the camera permission to your app.
Well, that would be where I go but you always get through the ID part fine which needs the camera
so the fact it errors after 1-2 camera sequences just as you press the "take a selfie" button feels strange
Good point
Which version of stripe-identity-react-native are you using?
It's not the same error code, but this is the closest thing I'm finding so far:
https://github.com/stripe/stripe-identity-react-native/issues/102
The most recent version, I did see that but it didn’t help unfortunately
I did dig into the iOS sdk code and it looks like the name of the error is “missingSelfieConfig”
Any chance you have logs from when the error happened? I'm thinking this is going to be best handled by creating an issue in our repo so our team that maintains that library can take a closer look, but curious if you have more context before I suggest that.
However the fact that:
- it works 100% of the time using the web verification link for a verification that fails on iOS
- it works 100% of the time on Android
- it only sometimes fails on iOS
Leads me to believe it isn’t an issue re how we set verification sessions up
I don’t but I can probably reproduce and provide
Agreed, I don't think this is an integration issue, but rather think there is either an intermittent bug or something specific to the devices being used.
Ok well I’ll try to replicate and find some logs