#liam-curran_api
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/1296406840694800426
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Could you please share the complete stacktrace ?
I'll just try replicate and get the entire error 👍
This is the function implementation if that helps:
const connectReaderHandler = async (reader: TerminalReader) => {
if (!terminal || reader.connected) return null;
setConnectReaderLoading(true);
const connectResult = await terminal.connectReader(reader, { fail_if_in_use: true });
if (connectResult && 'error' in connectResult) {
console.log(connectResult.error, 'connectResult');
// It is this error
setError(connectResult.error.message);
} else {
const { id: readerId } = connectResult.reader;
setReadersList(prevState =>
map(prevState, r => ({ ...r, connected: !!(r.id === readerId) }))
);
}
setConnectReaderLoading(false);
};
Thanks for the update.
Yes please.
That's the entire error:
{message: Parameter 'req_id': Expected type Integer, got typ…r/current/lib/terminalsimulator/util/utils.rb:115, code: reader_error}
and the message is what i posted above
It seems like it's a Stripe package bug, as we don't set any req_id anywhere in the code?
Sorry but this is not the entire stacktrace.
May I inivte you to reproduce the same issue on the official sample please?
https://github.com/stripe/stripe-terminal-react-native/tree/main/example-app
And share with me the reproduction steps.
Ah OK - we're not really sure what is triggering the failure so it may be tricky to reproduce
what extra info do you need re. stack trace?
well the full trace with all the filenames/lines.
also like, what version of stripe-terminal-react-native this is, if it happens on Android or iOS or both
Might just be a bug since that library is a beta and sounds vaguely like a problem in the simulated reader code, seems fine to just open a GH issue on it