#ash_code

1 messages ¡ Page 1 of 1 (latest)

river pendantBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1387098290939629568

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

upper jolt
#

Hello

#

Yes you would still use your Publishable key here.

#

Can you tell me more about what "not working anymore" means exactly?

#

Are you seeing a specific error?

sonic shore
#

so when i try to create a connectionToken according to the documentation, it returns a secret. But in our older application, we dont get any secret, instead we get a publishable api key (terminal 3.3.0). When we use this api key as the connection token, it doesnt fetch locations, but when we use secret, it fetches locations.

#

earlier, in our old app, it never returned any secret

#

we used the api key as our connection token

upper jolt
#

Is this using the Javascript SDK?

sonic shore
#

android

#

native code

#

we checked the github for stripe android

#

and we found out secret is now mandatorily required to fetch locations

upper jolt
#

Gotcha, as far as I know you should always have been using your Publishable key to initialize the SDK and then call your backend for a Connection Token.

#

But I'm double checking

sonic shore
#

So there are 2 steps:

Init terminal - in which we pass the connection token
This connection token - earlier - publishable api key, now secret key

upper jolt
#

What do you mean by:

  • earlier - publishable api key
    You could never create a Connection Token with your Publishable Key... that would have removed the security it provided.
sonic shore
#

it was possible during 3.3.0

#

i remember that it was removed for security concerns like u said

#

so im trying to find a proof of where is it in the changelog

#

so that i can present to my product team that secret key is needed for the terminal now

#

can u pls provide that for me? if possible?

#

I would greatly appreciate it

upper jolt
#

I'm looking but I don't believe this was ever possible. Do you have a request ID where you created a Connection Token with your Publishable Key?

sonic shore
#

sorry i got it all wrong

#

the terminology i used is wrong

#

I have a connection token, i got a connection token succesfully

#

but the next step after this is to fetch locations

#

which im not able to

#

can u guess what coudl be the reason?

upper jolt
#

What does "which I'm not able to do" mean?

#

Is there an error?