Small knowledge, big challenge! This article is participating in the creation activity of “Essential Tips for Programmers”.
Origin of the event
Or the company’s cute app, since it is an app there is a pay too much, right? Although it is written in uniapp, it also supports payment, nice.
Open my happy HBuilderX, start my long-constructed DNA, test a wave of happy payment process, select products, select XX pay, enter the APP to pay, and return to the merchant.
APP has crashed. Hmm?? Why did it crash? You’re not my mindset. You’re giving me a mental breakdown.
Apple Pay, UniApp version 3.2.2, Q&A community take a look, is belongs to the update after the SDK problem, IOS under some devices crash, TSK TSK, nice.
However, I was late to the game, and soon patched to version 3.2.3, which was mainly for payment issues, so there were few updates.
You think this is the end of it? No, of course it’s not that simple.
After I spent a lot of money (time is money) updating to 3.2.3 and configuring the Android and IOS dock, I packed offline, booted, and walked.
Payment is paid, return to APP also does not crash, but does not walk the payment completed callback, also does not walk the payment failed callback. It’s not detectable anywhere. In addition to the page’s onShow() hook function.
But that’s not gonna work either. We have to go back. [smiles]
At present, the bug has been submitted to the developer. The last normal version was 3.1.22. I hope you will respect yourself later.