#lichtamberg
dim briar
let me see, mom
In general I create the payment intent like this:
PaymentIntentParameters.Builder()
.setAmount(amount.value!!)
.setMetadata(metadata).setCaptureMethod(CaptureMethod.Automatic) .setCurrency("eur") .build()
i guess here: Terminal.getInstance().connectLocalMobileReader(
yep, and the onFailure Callback gets called
Terminal.getInstance().connectLocalMobileReader(readers.get(0), config, object :
ReaderCallback {override fun onFailure(e: TerminalException) { callback.onFailure(e) }
slow wigeon
The reader location need to specify the country.
dim briar
But the Location ID is not the Stripe Location id?
because it was working before the stripe terminal SDK update
also the documentation shows the stripe id: https://stripe.dev/stripe-terminal-android/external/com.stripe.stripeterminal.external.models/-connection-configuration/-local-mobile-connection-configuration/index.html
ah wait
maybe its my mistake, let me check
slow wigeon
Could you please share the location ID?
dim briar
yeah I guess it was our fault, wrong location ID
slow wigeon
Did you manage to solve it?
dim briar
trying right now
fossil geodeBOT
feral sonnet
Thanks for the info. And what terminal SDK version did you upgrade from and to?
dim briar
2.23.1 to 3.0.0 today
we were testing it last week with the old version and updated today
feral sonnet
Not seeing anything immediately obvious in the migration guide. Still looking... https://stripe.com/docs/terminal/references/sdk-migration-guide?terminal-sdk-platform=android
dim briar
yeah, I also dont know what I could do wrong otherwise.. looks fine the code
not sure if this error inspection helps..
feral sonnet
Still having trouble finding info on this and I have pulled in a colleague. I will let you know what I can find.
dim briar
Ok thank you, I also couldnt find out why its not working.. would be great if you could find the reason
feral sonnet
And to double check are you using the new fields for location ID in your android code?
- Update: Deprecated classes and members have been replaced or removed:
- ConnectConfiguration.registerToLocation has been removed and replaced with ConnectConfiguration.locationId.
- The locationId parameter from the HandoffConnectionConfiguration constructor has been removed.
- Reader.registeredLocation has been removed and replaced with Reader.location.
dim briar
as far as I understand it, the TTPA reader doesn't need to be registered, since you provide the location_id anyway (the same as the wisepos3)?
also there is nothing about this in the example integration: https://stripe.com/docs/terminal/payments/connect-reader?terminal-sdk-platform=android&reader-type=tap-to-pay
except passing the location id to the LocalMobileConnectionConfiguration
which we do (and is a valid test terminal location)
(tml_FQUNxQj0hAOhz8)
feral sonnet
Right, apologies, I forgot we were talking about tap to pay temporarily.
As far as we can tell the error should be related to the terminal location's country but it does look like that location has its country set
dim briar
yep, is set to austria
feral sonnet
So it looks like we identified this error last week and have a fix on the way but it is not out yet.
There is a GH issue about this as well, I am sure we will update it when the fix is out https://github.com/stripe/stripe-terminal-android/issues/372
dim briar
yep, this is my issue, i created it some minutes ago 😄
the problem is that we have a big event (7500 people) and we would like to use the terminals.. I mean we can revert to the old code, but unfortunately the (old) documentation is not online anymore?
or is there a way to see the old documentation?
so we would have to decide if this gets fixed this week (we need the final software next week).. .or we should revert?
feral sonnet
Yeah I would say reverting is probably the safest bet in the meantime. I feel that the fix will likely come out this week though I don't have an ETA on it at the moment.
Looking in to docs for previous versions. Is there something specific you need to know after reverting?