#ash_docs
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/1397575453698428968
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
Hey there, is this something you're actively developing or trying to deploy? At what stage is this failing?
Additionally, are there any errors surfaced in the UI or device logs that would hint at what is failing?
i am just trying to run the app above
it just keeps on loading
i also regsitered the reader correctly..
not sure why it doesnt work
no logs as far as i see on the app or console..
can u run it and see if it works for u
or someone from S700 team?
Are you running this on a devkit device? Development/testing can only be done on a devkit s700. If you can share the serial number of the reader we can look for errors in logs here, too.
It looks like that reader is reporting some network failures, being unable to connect to some of Stripe's servers requires for Terminal to function
You should review that list and ensure your network allows connections to all of those domains/hosts
I'm also seeing some errors suggesting an invalid reader type might have been passed, but its unclear if that would be from your code
Invalid device_type: must be one of bbpos_wisepad3, stripe_m2, stripe_s700, bbpos_chipper2x, bbpos_wisepos_e, verifone_P400, simulated_wisepos_e, simulated_stripe_s700, or mobile_phone_reader
That seems like you might be making a call with an invaliddevice_typeparameter. Can you check your device/app logs for this, or any calls you make that would fit this shape?
wait
You said this was the sample app, though, right?
i used this device for my personal app also
but i am asking about sample app
can u run the sample app and check pls?
I can't currently, no, I'm not set up for that.
i used this device for my personal app also
I assume you mean a separate Apps on Devices app. Did you have the same issue with that?
my only issue is with running the sample app
will u be able to guide me
if im missing anything ?
cus i am sure i followed all the right steps.
who can guide me for this?
i can give all the data needed..
one month back i didnt have any issues running this sample app.. all of a sudden im getting issue
There haven't been any changes recently other than updating the SDK version use: https://github.com/stripe-samples/terminal-apps-on-devices/commits/main
And you're running the App as described here? https://github.com/stripe-samples/terminal-apps-on-devices/blob/main/README.md?tab=readme-ov-file#setup
I still think that what we really need is device logs. If its erroring/crashing there should be some logs on the reader while running.
on the reader or console, i dont see any erorr logs
With the devkit you can use adb and logcat to tail the device logs
sometimes it shows that the reader is not registered
even if it is
thats the only log i see
the app doesnt crash its just that the app keeps on loading
if u open the code, u can see a string for "register a reader" or so
but that should not happen either cus the reader is registered to correct stripe account..
is there anyone who can run the app and see if it works for them
and guide me
The guidance currently is the same: we need more info in the form of logs from your device, which might require you to instrument this:
Stripe doesn’t provide an application-level instrumentation solution. To keep track of crashes and other logs from your application, you can use a third-party library such as Sentry or Crashlytics.
https://docs.stripe.com/terminal/features/apps-on-devices/build#instrument-app
This doesn't seem to align with expected behaviour:
the app doesnt crash its just that the app keeps on loading
https://docs.stripe.com/terminal/features/apps-on-devices/troubleshooting#:~:text=Why is my app constantly restarting%3F
Why is my app constantly restarting?The Stripe Terminal card readers restart the default app in the event of a crash. This manifests differently for production and DevKit devices:
Production – If you configure your app as the default app on production devices, the app automatically restarts when there’s a crash. If the app crashes during initialization (for example, a missing or broken database migration), the device can enter a crash loop.
DevKit – If you configure the Stripe payment app as the default app on DevKit devices, your app queues on the device and then becomes the primary app. If the app crashes, the Stripe payment app restarts instead.
It sounds like you are in a loop like the production reader description, its possible this could happen on the devkti too if you set your app as the default (instead of the stripe payment app)
its not restrating on its own
the app keeps on loading
one who worked on it or knows how to run may figure out the issue faster
the app keeps on loading
I don't understand what this means. I think it would be helpful if you could reset with a new build of the sample app and a new deployment to your devkit reader, and capturing the resulting behaviour.
If I have our bot send you a link to open a case with us, do you think you could capture a video showing what you're seeing end to end so we can raise with the Terminal team to try to help?
There seems to be a missing piece here that I'm hoping we can figure out seeing the entire flow you're using to reach this issue.
i can u send u one screenshot on whats happenin
I don't think that's going to be sufficient, since I suspect the entire sequence could matter here, not just the current/final state you see.
Hello @coral kiln, we have sent you a direct message, please check it at https://discord.com/channels/@me/1351622527948034171
- 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
shoud i send it here?