#gaz_code
frozen meteorBOT
👋 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/1329804459265757277
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- gaz_code, 8 minutes ago, 79 messages
torn dagger
hey i found it
release apks the secret is null
non release it is not
ive been sending him release ones but running mine from Android studio
soon as i use release its same
frozen meteorBOT
torn dagger
so the error is Execution error while retrieving connection token
due to result.body()!!.secret == null
torn dagger
no
need to be able to use release apks!
locationCallback.onFailure exception is Execution error while retrieving connection token
modern kestrel
so the error is Execution error while retrieving connection token
Yeah that was the API error I shaerd before. Looks like their build passes the wrong key
torn dagger
but where is the key specified? i dont recall specifying one
its probably because im in test mode etc too
my app doesnt include either key
tall chasm
due to result.body()!!.secret == null
This means that your App isn't able to get a response
torn dagger
or is it the key from the stripe terminal backend?
yes
a yes its form the backend!
tall chasm
Yes, you should use your secret key and not your publishable key in your backend
torn dagger
yeh im not using the publishable one
but the one im using is sk_test
starts with sk_test
tall chasm
No according to the requestId you've shared req_oRapf9se9qAPJ5 you are passing a publishable key
I encourage you to debug your integration and make sure you are making the correct call
torn dagger
how can u see the key?
and where did req_oRapf9se9qAPJ5 come from?
its not in my logs
tall chasm
Can you share your AccountId?
result.body()!!.secret == null
What is the response you got from this API call.
torn dagger
ow do i get my acocutn id again?
tall chasm
isn't this?
#1329779906564980781 message
tall chasm
And what is the API response content ?
tall chasm
and where did req_oRapf9se9qAPJ5 come from?
Please make sure that you are using the secret key in your backend API keys and not the publishable.
I strongly encarge you to debug your integration and inspect each call and see what key you are using.
torn dagger
backend shows STRIPE_TEST_SECRET_KEY sk_test_eetcetc
so basically in test mode it must use STRIPE_TEST_SECRET_KEY
and only work in debug
but in release you must need a different key and value
its because i used the backend supplied i gues,s didnt read code
it just says use STRIPE_TEST_SECRET_KEY={YOUR_API_KEY}
no where does it say how else to confingure the keys
tall chasm
I don't know about what backend you are referring to, sorry I don't have access to your code.
If you aren't the maintainer of the backend, I invite you to reach out to the maintainer and make sure not to use the publishable key
torn dagger
ye no one at stripe seems to realise that they are recommending and supplying this backend
tall chasm
Thanks for sharing this. So in production instead of setting the secret key as a var env you are setting a publishable key then.
Check your env vars
tall chasm
Happy to help!