Problems encountered in the development, to share with everyone, if there is a correction, no good.

[UIKBBlurredKeyView candidateList] [UIKBBlurredKeyView candidateList]

The application updated last week went online this week, and then my colleague told me yesterday that the crash rate of the information on Umeng was more than 1%, so please check it quickly. [UIKBBlurredKeyView candidateList]: unrecognized selector sent to instance… “And searched it

Crash recur:

Switch to the input area, click input, switch input method to handwritten input method (system, third party fine), then enter, enter one, the second word will crash.

The reason:

Because UIScrollView added a category, is used to handle the event of clicking the screen (touch screen recycling keyboard), it has always done so before, there is no problem, or no one feedback, 😓, it is estimated that there is no door to complain ah… And we didn’t test handwriting, because no one thought it would be any different. Apple didn’t think of it either, so we went live and crashed… This sucks

Solution:

Since you have this problem, you need to fix it, and the worst thing about using this category is that even if you don’t import this header file, you can crash it in other inputs… So the problem is very serious!! The solution is as simple as deleting the category and using this blog [UIKBBlurredKeyView candidateList]: Unrecognized selector sent to instance 0x177CC850.

2. The webView to load the web appeared this, NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, – 9813)

Yesterday, I added an entrance to an interface and clicked to jump to a web page, so I needed to bring the login status to the web page. After finishing the work, I tested it today and found that there was no problem with the jumping web page, but it could not be added to the shopping cart. I clicked the personal center in the label below the web page and there was no response.

Location reason:

See how android displays, whether it can jump, all working… Then start to check: a. Is the login status not uploaded to the web page? B. It is not a mobile phone problem, the url can be opened directly from the browser after these two exclusion, there is no way, C. Step through the print and see the difference between the urls that work and those that don’t. There is a real difference, the normal redirect is HTTP request, and the personal center is also HTTP, but after the request there is a redirect (automatic redirect), to HTTPS; Then there is a problem, go webView load failed method, print error is

NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9813) 

Copy the code

So, why? Look at the status of this HTTPS link in the browser, it shows that the link is not safe because the certificate has expired. D. Baidu, well, don’t make so much noise, it’s Baidu…

Conclusion:

Because the certificate for the test environment seems to have been created by the background and expired, so there’s this problem,

Solutions:

There are three solutions to this point: one is the background update certificate, find a good certificate can be trusted to put over; The second is that the client changes the code to screen out the unsafe one; But it’s a good idea to distinguish between live and test, and remove these when live, otherwise the HTTPS is meaningless. And the last one is, we don’t change it, we don’t test it, it’s fine online anyway… 😄 Don’t ask me which…

If the client to modify the reference iOS UIWebView loads HTTPS site appears NSURLConnection/CFURLConnection HTTP load failed (kCFStreamE… Well, I haven’t tried that. It’s like giving away something…