#.cooper4952
1 messages · Page 1 of 1 (latest)
Hello! Can you provide more details?
Are you trying to build a server-driven integration or one using the Stripe Terminal JS SDK?
I am using stripe terminal js sdk for now
Okay, so you shouldn't be using any server-driven APIs in that case. Can you tell me more about how setReaderDisplay and clearReaderDisplay aren't working as expected? Do you get an error when you call either one?
Can you provide a lot more detail? What's displayed on the Terminal device's screen before you call setReaderDisplay? What does your code look like? Why are you calling clearReaderDisplay if setReaderDisplay isn't working?
Sorry for confuse ... please ignore clearReaderDisplay for now. May I provide my script file here?
Please tech me as expert. I am strugging with this feature in some days
And you may tech me even if I am wrong on another part of stripe integration progress ...
Line 316
Can you answer my other question? What's displayed on the Terminal device's screen before you call setReaderDisplay?
It shows splash screen what we setup
In your code you're only doing await terminalRef.current.setReaderDisplay(readerDisplayObj)
You should set the result of that to a value so you can tell if the Promise resolves to an error or not, and if so what the error is.
Sorry, please provide a example snippet. I dont get your point
As you see, I have added try catch ...
In the docs for setReaderDisplay: https://stripe.com/docs/terminal/references/api/js-sdk#set-reader-display
You're discarding the promise entirely.
You should be doing something like const displayResult = await terminalRef.current.setReaderDisplay(readerDisplayObj) and then looking inside displayResult to see if there's an error or not.
Thank you. I am writing code already. Can I go back on this thread?
Go back? You mean can you reference this thread later?
Yeah, we don't delete threads, but we close idle ones. You can always find earlier closed threads with Discord's search, or via the threads interface.