#yuazeli_error

1 messages · Page 1 of 1 (latest)

boreal karmaBOT
#

👋 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/1449075659665047635

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

bitter summit
#

Hello, lookin in to this. I assume this behavior has always been going wrong as long as you have been trying to test it? Or has it ever properly errored here for you?

terse star
#

The first time. But happening on each round we test in iOS

#

With this image

bitter summit
#

Gotcha, thank you for the info

boreal karmaBOT
bitter summit
#

Apologies but I am having trouble finding the specific flow where you upload this ID. Can you tell me more about how specifically you are testing this flow? I am trying to test with our example iOS App's verificaiton project but it always seems to ask me to take pictures rather than upload an image

terse star
#

So in that space is where we upload this image as we are in a test environment. Not live. Eg- photo card. Upload this twice.

bitter summit
#

Can you tell me how you get to that space?

#

Also are you using our React Native or direct iOS SDK here? That shouldn't make a difference but could be helpful to know

terse star
#

The upload image is the space. We upload this failed image. It's failing in web and android just not in iOS.

#

Happy path- we have a nice green tick verified test image. And that returns as verified

bitter summit
#

Can you walk me through the steps you are taking to where you can upload this image? I am less familiar with our verification products, so I am having trouble getting to that screen. In the flows I have tried so far it doesn't let me upload pictures, it only allows pictures from a camera

terse star
#

We have customized it so the user can pick from gallery or take a pic and this is sent BE and the image sending is handled by the BE to the stripe sdk

bitter summit
#

Can you tell me more about what exactly you customized here?
Also to confirm, is you are using a WebView to go through a Connect onboarding Account Link correct?

terse star
#

We are using a direct java SDK.
No we are not using a web view.
We are sending test failed image from the BE

#

So the issue is the test verified and test not verified image both return as stripe verified

bitter summit
#

That is surprising, if this is a backend call then using the iOS SDK shouldn't effect that. Can you send me the code that your backend is using to submit this?

terse star
#

Actually we have just figured it's passing any image uploaded. Even if it's incorrect.

#

Hold on let me get you the code

#

If it helps we are based in AU.

#

File Creating: FileCreateParams params = FileCreateParams.builder() .setPurpose(FileCreateParams.Purpose.IDENTITY_DOCUMENT) .setFile(file) .build(); com.stripe.model.File.create(params)

bitter summit
#

I think the best way to debug this would be for you to try this flow once on iOS and once from one of the platforms where this works and have your code print out everything that is being sent in the request. The front end SDK and your country should not make a difference, this is very likely some difference between what your backend is actually passing to us in these API calls.

#

I more meant the API call that is actually submitting the account info and initializing the verification

terse star
#

Account creation:
AccountCreateParams accountCreateParams =                AccountCreateParams.builder()                        .setCountry(COUNTRY_AU)                        .setDefaultCurrency(CURRENCY_AU)                        .setEmail(request.getEmail())                        .setBusinessType(AccountCreateParams.BusinessType.INDIVIDUAL)                        .setIndividual(AccountCreateParams.Individual.builder()                                .setAddress(AccountCreateParams.Individual.Address.builder()

#

.setLine1(request.getAddress().getAddressLine1())                                        .setLine2(request.getAddress().getAddressLine2())                                        .setCity(request.getAddress().getCity())                                        .setState(request.getAddress().getState())                                        .setPostalCode(request.getAddress().getPostalCode())                                        .setCountry(request.getAddress().getCountry())                                        .build())                                .setEmail(request.getEmail())                                .setDob(AccountCreateParams.Individual.Dob.builder()                                        .setDay(request.getDob().getDay())                                        .setMonth(request.getDob().getMonth())                                        .setYear(request.getDob().getYear())                                        .build())                                .setFirstName(request.getFirstName())                                .setLastName(request.getLastName())                                .setPhone(request.getPhone())                                .setVerification(AccountCreateParams.Individual.Verification.builder()                                        .setDocument(AccountCreateParams.Individual.Verification.Document.builder()                                                .setFront(documents.getFrontDocumentId())                                                .setBack(documents.getBackDocumentId())                                                .build())                                        .build())                                .build())                        .setController(                                AccountCreateParams.Controller.builder()                                        .setFees(

bitter summit
#

Yep that defintiely shouldn't be effected by frontend or your account country here. Can you send me an account ID on hand from an account where you submitted this failed verification image but the it got successfully verified anyways?

terse star
#

There's more to that. Was getting the rest to you. Not on a nitro account. Lol

#

Acct_1SXUQVRjzJnxX01G

#

That's our main account.

bitter summit
#

Can you double check that ID? I am getting an error that that doesn't exist

#

Something else that could help is a request ID (req_123) from a time you created an account like that in your request logs

terse star
#

Oh

#

Acct_1Rq0oSRk1SuPEh2S

bitter summit
#

Also not able to find any accounts with that ID

#

I don't know what to say unfortunately, the only way for us to look further in to this would be to get an account or request ID that we can actually look up.

#

I do still think that the issue is something that your server is passing to that account creation API call, so the best next steps would be to set a breakpoint or something and double check that everything being passed there is what you expect

terse star
#

I have the request ID

#

req_nVskpJKpibDBbN

#

req_ ha5DF5vBRCjKeS

#

req_nCRxSiUhMYrfT3

#

req_2s6USoHxbTB8x1

#

Acct_1Rq0oSRk1SuPEh2S(zero, o after q)

#

So the issue is we aren't validating anything other than the image type. And stripe is passing wrong images as verified.

#

Weirdly only happening in iOS. The other flows the same image is being rejected and the user not verified.

bitter summit
#

We don't replace the image that you send us. It is possible that your backend may be mixing up these images, but we don't change the image that you send us.

#

Like I definitely think it would be worth going through your code path and seeing if anything different happens between your iOS frontend and other frontends. I have seen similar situations where a user accidentally hard coded the success thing but for just one specific code path and forgot to undo it when testing something else later

boreal karmaBOT
terse star
#

Is it possible to check the file details in the request?
So far we can't find any issues on our end as it's the same for android, iOS and web

bitter summit
#

I don't have permission to see the image it looks like. Even though it is test mode we have strict controls there.

terse star
#

Right. Any idea why the same image is failing in the others (as expected) but being verified in iOS?

bitter summit
#

I actually think that might not be the same image. I see that the file uploaded to us there was about 1 KB but the failed verification image is 5 KB

terse star
#

We are using version 26.10.0

bitter summit
#

Do you have a request ID from a time that that was successful? I can double check that I'm looking at things correctly

#

Of the iOS SDK? That is good to know, but completely irrelevant to how this Account create call is behaving

terse star
#

We tested the iOS flow recently. So havent had it successfully not verified.

#

The request IDs are the most recent passes we got

#

Java sdk

bitter summit
#

Sorry I phrased that poorly. I meant do you have a request ID from a non-iOS test you did where you correctly got a verification failure?

terse star
#

Noted. Was wondering if versioninig could be a part of the problem

bitter summit
#

Gotcha, my apologies for jumping to conclusions there

terse star
#

Np.

#

Hold on searching for an ID

#

req_soeJrdKPTF1UtR

#

req_eQDqHSsmq1QCaG

marsh falcon
#

👋 Taking over this thread, catching up now

terse star
#

👋

marsh falcon
#

The file in req_eQDqHSsmq1QCaG (expected) has a different file size from the one in req_nVskpJKpibDBbN (unexpected). They don't seem to be the same file

terse star
#

Is this an heic to jpeg problem or just size

#

Is the expected smaller sized then unexpected?

marsh falcon
#

We can only see the file size and name differences.

For req_eQDqHSsmq1QCaG (expected), the file name was IDENTITY_DOCUMENT_FRONT_1f226d26-503b-4dea-bcf0-8fd46e8c511c_image (1).png-0

For req_nVskpJKpibDBbN (unexpected), the file name was IDENTITY_DOCUMENT_FRONT_46599794-43d9-4cf0-80ee-c8aeba0fd2c6_IMG_4515.png

They aren't from the same file based on the file name

terse star
#

Ok sizes of each?

marsh falcon
#

For req_eQDqHSsmq1QCaG (expected) - 5086 bytes

For req_nVskpJKpibDBbN (unexpected) - 6400 bytes

terse star
#

Thanks so much.

#

Still baffles me though how it got passed as verified

marsh falcon
#

Could you try to submit the same file and try again? Based on the details, they don't seem to be the same file. We are unable to view the actual image, so it's hard to tell what has been submitted

boreal karmaBOT
terse star
#

It was this in different sizes.

#

And yet passed the stripe verification in iOS

hollow marsh
#

hi there, taking over for my colleague as they needed to step away. give me a few moments to catch up on the thread