Closed basvandorst closed 8 months ago
Hi @basvandorst!
Thank you for your report. We are currently investigating this issue but have so far not been able to reproduce it. Could you please send us the software version of the readers you have connected? You should be able to find this using the Settings > Readers > Connected reader. It should a table with information such as the card reader model, software version and program version. If you could be so kind to share that, it might help us in our investigation.
Thank you in advance!
Thanks @ppeelen, just contacted our partner who experienced these kind of problems. They will let me know when it occurs again and send me the requested information.
Hi @basvandorst!
Do you have any further updates regarding this issue as we were not able to reproduce it?
@ppeelen just checked the status of this issue by our partner. They haven't seen this issue in the last 2 months. Note; now they always double check the power cables after each installation, so they made sure all devices are continuously power connected.
Consider it as closed for now, since we haven't experienced it the last months + don't have concrete steps to reproduce the issue.
Thank you Bas for your update. I will now close this issue, but please do not hesitate to reach out to us again if this, or any other issue for that matter, would occur.
Best regards, Paul Peelen
Expected Behavior
Callback for a failed or successful transaction
Current Behavior
Context
We had similar issues before, but much less after the 3.5.0 release: https://github.com/iZettle/sdk-ios/releases/tag/3.5.0 Unfortunately we still have the issue in some cases (<1%). Most probably related battery percentage, because we only experience it when the battery is very low.
Failure Logs
N/A