#wilcalaf_api
1 messages ¡ Page 1 of 1 (latest)
đ 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/1280473802161127424
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
hi! can you try v3.8.1 of the SDK?
ah we had to pull that release for an unrelated reason
ill try now
but in any case I can see we're aware of this issue already and there is a fix, it will be in the next release
should be this week, yesterday was a holiday in the US so that's delayed things a bit, plus we had an unrelated issue deploying 3.8.1 so it's going to be what the team is working on when they're back
so upgrading now to 3.8.1 probably wont solve the issue?
well you can't upgrade to 3.8.1. that release was pulled down for an unrelated issue in it
but the next release will include the fix for this issue
mmm sorry i got confused. first you asked me if i can try 3.8.1 - how can i try it then?
ahhh and then you wrote that you had to pull that
sorry i tought you ment, pull as of release not as pull down
you can't, I was mistaken. I looked up some details internally and saw we identified this issue last week and pushed a fix for it in 3.8.1, so I told you that. Then I looked more closely and apparently we had to pull that release late on Friday night due to an issue with it. So it will be cleaned up in US time this week and a new release cut.
where can i keep updated on when this will be released?
I pinged the team working on this to express the urgency and that it's affecting you since I think we didn't realise this VerifyError was widespread
I don't know to be honest, but worth a try!
mmm
i tried upgrading on my build.gradle
to 3.8.1
and it worked
altough its not on github it seems to be on maven
but do you think it is safe to use? since you said you have to pull it for another reason. i dont want to break something else lol
safe to use
What are you concerned about exactly?
well karllekko said you had to remove that release for some reason
thats why its not on github
so im wondering since you removed it, if its safe to use
Ok. My colleague suggested that the fix for your issue will be available in the next release. It was available in 3.8.1 but it was taken down, however, the next release, that will come out somewhere this week will have the fix you need.
Basically, if you could wait for a few days, you can just use the upcoming release.
the release was taken down for security reasons and I can't say more than that, I'd recommend waiting for the official release
yeah but also the latest PR is a revert of the release
but yes it might still be accessible, it's hard to pull stuff from all the open source repos, like I said this was all a Friday night escalation
ok so its not safe to use 3.8.1 basically you reccomend waiting for next release
regardless the official answer we're giving you is : We're aware of the issue, we know the fix, we will officially release it ASAP so watch for that release
thanks
This thread has been archived. If you need help with anything else please ask in #dev-help or contact Stripe Support: https://support.stripe.com/contact
Find help and support for Stripe. Our support site provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.