#mordil
1 messages · Page 1 of 1 (latest)
Hi there
Not aware of any particular ongoing issue.
But I'd recommend gathering up some examples and writing a detailed report to https://support.stripe.com/contact/login and we would be happy to take an indepth look
We're seeing a large amount of sdk busy errors, or just straight up terminal(_ terminal:didReportUnexpectedReaderDisconnect reader:)
We've enabled logging, but those aren't proving to be that useful to us to determine why the M2 devices are being disconnected.
Sometimes it's after 5 hours of the app being ran, other times it's 19-24+ (we're notifying partners that it's expected every 24 hours)
Yeah like I said I'm not aware of any uptick in these issues lately. There could be many reasons this might be happening. Really your best bet is to gather specific examples (the exact time, the reader, and example PaymentIntent, etc.) and provide that to us over email so we can investigate.