#echeyde-terminal-wisepos

1 messages · Page 1 of 1 (latest)

languid sparrow
#

Hey @tired lily can you clarify what you mean by IP address frequently changing? Like they reboot the device?

tired lily
#

sure, like the wisepos e address is changed by the LAN dhcp system.

languid sparrow
#

but does it happen as the device is live and connected?

tired lily
#

yes

tired lily
#

yes I did.

#

which leads to understanding how is the dns record updated and what is the TTL ?

#

since the card reader hostname is tied to the ip address

languid sparrow
#

gotcha

#

I'm asking a colleague I don't know much about that part, I'll update you once I find out more

tired lily
#

great, thanks!

languid sparrow
#

Okay I confirmed with some engineers that this is something we don't handle well today. You would detect the connection error and basically you'd have to disconnect/reconnect in that case.

tired lily
#

ok , so reconnect is the flow that creates the DNS record ?

#

also can you lmk what is the TTL for that dns record? thanks

languid sparrow
#

I worry you're overindexing on the DNS when it's more that we don't really support the device changing IP address in the middle of being "up"

tired lily
#

i just need to know which flow will cause the new dns entry, it is reconnect?

languid sparrow
#

But again you are focusing on a DNS entry that is irrelevant

#

the problem is that the app is stuck with the old IP and never looks for a new one at that point

tired lily
#

ok, so how to get the app unstuck? re-pair wisepos e?

languid sparrow
#

no, you disconnect and reconnect your app (which is unrelated to the DNS entry being flushed, there's just a new entry for the new IP at that point already, and the app doesn't know about it because it stored the old hostname)

#

disconnecting/reconnecting doesn't change the DNS entry, but it forces the app to get the correct hostname back

tired lily
#

is correct hostname returned by connect then?

languid sparrow
#

it's when you discover readers I think

tired lily
#

ok, and stored on local iOS storage... note a reconnect/disconnect does not seem to work to solve an IP address change...

languid sparrow
#

you need to re-discover readers too. Have you tried that?

tired lily
#

yes, same. Does the sdk has a flush() function to remove any locally stored artifacts, like hostname ?

languid sparrow
#

looking

tired lily
#

👍 thanks , love your sharp support here!

languid sparrow
#

what exact SDK are you using and what exact version

tired lily
#

it's an iOS one , and recent, let me track my dev to know exact

#

version 2.0

languid sparrow
#

exact version would help. Unfortunately no one is around to answer the specifics. I'd recommend contacting our support team https://support.stripe.com/contact and providing detailed examples where this happened and we can look at our own logs to try and narrow it down

tired lily
#

will do , much thanks for the help.