CN112148597B - Method for eliminating iOS device authorization dialog box, test method and storage medium - Google Patents
Method for eliminating iOS device authorization dialog box, test method and storage medium Download PDFInfo
- Publication number
- CN112148597B CN112148597B CN202010972373.0A CN202010972373A CN112148597B CN 112148597 B CN112148597 B CN 112148597B CN 202010972373 A CN202010972373 A CN 202010972373A CN 112148597 B CN112148597 B CN 112148597B
- Authority
- CN
- China
- Prior art keywords
- application program
- application
- ios device
- eliminating
- hook code
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The application relates to a method for eliminating an iOS device authorization dialog box, a test method and a storage medium, wherein the method for eliminating the iOS device authorization dialog box comprises the following steps: acquiring an ID of a first application program; and replacing the ID of the second application program with the ID of the first application program so that the second application program uses the authorization information of the first application program. The test method comprises the following steps: installing a first application program in the iOS device; setting the authority of the first application program to generate authorization information of the first application program in the iOS device; replacing the ID of the second application program with the ID of the first application program so that the second application program uses the authorization information of the first application program; installing the second application program in the iOS device; the second application is tested using the test script. By the method and the device, the authorization dialog box during the operation of the application program is avoided, and the automatic test is realized.
Description
Technical Field
The present application relates to the field of software testing technologies, and in particular, to a method for eliminating an iOS device authorization dialog box, a testing method, and a storage medium.
Background
On the iOS device, after an application program (APP) is installed, when the APP runs for the first time (but not limited to this), the system pops up various authorization dialog boxes according to resources used by the APP, for example: whether an open location service is running, whether an album can be accessed, whether a cellular network can be used, etc. These dialog boxes are all system-level dialog boxes, and the APP cannot be eliminated by simulating clicks.
In an automated test, if these dialogs are not eliminated, the APP test will be abnormal, thereby terminating the automated test flow.
Disclosure of Invention
To solve the above technical problem or at least partially solve the above technical problem, the present application provides a method, a test method, and a storage medium for eliminating an iOS device authorization dialog.
In a first aspect, the present application provides a method for eliminating an iOS device authorization dialog, comprising: acquiring an ID of a first application program; and replacing the ID of the second application program with the ID of the first application program so that the second application program uses the authorization information of the first application program.
In some embodiments, the method for eliminating an iOS device authorization dialog described above further includes: storing the ID of the second application in a static resource of the second application; injecting a Hook code in the second application, wherein the Hook code is configured to obtain the ID of the second application from the static resource and provide the ID of the second application to the second application.
In some embodiments, the method for eliminating an iOS device authorization dialog described above further includes: installing a first application program in the iOS device; setting the authority of the first application program to generate the authorization information of the first application program in the iOS device.
In some embodiments, the method for eliminating an iOS device authorization dialog described above further includes: modify a load command (loadcommand) list of a map-o (Mach object) file to cause the Hook code to be loaded preferentially.
In some embodiments, injecting Hook code in the second application includes: the Hook code is put into the arbitrary class + load method of the second application.
In a second aspect, the present application provides a testing method, comprising: installing a first application program in the iOS device; setting the authority of the first application program to generate authorization information of the first application program in the iOS device; replacing the ID of the second application program with the ID of the first application program so that the second application program uses the authorization information of the first application program; installing the second application program in the iOS device; the second application is tested using the test script.
In some embodiments, before installing the second application in the iOS device, further comprising: storing the ID of the second application in a static resource of the second application; injecting a Hook code in the second application, wherein the Hook code is configured to obtain the ID of the second application from the static resource of the second application and provide the ID of the second application to the second application.
In some embodiments, the testing method further comprises: the loadcommand list of the map-o file is modified so that the Hook code is loaded preferentially.
In some embodiments, injecting Hook code in the second application includes: the Hook code is put into the arbitrary class + load method of the second application.
In a third aspect, the present application provides a computer readable storage medium having stored thereon a program for eliminating an iOS device authorization dialog, which when executed by a processor implements the steps of a method of eliminating an iOS device authorization dialog.
Compared with the prior art, the technical scheme provided by the embodiment of the application has the following advantages: according to the method provided by the embodiment of the application, the ID of the second application program is replaced by the ID of the first application program, so that the iOS device can use the authorization information of the first application program when the second application program is tested, the permission of the second application program does not need to be set, an authorization dialog box does not exist during running, and the automatic test is facilitated.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without inventive exercise.
FIG. 1 is a flowchart of one embodiment of a method for eliminating an iOS device authorization dialog box according to an embodiment of the present invention;
FIG. 2 is a flow chart of one embodiment of a testing method provided in an embodiment of the present application; and
fig. 3 is a hardware schematic diagram of an implementation manner of a computer device according to an embodiment of the present application.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
In the following description, suffixes such as "module", "component", or "unit" used to denote elements are used only for facilitating the explanation of the present invention, and have no specific meaning in itself. Thus, "module", "component" or "unit" may be used mixedly.
On iOS devices (e.g., apple smart devices such as iPhone, iPad, etc.), when APP uses restricted resources (e.g., private data and tariff related resources), a dialog box pops up for the user to confirm. After the user sets the authority, the iOS system records the authorization information of each APP, and stores the authorization information of the APP and the unique identifier (also called bundleID, application ID, etc.) of the APP into a local database of the iOS device. Due to sandbox limitations, the APP cannot access the database.
When the APP runs, if a certain limited resource is used, the iOS system firstly queries a database, if authorization information corresponding to the ID of the APP exists, execution is carried out according to authorization, and if the authorization information does not exist, a dialog box is popped up. When the APP is unloaded, all the authorization information related to the APP is deleted.
The embodiment of the present application provides a method for eliminating an iOS device authorization dialog, as shown in fig. 1, the method includes steps S102 to S104.
Step S102, obtaining the ID of the first application program.
Step S104, replacing the ID of the second application program with the ID of the first application program so that the second application program can use the authorization information of the first application program.
By the method provided by the embodiment of the application, the ID of the second application program is replaced by the ID of the first application program, so that the iOS device can use the authorization information of the first application program when the second application program is tested, the permission of the second application program does not need to be set, an authorization dialog box is not required during running, and the automatic test is facilitated.
In the embodiment of the application, the second application program with the replaced ID is obtained by unpacking, packing and re-signing the second application program.
In some cases, the application itself needs to use the ID (e.g., the service side of the application may verify the ID of the application), and some functions of the application may be affected after replacing the ID, so that, in some embodiments, the method for eliminating the iOS device authorization dialog described above further includes: storing the ID of the second application in a static resource of the second application; injecting a Hook code in the second application, wherein the Hook code is configured to obtain the ID of the second application from the static resource and provide the ID of the second application to the second application. Thus, when the internal code of the second application gets the application ID (e.g., but not limited to, the application checks its own ID or sends the ID to the server), the Hook code returns the original ID instead of the ID of the first application.
In some embodiments, the first application is installed in the iOS device prior to installing or testing the second application; the authority of the first application is set to generate authorization information of the first application in the iOS device. Typically, the permissions of the second application are a subset of the permissions of the first application, but are not so limited.
In order for the second application to obtain its original ID, in some embodiments, the loadcommand list of the map-o file is modified so that the Hook code is loaded preferentially. In some embodiments, the loadcommand list of the map-o file is modified so that the Hook code is loaded first, but embodiments of the present application are not so limited.
Since + load is the automatic, earliest execution once a library is loaded, in some embodiments Hook code is injected in the second application, including: the Hook code is put into the arbitrary class + load method of the second application.
The embodiment of the present application further provides a testing method, as shown in fig. 2, the testing method includes steps S202 to S210.
In step S202, a first application is installed in the iOS device.
Step S204, the authority of the first application program is set so as to generate the authorization information of the first application program in the iOS device.
In step S206, the ID of the second application is replaced with the ID of the first application, so that the second application uses the authorization information of the first application.
In step S208, the second application is installed in the iOS device.
Step S210, the second application is tested using the test script.
By the method provided by the embodiment of the application, the ID of the second application program is replaced by the ID of the first application program, so that the iOS device can use the authorization information of the first application program when the second application program is tested, the permission of the second application program does not need to be set, an authorization dialog box is not required during running, and the automatic test is facilitated.
In some embodiments, before installing the second application in the iOS device, further comprising: storing the ID of the second application in a static resource of the second application; injecting a Hook code in the second application, wherein the Hook code is configured to obtain the ID of the second application from the static resource of the second application and provide the ID of the second application to the second application. Thus, when the internal code of the second application gets the application ID (e.g., but not limited to, the application checks its own ID or sends the ID to the server), the Hook code ensures that the original ID is returned instead of the ID of the first application.
In order for the second application to obtain its original ID, in some embodiments, the loadcommand list of the map-o file is modified so that the Hook code is loaded preferentially. In some embodiments, the loadcommand list of the map-o file is modified so that the Hook code is loaded first, but embodiments of the present application are not so limited.
In some embodiments, injecting Hook code in the second application includes: the Hook code is put into the arbitrary class + load method of the second application, but is not limited thereto.
The embodiment also provides a computer device, such as a smart phone, a tablet computer, a notebook computer, a desktop computer, a rack server, a blade server, a tower server or a rack server (including an independent server or a server cluster composed of a plurality of servers) capable of executing programs, and the like. The computer device 20 of the present embodiment includes at least, but is not limited to: a memory 21, a processor 22, which may be communicatively coupled to each other via a system bus, as shown in FIG. 3. It is noted that fig. 3 only shows the computer device 20 with components 21-22, but it is to be understood that not all shown components are required to be implemented, and that more or fewer components may be implemented instead.
In the present embodiment, the memory 21 (i.e., a readable storage medium) includes a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, and the like. In some embodiments, the storage 21 may be an internal storage unit of the computer device 20, such as a hard disk or a memory of the computer device 20. In other embodiments, the memory 21 may also be an external storage device of the computer device 20, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), or the like, provided on the computer device 20. Of course, the memory 21 may also include both internal and external storage devices of the computer device 20. In this embodiment, the memory 21 is generally used for storing an operating system and various types of application software installed in the computer device 20, such as program codes of a method for eliminating an iOS device authorization dialog box, a test method, and the like. Further, the memory 21 may also be used to temporarily store various types of data that have been output or are to be output.
Processor 22 may be a Central Processing Unit (CPU), controller, microcontroller, microprocessor, or other data Processing chip in some embodiments. The processor 22 is typically used to control the overall operation of the computer device 20. In this embodiment, the processor 22 is configured to execute the program code stored in the memory 21 or process data, for example, the program code of the method for eliminating the iOS device authorization dialog box and the test method, so as to implement the method for eliminating the iOS device authorization dialog box and the test method.
The present embodiment also provides a computer-readable storage medium, such as a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, a server, an App application mall, etc., on which a computer program is stored, which when executed by a processor implements corresponding functions. The computer-readable storage medium of the present embodiment is used for storing an index time-series abnormality detection program, and when executed by a processor, implements the method of eliminating the iOS device authorization dialog box, and the steps of the test method.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.
Claims (8)
1. A method of eliminating an iOS device authorization dialog for testing of a second application, comprising:
acquiring an ID of a first application program;
replacing the ID of the second application program with the ID of the first application program, so that the iOS device uses the authorization information of the first application program to authorize the second application program when running the second application program; and
storing the ID of the second application in a static resource of the second application;
and injecting a Hook code into the second application program, wherein the Hook code is configured to acquire the ID of the second application program from the static resource and provide the ID of the second application program to the second application program when the internal code of the second application program acquires the ID of the second application program.
2. The method of claim 1, further comprising:
installing a first application program in the iOS device;
setting the authority of the first application program to generate the authorization information of the first application program in the iOS device.
3. The method of claim 1, further comprising:
and modifying the loadcommand list of the map-o file so that the Hook code is loaded preferentially.
4. The method of claim 1 or 3, wherein injecting Hook code in the second application comprises:
the Hook code is put into the arbitrary class + load method of the second application.
5. A method of testing, comprising:
installing a first application program in the iOS device;
setting the authority of the first application program to generate authorization information of the first application program in the iOS device;
replacing the ID of the second application program with the ID of the first application program, so that the iOS device uses the authorization information of the first application program to authorize the second application program when running the second application program;
installing the second application in the iOS device;
testing the second application using a test script;
wherein the content of the first and second substances,
before installing the second application in the iOS device, further comprising:
storing the ID of the second application in a static resource of the second application;
and injecting a Hook code into the second application program, wherein the Hook code is configured to acquire the ID of the second application program from the static resource and provide the ID of the second application program to the second application program when the internal code of the second application program acquires the ID of the second application program.
6. The test method of claim 5, further comprising:
and modifying the loadcommand list of the map-o file so that the Hook code is loaded preferentially.
7. The test method according to claim 5 or 6, characterized in that injecting Hook code in the second application program comprises:
the Hook code is put into the arbitrary class + load method of the second application.
8. A computer-readable storage medium, having stored thereon a program for eliminating an iOS device authorization dialog, the program for eliminating an iOS device authorization dialog, when executed by a processor, implementing the steps of the method for eliminating an iOS device authorization dialog as claimed in any of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010972373.0A CN112148597B (en) | 2020-09-16 | 2020-09-16 | Method for eliminating iOS device authorization dialog box, test method and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010972373.0A CN112148597B (en) | 2020-09-16 | 2020-09-16 | Method for eliminating iOS device authorization dialog box, test method and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112148597A CN112148597A (en) | 2020-12-29 |
| CN112148597B true CN112148597B (en) | 2021-12-10 |
Family
ID=73892961
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010972373.0A Active CN112148597B (en) | 2020-09-16 | 2020-09-16 | Method for eliminating iOS device authorization dialog box, test method and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112148597B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113076258B (en) * | 2021-04-21 | 2023-09-19 | ***通信集团陕西有限公司 | Method, device and equipment for applying permission and readable storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105468405A (en) * | 2015-11-18 | 2016-04-06 | 深圳市创想天空科技股份有限公司 | Installation processing method and device of application program |
| CN105786551A (en) * | 2014-12-26 | 2016-07-20 | 北京元心科技有限公司 | Application program operation access control method and system |
| CN110321669A (en) * | 2019-06-04 | 2019-10-11 | 平安科技（深圳）有限公司 | Method, apparatus, equipment and the storage medium that application program is signed again |
| CN111177710A (en) * | 2019-12-31 | 2020-05-19 | 维沃移动通信有限公司 | Application authorization method, electronic device and storage medium |
Family Cites Families (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050262487A1 (en) * | 2004-05-11 | 2005-11-24 | International Business Machines Corporation | System, apparatus, and method for identifying authorization requirements in component-based systems |
| CN102467642B (en) * | 2010-11-17 | 2015-02-25 | 北大方正集团有限公司 | Permission control method and device for application software |
| CN103123605B (en) * | 2013-02-07 | 2018-12-14 | 百度在线网络技术（北京）有限公司 | A kind of Android platform automatic integration test method and device |
| US9378119B2 (en) * | 2014-09-17 | 2016-06-28 | Verizon Patent And Licensing Inc. | Release template |
| CN104283953B (en) * | 2014-09-30 | 2017-08-11 | 清华大学 | A kind of position information share system and sharing method |
| CN105303071B (en) * | 2015-09-18 | 2018-06-12 | 许继集团有限公司 | A kind of embedded device program authorization guard method |
| CN105574369A (en) * | 2015-12-14 | 2016-05-11 | 网易（杭州）网络有限公司 | Method, device and system for re-signing application program |
| CN106126290B (en) * | 2016-06-27 | 2019-08-13 | 微梦创科网络科技（中国）有限公司 | Application program optimization method, apparatus and system |
| US10346290B2 (en) * | 2016-10-31 | 2019-07-09 | International Business Machines Corporation | Automatic creation of touring tests |
| CN106845162B (en) * | 2016-12-20 | 2020-05-26 | 北京五八信息技术有限公司 | Re-signing method and device |
| CN108337540B (en) * | 2017-01-20 | 2021-11-23 | 中兴通讯股份有限公司 | Authorization management method, device and system |
| CN107544811B (en) * | 2017-09-08 | 2020-07-31 | 武汉斗鱼网络科技有限公司 | Method, storage medium, electronic device and system for hiding dylib file in IOS platform |
| CN108089880A (en) * | 2017-12-28 | 2018-05-29 | 北京奇虎科技有限公司 | The method, apparatus and server pre-processed to application program installation file |
| CN109995534B (en) * | 2017-12-29 | 2022-04-26 | 北京京东尚科信息技术有限公司 | Method and device for carrying out security authentication on application program |
| CN110209578B (en) * | 2019-05-21 | 2022-07-08 | 苏州浪潮智能科技有限公司 | Information online test platform |
-
2020
- 2020-09-16 CN CN202010972373.0A patent/CN112148597B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105786551A (en) * | 2014-12-26 | 2016-07-20 | 北京元心科技有限公司 | Application program operation access control method and system |
| CN105468405A (en) * | 2015-11-18 | 2016-04-06 | 深圳市创想天空科技股份有限公司 | Installation processing method and device of application program |
| CN110321669A (en) * | 2019-06-04 | 2019-10-11 | 平安科技（深圳）有限公司 | Method, apparatus, equipment and the storage medium that application program is signed again |
| CN111177710A (en) * | 2019-12-31 | 2020-05-19 | 维沃移动通信有限公司 | Application authorization method, electronic device and storage medium |
Non-Patent Citations (3)
| Title |
|---|
| Android (Nougats) security issues and solutions;Shahid Iqbal;《2018 IEEE International Conference on Applied System Invention (ICASI)》;20180625;1-2 * |
| Masque Attack Spoofs Apps, Bypasses Privacy Protection;Trend Micro;《https://www.trendmicro.com/en_us/research/16/j/ios-masque-attack-spoof-apps-bypass-privacy-protection.html》;20161031;1-6 * |
| 基于JSON Web签名的Web安全研究;GOGOE VIDJINNAGNI PAUL;《中国优秀硕士学位论文全文数据库 信息科技辑》;20171215;I139-90 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112148597A (en) | 2020-12-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110597531B (en) | Distributed module upgrading method and device and storage medium | |
| CN105867947A (en) | Data processing method and device after upgrades of preset applications | |
| CN103826215A (en) | Method and apparatus for carrying out root authority management at terminal equipment | |
| CN109815680B (en) | Application authority management method and device, terminal equipment and storage medium | |
| CN110515795B (en) | Big data component monitoring method and device and electronic equipment | |
| CN111263354B (en) | OTA differential upgrading method and device | |
| CN107908553B (en) | Association testing method, application server and computer readable storage medium | |
| CN111181975A (en) | Account management method, device, equipment and storage medium | |
| CN111159595A (en) | Page loading method, system, computer equipment and computer readable storage medium | |
| CN109710286B (en) | System upgrading method, device, equipment and storage medium | |
| CN111460496A (en) | Permission configuration method based on user role, electronic device and storage medium | |
| CN112148597B (en) | Method for eliminating iOS device authorization dialog box, test method and storage medium | |
| CN111026080A (en) | Hardware-in-loop test method and device for controller | |
| CN110597662B (en) | Backup data automatic verification method and device, user equipment and storage medium | |
| CN110750434A (en) | Interface testing method and device, electronic equipment and computer readable storage medium | |
| CN113259397B (en) | Method, device and equipment for executing plan and readable storage medium | |
| US20160004850A1 (en) | Secure download from internet marketplace | |
| CN112559352A (en) | Interface test method, device, equipment and storage medium | |
| CN111046377B (en) | Method and device for loading dynamic link library, electronic equipment and storage medium | |
| CN111159985B (en) | Data deriving method, apparatus, computer device and computer readable storage medium | |
| CN112685077A (en) | Data modification method, system, computer device and computer readable storage medium | |
| CN109429260A (en) | A kind of method of calibration and device of northbound data | |
| CN109492144B (en) | Association relation analysis method, device and storage medium for software system | |
| CN110837500A (en) | Data screening method and device based on local embedded window and computer equipment | |
| CN112698842A (en) | Method and device for acquiring additional information of application program |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |