#domhacking

1 messages · Page 1 of 1 (latest)

lucid patrolBOT
iron moat
#

Hey there

#

Which reader are you working with?

charred mortar
#

WisePad 3

slim ingot
#

Hi 👋 Thank you, for that clarification taking a closer look.

#

It looks like didStartInstallingUpdate is thrown when a reader's update is expected to take longer than 30 seconds.

Mandatory updates should prevent your application from connecting to the reader until the required update is successfully installed on the reader.

If an optional update is available, then didReportAvailableUpdate should be thrown.

charred mortar
#

Ok thank you I will have a read through.

#

I think I am doing it correctly as the download starts but then after about 13% the update stops.

#

And I get this error:

{code: "READER_ERROR.READER_SOFTWARE_UPDATE_FAILED", message: "Update failed due to configuration error"}

indigo shadow
#

@charred mortar hello, catching up here

1/ the same reader, does it update through the Stripe app?

#

cause if not, then it might be a firmware config issue on the reader

#

you mentioned it does fine on the Stripe app?

charred mortar
#

Hey @indigo shadow , Yes it does update through the stripe app. But will not on my app

#

In my code is there anything that could be blocking that?

indigo shadow
#

and the "Stripe App" here is the Terminal example app?

#

how far does it update with that?

charred mortar
#

Payment for stripe

#

But I will try the terminal example app now. Good point.

#

get 13%

indigo shadow
#

sorry still unclear, it only updates to 13% with the Payment For Stripe app?

charred mortar
#

Sorry

#

Payment For Stripe -> Works
My App -> 13% - 22%
Example App -> Trying now

indigo shadow
#

gotcha!

charred mortar
#

I think the example app looks like it is failing as well.

#

@indigo shadow

#

I have not received an error message yet

#

Ok error received

indigo shadow
#

ah ok then I think the issue is with the reader itself

charred mortar
#

But I have tried multiple readers

indigo shadow
#

wait, multiple readers can't be updated by the Terminal Example app?>

charred mortar
#

Well, I have tried three terminals on my app and they both fail to update.

I have just one of those readers on the example app and it also fails.

#

I would assume that if I tried another reader I would get the same message.

indigo shadow
#

yeah that sounds like an issue with the Readers

#

they could have bad firmware on them

#

and none updated

#

and that they should send you a different reader to try

#

also share with them the Reader serial number, the firmware version number etc

charred mortar
#

Ok

#

I think it sounds like an issue with the RN example code or RN wrapper?

indigo shadow
#

neither

#

actually ah you tried the RN example app

#

try the Terminal iOS example app just to rule RN out entirely

#

and see if that updates fully

charred mortar
#

Cool cool