#othella_unexpected
manic widgetBOT
👋 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/1403292984497278987
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
modest kayak
I'm afraid the team here aren't a part of the app review process. You'll need to contact them directly as part of the review process and provide clear instructions on how the app works: https://docs.stripe.com/terminal/features/apps-on-devices/app-review#instructions
pale compass
I have already followed all those steps, it's been 10 days I am submitting again and again, but the asynchronous communication between 2 different timezones is a nightmare. I need technical info on my APK run during review, in order to be able to fix the code. Do you know who I could reach? (I already have contact with terminal support team, accelerate program team, business team)
I should be able to see in Sentry the reviewers attempts to launch the app, but I have no data at all, as if tests where made without internet connection
modest kayak
I don't know who you can contact directly unfortunately, other than perhaps our team directly and we can escalate internally. Have you tried running the intrsuction steps you've provided yourself? Does the app work on a fresh install with a new Stripe account?
My guess is the app isn't functioning like you expect so I'd recommended trying to repro that scenario and debug it
pale compass
I can only test on a DevKit, using a sandbox. Interaction with Stripe are both on backend (API key used), and also on terminal itself when initializing. I don't see any request to my backend to fetch connection token, I don't see any logs in Sentry coming from app start, so I don't know how to reproduce the review steps
Do you think I should create another account (not a sandbox), and associate DevKit to it, upload APK and try the flow?
modest kayak
I think you should try and test your flow end-to-end as if you were a reviewer, yes. Obviously it works on your account you've been testing/developing with, but the reviewers will be approaching this as a user with a fresh account, etc
pale compass
Thing is, only thing I can do to reproduce is deploy the app on my DevKit from the dashboard, and use it after terminal restart. I've done it many times, with success. I don't know what could differ on a non devKit terminal...
Cannot register reader with device_type of stripe_s700_devkit in live mode
I can't use my DevKit to test on a live account...
modest kayak
What details did the reviewer(s) actually share with you?
pale compass
"Your app is no reaction after a loading of charging payment."
And added a video + logs
I already mentioned to the terminal support team a blocking error I find in the logs
java.net.SocketTimeoutException: failed to connect to 172-20-10-6.tly344whj5qxuf5ffkoq.device.stripe-terminal-local-reader.net/172.20.10.6 (port 4443) from /192.168.1.109 (port 35498) after 45000ms: isConnected failed: ETIMEDOUT (Connection timed out)
It's depending on the terminal, not the code...
manic widgetBOT
pale compass
Hi @ripe lava . Thanks 🙂
ripe lava
I already mentioned to the terminal support team a blocking error I find in the ...
you're already in contacts with the terminal support team?
do you have the case ID please?
pale compass
Yes I am, first in chat then per mail. I don't have any case ID...
wait, I just had a look at the Stripe logs. I see connection_tokens requests from one of the testers device. Would it mean the fetched token they get don't allow to communicate further with the API?
ripe lava
Yes I am, first in chat then per mail. I don't have any case ID...
would you mind sharing your account ID please?
pale compass
used sandbox is acct_1RKyitIb2ZY3yfJp
I see readers and connection token fetch
But then no other requests
ripe lava
I was able to look into the case you've opened with our terminal team
here's their response from yesterday evening
They will need to add more logs to their production build and devkit build to understand why. For the logs, if the connection is failing then the reader cannot be found, so therefore there is no active reader that is able to be detected
pale compass
Actually I can build an APK with (many many) many logs
Should I send a production build with verbose mode enabled?
Although I suppose that the error with reader discovery (using "internet" method) is a painpoint
ripe lava
we're not saying you should submit that version
we're saying that the logs you have are not verbose enough for us to help you debug
pale compass
I will try to build a version with more logs in it, although most errors are logged
ripe lava
one more thing that I think you need to validate is the that your DNS is able to correctly resolve our Terminal Domains https://docs.stripe.com/ips#stripe-terminal-domains
pale compass
I see request on my API backend to fetch the connection tokens, so that should be the reason with reader discovery fails
ripe lava
it's not the same domains
pale compass
connection errors come from logcat, so the device itself your testing team uses, no?
Discovery is handled by the terminal, not the backend
I am using the Terminal React Native SDK
(Discovery, connection, payment method collection are from the terminal)
I only interact with stripe API from my own backend
ripe lava
yes the server-driven integration requires you to both have access to the Stripe API (from the backend) and the Stripe Terminal Domains
could you please check on your network if 172-20-10-6.tly344whj5qxuf5ffkoq.device.stripe-terminal-local-reader.net resolves to an IP address?
pale compass
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
Name: 172-20-10-6.tly344whj5qxuf5ffkoq.device.stripe-terminal-local-reader.net
Address: 172.20.10.6```but I cannot test from the server itself, it deployed using Vercel 😅
ripe lava
this should be the network where the terminal is
pale compass
My devkit is on same network I just used for the nslookup
But I can't say if it resolved on the reviewers' team network...
ripe lava
Address: 172.20.10.6
that's the correct address
pale compass
That's why I wanted to check their configuration
My own device, a DevKit, runs the app seamless, I cannot reproduce the errors from reviewers team...
ripe lava
My own device, a DevKit, runs the app seamless, I cannot reproduce the errors fr...
oh so it's not your terminal that is not working?
pale compass
no
On my end it works like a charm
But it fails on the review team devices
no clue why
ripe lava
ok so you need to test the nslookup on their network
pale compass
That's why I am asking for a way to reach them and do some network tests 😄
ripe lava
oh! when you say reviewers team you mean us
pale compass
ahahah
ripe lava
🤦
pale compass
yes 😄
ripe lava
sorry for the wrong emoji I just typed face 🤦
pale compass
"you" are rejecting my app 😉
ripe lava
sorry for some reason I didn't got all of the context. I thought it's not working on your side
pale compass
No worry. On my side everything is fine
But when your testing team tries the app, I don't get any Sentry trace, the app fails
Although I can see connection_tokens are being fetched on my backend
but then no other request
ripe lava
ok then it must be your vercel API app that is not reachable
pale compass
It is, the connection_tokens requests are handled
ripe lava
can you share a request ID?
pale compass
https://dashboard.stripe.com/test/workbench/logs/req_NFNYV6elgtsStb
https://dash...
here
pale compass
those are logs on my API, coming form my own device. see the /merchant/... request
those are logs from "your" team 😄
only connection_token fetch
although the code sets a lifetime of 4 minutes for this token
In the code, I fetch a connexion token, then I run discovery and connect method from the terminal, then I fetch some info from my API
But when you team tries the app, it fails on discover & connect
ripe lava
can you do me a favor?
To use the API or test your app, you can limit the compatible_device_types to only DevKit device types (stripe_s700_devkit).
can you do that and skip the app review
uninstall your version from the terminal
pale compass
I have some version for devkit only uploaded
ripe lava
I just want you to try to install it from Stripe's side instead of directly to your terminal if you know what I mean
pale compass
I have already deployed from the dashboard and restarted the device
ripe lava
did you uninstall before?
pale compass
No. Am I able to uninstall from DevKit using adb?
ripe lava
yes you should be
I'm just afraid that for some weird reason you're not running the same version of the app as the one you've submitted
pale compass
it's a pain not being able to test a version that I want to use as production version
I need to rebuild
You should tell your company to change that process 😄
I just uninstalled and redeployed
it's loading and reader is connected
Logs from my API as proof
modest kayak
Hey, so we checked internally and it seems like you're already working with a colleague on this. They're talking with the Terminal team about the problem, and they're the best team for you to get help from. I expect you'll have a reply from them ~today so I'd recommend you just hold out for that
We don't really know how the review process works so I think us suggesting steps on how to debug is not productive
pale compass
I know how to debug my app on my device, I just don't know how to get useful info from your review team 😄
modest kayak
And that's the part they're working on 🙂