Awful! Knowledge answer PK out of the line bug! Recap and summarize

Awful! Knowledge answer PK out of the line bug! Let me review and summarize.
There are two main problems:
1. Server problem: cloud database watch monitoring error reporting;
2. card bug problem: after the matching is successful or pk starts, someone quits midway;

cloud database watch monitoring error reporting
Regarding the first question, According to user feedback, the watch has frequently and irregularly encountered errors these days: Error: errCode: -402002.


problem found


Now that the problem has been discovered, it has happened occasionally in the past two days. I have tried many times and have not reproduced the problem, so I have no way to locate it for the time being.



First, by consulting the official technical documents, I found that -402002 belongs to "SDK database error: initialization monitoring failed", not a bug in the PK answering applet developed by me or a problem of unstable or poor network quality of the user, which can be ruled out possible. Then there is the problem of the official server.
 


Then, I went to the community and saw that someone had encountered it. Later, by accident, I also encountered this problem. I will give feedback to the official Tencent cloud server manufacturer, and then solve this problem.
The official Tencent cloud server manufacturer also quickly responded and resolved it.


I tried it, and the problem didn't appear. The Tencent cloud server manufacturer officially solved it quickly, and I immediately reported to the user that the problem has been solved, and he also tested it, and the problem did not recur.



After the match is successful or the pk starts, someone quits midway.
According to user feedback, in this pk, one person has successfully matched and started to answer questions, and the other person is still matching, but the person who has successfully matched cannot continue to answer questions. That is, when the match is made, the other party quits or has already started.


Indeed, it is necessary to add the function you mentioned a few days ago to take into account this abnormal operation process.
Most of the 1v1 invitation pk battle answering system I have done before, both parties A and B can choose whether to start or quit before the start. After the match, Party B can choose "Accept", and then Party A can choose "Start", and then start the pk . Therefore, it is almost rarely the case of exiting during the pk, and the probability is very low.
Furthermore, the mechanism of 1v1 invites pk to answer questions is different in that it does not limit the number of pk, and only counts the normal pk based on the normal operation process, so even if some people quit in the middle of the pk, it will not have any impact.


The current 1v1pk answering mechanism or mode is automatic matching. In fact, before the event started, some program logic was modified at the request of the other party.
 


In fact, there are certain risks. After all, the answering pk applet has been launched and is running stably. If there are major changes in a short period of time, it will inevitably cause instability. Because some situations are not covered, the time is short, and there are not enough regression tests, stress tests, and smoke tests.
Although the risk points have been informed to the other party in advance, I also need to bear certain responsibilities, after all, it was developed and built by me. Therefore, we can only carry out strategic repairs for those special cases without affecting the normal use of most people, so as to be as compatible as possible.
 


 


 



 


 


 


 


 


 


Through this review and summary, there are also gains. Although the main program is running normally, when some special circumstances occur, it will affect the user experience. For example, official server problems, unconventional operations of individual users (exit during pk battle), etc.
Official server problems need to be reported to the official immediately for resolution.

The user operation problem can be solved or circumvented in three ways: operation process design, program code control and activity plan adjustment strategy.
The priority is to solve it through the design of the operation process, but this is a major change, which requires sufficient time to preview for modification and adjustment and a large number of tests before the official start of the activity. (Optimal solution)
Secondly, the program code is used to be compatible with various special situations and to block them. However, in this way, some situations may not be thought of before they are encountered, and they will be missed. After all, various mobile phones The model or its mobile phone system will have some particularities. It is also necessary to treat user feedback before learning about it and then solving it. (The next best thing to do)
Also, you can adjust the rules or plans of the event, without limiting the number of times of pk. (suboptimal solution)
 

Guess you like

Origin blog.csdn.net/qq_29528701/article/details/131477868