WO2019071927A1

WO2019071927A1 - Authorization information obtaining method and apparatus, electronic device, and readable storage medium

Info

Publication number: WO2019071927A1
Application number: PCT/CN2018/081384
Authority: WO
Inventors: 张磊; 张文明; 陈少杰
Original assignee: 武汉斗鱼网络科技有限公司
Priority date: 2017-10-09
Filing date: 2018-03-30
Publication date: 2019-04-18
Also published as: CN107679373B; CN107679373A

Abstract

An authorization information obtaining method and apparatus, an electronic device, and a readable storage medium provided in the present application. The method comprises: a first application invokes, according to description information, a first protocol preset in the electronic device to implicitly open a start page predefined in a second application; when the second application obtains an authorization code before being closed, generate authorization feedback data according to the authorization code; and after the second application is closed, feed the authorization feedback data back to the first application by means of a second protocol, thereby enabling the first application to obtain authorization information of the second application. The function of allowing the second application to send the feedback data to the first application after the second application is started by the first protocol is skillfully applied, so that a coupling relationship between the applications is reduced, and the efficiency of communication between the applications is effectively improved. Furthermore, the first protocol is a system-level protocol with higher security.

Description

Authorization information acquisition method, device, electronic device and readable storage medium

This application claims the priority of the Chinese Patent Application No. 201710928685.X entitled "Authorization Information Acquisition Method, Apparatus and Electronic Device" filed on October 09, 2017, the entire contents of which are incorporated herein by reference. In the application.

Technical field

The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, an electronic device, and a readable storage medium for obtaining authorization information.

Background technique

Authorized logins for different applications are usually required before interacting between different applications. Authorized login is essentially a data communication between two applications. In the prior art, the way to communicate between two applications is usually implemented by adopting the Android Interface Definition Language (AIDL).

However, the method of inter-process communication by means of AIDL has the following drawbacks: When AIDL changes, both applications need to change and upgrade the AIDL file at the same time, so that inter-process communication can be performed. This causes the coupling relationship between the two applications to be too tight. Once a party application upgrades the AIDL file and the other application does not upgrade the AIDL file, it will cause an abnormal situation such as communication failure between the two applications.

Summary of the invention

The purpose of the present application is to provide a method, an apparatus, an electronic device, and a readable storage medium for obtaining authorization information to improve the above problem.

In order to achieve the above object, the technical solution adopted by the embodiment of the present application is as follows:

In a first aspect, the embodiment of the present application provides a method for acquiring authorization information, which is applied to an electronic device, where the plurality of applications are stored in the electronic device, where the method includes: the first application obtains the second application in response to the user operation. Corresponding description information; the first application invokes a first protocol preset in the electronic device according to the description information, and implicitly opens a predefined startup page in the second application, where the The first protocol is configured to implement an application process corresponding to the description information and allow the application process to be closed to feed back data to the first application, where the feedback data is the second application Generating data generated after the page is started; when the second application acquires the authorization code before the second application is closed, generating authorization feedback data according to the authorization code, wherein the feedback data includes authorization feedback data; After the second application is closed, the authorization feedback data is fed back to the device through a preset second protocol. a first application, so that the first application acquires authorization information of the second application, where the second protocol is used to implement the feedback of the feedback data after the second application is closed to allow the feedback to be received Data application.

In a second aspect, the embodiment of the present application further provides an authorization information acquiring apparatus, which is applied to an electronic device, where the electronic device stores a plurality of application programs, where the device includes: a first acquiring module, a starting module, a generating module, and Feedback module. The first obtaining module is configured to: obtain, by the first application, the description information corresponding to the second application in response to the user operation; the startup module, configured to invoke, in the electronic device, the electronic device according to the description information Setting a first protocol, implicitly opening a predefined startup page in the second application, wherein the first protocol is used to implement launching an application process corresponding to the description information and allowing the application process After the closing, the data is fed back to the first application, wherein the feedback data is data generated after the second application launch page is started; and the generating module is configured to: when the second application is in the When the authorization code is obtained before the application is closed, the authorization feedback data is generated according to the authorization code, where the feedback data includes authorization feedback data, and the feedback module is configured to: after the second application is closed, pass the preset The second protocol feeds back the authorization feedback data to the first application, so that the first application acquires the second application Program authorization information, wherein the second protocol for implementing closed after the second application to the feedback data is transmitted to allow the feedback received application data.

In a third aspect, an embodiment of the present application further provides an electronic device, where the electronic device includes: a memory; a processor; and an authorization information acquiring device, where the authorization information acquiring device is stored in the memory and includes one or more a software function module executed by the processor, comprising: a first acquiring module, configured to acquire, by the first application, the description information corresponding to the second application in response to the user operation; and the startup module is configured to be used by the first application The program, according to the description information, invokes a first protocol preset in the electronic device, and implicitly opens a predefined startup page in the second application, where the first protocol is used to implement startup and the Describe the application process corresponding to the information and allow the application process to be closed to feed back data to the first application, wherein the feedback data is data generated after the second application launch page is started; generating module And when the second application acquires an authorization code before the second application is closed, according to the granting Code generation authorization feedback data, wherein the feedback data includes authorization feedback data; and a feedback module, after the second application is closed, feeding back the authorization feedback data to the first through a preset second protocol An application, so that the first application acquires authorization information of the second application, where the second protocol is configured to implement, after the second application is closed, the feedback data is delivered to the data that is allowed to receive the feedback data. application.

In a fourth aspect, the embodiment of the present application further provides a readable storage medium, where the readable storage medium includes a computer program, where the computer program controls the electronic device where the readable storage medium is located to perform the first aspect. The method of obtaining authorization information.

Compared with the prior art, the present application provides an authorization information acquisition method, apparatus, electronic device, and readable storage medium. The first application opens the second application in an implicitly initiated manner according to the description information and the first protocol. After clever application of the first protocol to start the second application, the function of allowing the second application to send feedback data to the first application replaces the prior art using AIDL service for data communication, thereby reducing the application between Coupling relationship. Effectively improve the efficiency of communication between applications. At the same time, the first protocol is a system-level protocol, which is more secure and more reliable.

The above described objects, features, and advantages of the present invention will become more apparent from the following description.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings to be used in the embodiments will be briefly described below. It should be understood that the following drawings show only certain embodiments of the present application, and therefore It should be seen as a limitation on the scope, and those skilled in the art can obtain other related drawings according to these drawings without any creative work.

FIG. 1 is a block schematic diagram of an electronic device provided by an embodiment of the present application.

FIG. 2 is a part of a flow chart showing the steps of the method for acquiring authorization information provided by the preferred embodiment of the present application.

FIG. 3 shows another part of the flow chart of the steps of the method for acquiring authorization information provided by the preferred embodiment of the present application.

FIG. 4 is a schematic diagram of an authorization information acquiring apparatus provided by a preferred embodiment of the present application.

Icon: 100-electronic device; 101-memory; 102-storage controller; 103-processor; 200-authorization information acquisition device; 201-first acquisition module; 202-activation module; 203-generation module; 204-feedback module ; 205 - parsing module; 206 - second acquiring module; 207 - adding module.

Detailed ways

The technical solutions in the embodiments of the present application are clearly and completely described in the following with reference to the drawings in the embodiments of the present application. It is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. The components of the embodiments of the present application, which are generally described and illustrated in the figures herein, may be arranged and designed in various different configurations. The detailed description of the embodiments of the present application, which is set forth in the accompanying drawings, is not intended to limit the scope of the claims All other embodiments obtained by a person skilled in the art based on the embodiments of the present application without creative efforts are within the scope of the present application.

It should be noted that similar reference numerals and letters indicate similar items in the following figures. Therefore, once an item is defined in one figure, it is not necessary to further define and explain it in the subsequent figures. Also, in the description of the present application, the terms "first", "second", and the like are used merely to distinguish a description, and are not to be construed as indicating or implying a relative importance.

Please refer to FIG. 1 , which is a block diagram of an electronic device 100 according to an embodiment of the present application. The electronic device 100 can be, but is not limited to, a smart phone, a tablet computer, a laptop portable computer, a car computer, a personal digital assistant (PDA), a wearable mobile terminal, and the like. The electronic device 100 is installed with an iOS system including an authorization information acquisition device 200, a memory 101, a storage controller 102, and a processor 103.

The components of the memory 101, the memory controller 102, and the processor 103 are electrically connected directly or indirectly to each other to implement data transmission or interaction. For example, the components can be electrically connected to one another via one or more communication buses or signal lines. The authorization information obtaining apparatus 200 includes at least one software function module or installation that can be stored in the memory 101 or is solidified in an operating system (OS) of the electronic device 100 in the form of software or firmware. An application in the electronic device 100. The processor 103 is configured to execute an executable module stored in the memory 101, such as a software function module or a computer program included in the authorization information acquiring device 200.

The memory 101 may be, but not limited to, a random access memory (RAM), a read only memory (ROM), and a programmable read-only memory (PROM). Erasable Programmable Read-Only Memory (EPROM), Electric Erasable Programmable Read-Only Memory (EEPROM), and the like. The memory 101 is used to store a program, and the processor 103 executes the program after receiving the execution instruction. The method executed by the server defined by the process disclosed in any embodiment of the present application may be applied to the processor 103. Or implemented by the processor 103.

The processor 103 can be an integrated circuit chip with signal processing capabilities. The processor 103 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), a voice processor, a video processor, etc., and may also be a digital signal processor. ASIC, field programmable gate array or other programmable logic device, discrete gate or transistor logic device, discrete hardware component. The methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general purpose processor may be a microprocessor or the processor 103 may be any conventional processor 103 or the like.

First embodiment

Please refer to FIG. 2. FIG. 2 is a flowchart of a method for acquiring authorization information provided by a preferred embodiment of the present application. The authorization information acquisition method is applied to the electronic device 100 in FIG. 1 . The electronic device 100 stores a plurality of applications, and the authorization information acquisition method includes the following steps:

Step S201: Obtain description information corresponding to each of the applications.

In this embodiment, the description information corresponds to an application to facilitate searching for a corresponding application by using the description information. The description information may be information describing the function of the application, for example, the retrieval is used as the description information of the browsing application; of course, the description information may also be the application package name. In this embodiment, each application package name is used as the description information of the corresponding application, wherein the package name of each application is unique in the electronic device 100.

Step S202, adding the description information to a description file of the corresponding application.

In this embodiment, a launch page for launching an authorization is created in each application. The startup page includes a description file. Add the description information to the corresponding description file. It should be noted that the description file can be a setting file, which is essentially an XML file.

As an implementation manner of this embodiment, a filter intent-filter may be added in the description file, and then a filtering method Action class is added in the filter, where the Action class is a bridge between the user request and the business logic. Each Action acts as a business agent for the customer. The Action event can be <action android:name="com.xxx.xxx.getuserinfo">, where com.xxx.xxx.getuserinfo is the descriptive information. When the activity corresponding to the filtering method Action corresponding to the application appears, the Activity is an application component, which is used to provide a screen, which can be used to interact to complete a certain task, that is, when the system corresponding Action event corresponding to the application appears. At that time, you can start the application's startup page.

As shown in FIG. 3, the method for acquiring authorization information provided in this embodiment further includes the following steps:

Step S101: The first application acquires the description information corresponding to the second application in response to the user operation.

A plurality of applications are installed in the electronic device 100, and the description information of the second application is acquired in response to the user operation during the running of the first application. In this embodiment, the description of the second application may be the package name of the second application in response to the user operation.

Step S102: The first application invokes a first protocol preset in the electronic device 100 according to the description information, and implicitly opens a preset startup page in the second application.

In this embodiment, the first protocol is used to implement an application process corresponding to the description information and allow data to be fed back to the first application after the application process is closed, wherein the feedback is The data is data generated by the startup page of the second application after startup. Optionally, the first protocol may include a startActivityforResult function. In the startActivityforResult function, the startup page of the second application corresponding to the description information is opened in an implicitly started manner.

In this embodiment, in order to enable the second application to be launched by means of implicit startup, it is necessary to define a page in the second application and in the description file of the page (for example, AndroidManifest.xml file) An implicitly launched page defines an implicit entry. Specifically, by adding a filter intent-filter and then adding a filtering method Action in the filter, wherein the specific content of the Action can be <action android:name="com.xxx.xxx.getuserinfo"/>, such that The Activity in the application will filter out the custom action object. When the system has the custom action object, the page can be started. Where com.xxx.xxx.getuserinfo is the package name of the application. Since there are no two applications with the same package name in the same system, the uniqueness of com.xxx.xxx.getuserinfo can be ensured.

In this embodiment, the intent class is used to make a relationship between the two activities. Specifically, the intent class can be used to start another Activity in an Activity; or use an intent to transfer data between activities.

As an implementation manner of this embodiment, when the first application is running, an instance of the Intent object is obtained by constructing a method in the Intent class, and then by calling addAction ("com.xxx.xxx.getuserinfo") in the intent. The method adds an action event to the Intent object, and then adds an action description of the Intent object by calling intent.addAction("android.intent.action.VIEW"). In this embodiment, the action is described as obtaining authorization. Through the above two steps, the startup page of the action class android.intent.getuserinfo is opened. The startup page is then opened in the first application by calling the startActivityforResult(intent) method. It should be noted that the startActivityforResult function can only be applied to the startup between processes in the same application. In this embodiment, the implicit start method is combined with the startActivityforResult function to overcome the startActivityforResult function is limited to the same application. The limitation of the use in the middle, at the same time, because the startActivityforResult function can enable the feedback data after the startup page is closed, and thus realize the data interaction between different applications without using AIDL. And the startActivityforResult function is a system-level function, and AIDL is only a service. Therefore, the startActivityforResult function has higher security performance than AIDL.

Step S103: When the second application acquires an authorization code before the second application is closed, generating authorization feedback data according to the authorization code, where the feedback data includes authorization feedback data.

In this embodiment, the authorization code is obtained in response to the user's click operation in the startup page of the second application. For example, the user clicks the authorization button in the launch page of the second application to generate an authorization code. Authorization feedback data is generated according to the obtained authorization code before the startup page of the second application is closed. Optionally, when the second application acquires the authorization code within a predetermined time, generating feedback data of authorization success according to the authorization code; when the second application does not acquire the location within a predetermined time When the authorization code is described, the feedback data of the authorization failure is generated according to the authorization code.

Step S104: When the second application acquires the unauthorized information before the second application is closed, generating authorization failure feedback data.

In this embodiment, after the authorization failure feedback data is generated and the second application is closed, the feedback data of the authorization failure is fed back to the first application through a preset second protocol. It should be noted that the unauthorized information may be information generated by the user clicking the rejection authorization in the startup page of the second application.

Step S105, after the second application is closed, feeding back the authorization feedback data to the first application by using a preset second protocol, so that the first application acquires authorization information of the second application. .

In this embodiment, the second protocol is for transmitting the feedback data to an application that allows the feedback data to be received after the second application is closed. Alternatively, the second protocol can be implemented using the setResult method.

As an implementation, the setResult(RESULT_OK, intent) method is called to return the feedback data. RESULT_OK is an integer used to indicate that the result is successfully obtained. When the feedback data is feedback data of authorization success, RESULT_OK is a normal value; when the feedback data is feedback data of authorization failure, RESULT_OK is abnormal. The intent represents an intent object in which the authorization code that needs to be returned is encapsulated. The intent object contains a bundle object, and the bundle object is used to store the authorization code. Specifically, the authorization code is stored by calling putString(AUTH_CODE, code) in the bundler, where AUTH_CODE represents the key name of the authorization code, and code represents the value of the authorization code. After the setResult method is set, the system will return the intent message to the first application when the page returns, thereby completing the transmission of the message between the first application and the second application.

Step S106: When the first application determines that the received authorization feedback data is the feedback data of the authorization success, the feedback data of the authorization success is parsed to obtain the authorization code.

As an implementation manner, whether the RESULT_OK is abnormal in the information transmitted by the second application through the setResult method may be checked first. When the RESULT_OK is abnormal, it is determined that the current authorization fails, and the first application does not acquire the authorization of the second application. When the RESULT_OK is normal, the first application parses the passed intent object to obtain the content of the authorization code. The specific parsing process is to obtain the bundle object by calling the getBundle in the intent, and then get the content of the authorization code by calling the getString(AUTH_CODE) method in the bundler object, so that the authorization code information can be obtained.

Second embodiment

Please refer to FIG. 4. FIG. 4 is a schematic diagram of an authorization information acquiring apparatus 200 according to a preferred embodiment of the present application. The authorization information obtaining apparatus 200 includes a first obtaining module 201, a starting module 202, a generating module 203, a feedback module 204, a parsing module 205, a second obtaining module 206, and an adding module 207.

The first obtaining module 201 is configured to obtain, by the first application, the description information corresponding to the second application in response to the user operation.

In the embodiment of the present application, step S101 may be performed by the first obtaining module 201.

The startup module 202 is configured to invoke the first protocol preset in the electronic device 100 according to the description information, and implicitly open a preset startup page in the second application, where The first protocol is configured to implement an application process corresponding to the description information and allow the application process to be closed to feed back data to the first application, where the feedback data is the second application Starts the data generated after the page is started.

In the embodiment of the present application, step S102 may be performed by the startup module 202.

The generating module 203 is configured to generate authorization feedback data according to the authorization code when the second application acquires an authorization code before the second application is closed, wherein the feedback data includes authorization feedback data. And being further configured to generate authorization failure feedback data when the second application acquires the unauthorized information before the second application is closed.

In this embodiment, the generating module is specifically configured to:

When the second application acquires the authorization code within a predetermined time, generating feedback data of authorization success according to the authorization code;

When the second application does not acquire the authorization code within a predetermined time, the feedback data of the authorization failure is generated according to the authorization code.

a feedback module 204, after the second application is closed, feeding back the authorization feedback data to the first application by using a preset second protocol, so that the first application acquires the second application The authorization information, wherein the second protocol is used to implement the feedback of the feedback data to the application that allows the feedback data to be received after the second application is closed.

In this embodiment, the generating module 203 is further configured to generate authorization failure feedback data when the second application does not obtain the authorization information before the second application is closed;

The feedback module 204 is further configured to feed back the feedback data of the authorization failure to the first application by using a preset second protocol after the second application is closed.

The generating module 203 is further configured to:

When the second application acquires the authorization code before the second application is closed, the setResult(RESULT_OK, intent) function is called to return the authorization feedback data, wherein RESULT_OK is an integer used to indicate that the result is successfully obtained. The feedback data is the feedback data of the authorization success, and the RESULT_OK corresponds to a preset integer (such as 1); when the feedback data is the feedback data of the authorization failure, the RESULT_OK corresponds to a non-preset integer (such as 0); the intent represents an intent object. Encapsulating an authorization code that needs to be returned in the intent object; the intent object includes a bundle object, and the bundle object is used to store the authorization code; wherein the authorization code is by calling putString(AUTH_CODE, code) in the bundler object Stored, where AUTH_CODE represents the key name of the authorization code, and code represents the value of the authorization code.

In the embodiment of the present application, both step S103 and step S104 may be performed by the generating module 203, and the step S105 may be performed by the feedback module 204.

The parsing module 205 is configured to parse the authorization success feedback data to obtain the authorization code when the first application determines that the received authorization feedback data is authorization success feedback data.

The parsing module is specifically configured to:

Call the getBundle function in the intent object to get the Bundle object.

The authorization code is obtained by calling the getString(AUTH_CODE) function in the Bundle object.

In the embodiment of the present application, step S106 may be performed by the parsing module 205.

The second obtaining module 206 is configured to obtain the description information corresponding to each of the applications, where the description information includes an application package name.

In the embodiment of the present application, step S201 may be performed by the second obtaining module 206.

The adding module 207 is configured to add the description information into a description file of the corresponding application.

In the embodiment of the present application, step S202 may be performed by the adding module 207.

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may also be implemented in other manners. The apparatus embodiments described above are merely illustrative, for example, the flowcharts and block diagrams in the figures illustrate the architecture, functionality, and functionality of possible implementations of apparatus, methods, and computer program products according to various embodiments of the present application. operating. In this regard, each block of the flowchart or block diagram can represent a module, a program segment, or a portion of code that includes one or more of the Executable instructions. It should also be noted that, in some alternative implementations, the functions noted in the blocks may also occur in a different order than those illustrated in the drawings. For example, two consecutive blocks may be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending upon the functionality involved. It is also noted that each block of the block diagrams and/or flowcharts, and combinations of blocks in the block diagrams and/or flowcharts, can be implemented in a dedicated hardware-based system that performs the specified function or action. Or it can be implemented by a combination of dedicated hardware and computer instructions.

In addition, each functional module in each embodiment of the present application may be integrated to form a separate part, or each module may exist separately, or two or more modules may be integrated to form a separate part.

The functions, if implemented in the form of software functional modules and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application, which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including The instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

It should be noted that, in this context, relational terms such as first and second are used merely to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply these entities or operations. There is any such actual relationship or order between them. Furthermore, the term "comprises" or "comprises" or "comprises" or any other variations thereof is intended to encompass a non-exclusive inclusion, such that a process, method, article, or device that comprises a plurality of elements includes not only those elements but also Other elements, or elements that are inherent to such a process, method, item, or device. An element that is defined by the phrase "comprising a ..." does not exclude the presence of additional equivalent elements in the process, method, item, or device that comprises the element.

The above description is only the preferred embodiment of the present application, and is not intended to limit the present application, and various changes and modifications may be made to the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of this application are intended to be included within the scope of the present application. It should be noted that similar reference numerals and letters indicate similar items in the following figures. Therefore, once an item is defined in one figure, it is not necessary to further define and explain it in the subsequent figures.

The foregoing is only a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the present application. It should be covered by the scope of protection of this application. Therefore, the scope of protection of the present application should be determined by the scope of the claims.

Industrial applicability

The method for acquiring authorization information, the electronic device, and the readable storage medium provided by the application, after the first protocol is started, the second application is allowed to send the feedback data to the first application. The function replaces the prior art using AIDL services for data communication, thereby reducing the coupling relationship between applications. Effectively improve the efficiency of communication between applications. At the same time, the first protocol is a system-level protocol, which is more secure and more reliable.

Claims

A method for acquiring authorization information, which is characterized in that it is applied to an electronic device, and the electronic device stores a plurality of applications, and the method includes:

The first application obtains the description information corresponding to the second application in response to the user operation;

The first application, according to the description information, invokes a first protocol preset in the electronic device, and implicitly opens a predefined startup page in the second application, where the first protocol is used for Implementing an application process corresponding to the description information and allowing the application process to close, and then feeding back data to the first application, the feedback data being data generated after the second application startup page is started ;

And when the second application acquires the authorization code before the second application is closed, generating authorization feedback data according to the authorization code, where the feedback data includes authorization feedback data;

After the second application is closed, the authorization feedback data is fed back to the first application by using a preset second protocol, so that the first application acquires authorization information of the second application, where The second protocol is for transmitting the feedback data to an application that allows the feedback data to be received after the second application is closed.
The method of claim 1, wherein the startup page comprises a description file, the method further comprising:

Obtaining the description information corresponding to each of the applications, where the description information includes an application package name;

The description information is added to the corresponding description file of the application.
The method according to claim 1, wherein when the second application acquires an authorization code before the second application is closed, the step of generating authorization feedback data according to the authorization code comprises:

When the second application acquires the authorization code within a predetermined time, generating feedback data of authorization success according to the authorization code;

When the second application does not acquire the authorization code within a predetermined time, the feedback data of the authorization failure is generated according to the authorization code.
The method of claim 3, wherein the method further comprises:

Generating authorization failure feedback data when the second application fails to obtain authorization information before the second application is closed;

After the second application is closed, the feedback data of the authorization failure is fed back to the first application through a preset second protocol.
The method according to claim 3, wherein when the second application acquires an authorization code before the second application is closed, the step of generating authorization feedback data according to the authorization code comprises:

The second application calls the setResult(RESULT_OK, intent) function to return the authorization feedback data when the authorization code is obtained before the second application is closed, wherein RESULT_OK is an integer used to indicate that the result is successfully obtained. The feedback data is the feedback data of the authorization success, and the RESULT_OK corresponds to a preset integer; when the feedback data is the feedback data of the authorization failure, the RESULT_OK corresponds to the non-preset integer; the intent represents an intent object, and the encapsulation needs to be returned in the intent object. The authorization code passed; the intent object contains a bundle object, and the bundle object is used to store the authorization code; wherein the authorization code is stored by calling putString(AUTH_CODE, code) in the bundler object, where AUTH_CODE indicates The key name of the authorization code, code indicates the value of the authorization code.
The method of claim 5, wherein the method further comprises:

And when the first application determines that the received authorization feedback data is the authorization success feedback data, parsing the authorization success feedback data to obtain the authorization code.
The method of claim 6, wherein the step of parsing the authorization success feedback data to obtain the authorization code comprises:

Call the getBundle function in the intent object to get the Bundle object.

The authorization code is obtained by calling the getString(AUTH_CODE) function in the Bundle object.
The method of any of claims 1-7, wherein the first protocol comprises a startActivityforResult function.
The method of any of claims 1-7, wherein the second protocol comprises a setResult function.
An authorization information acquisition device is characterized in that it is applied to an electronic device, and the electronic device stores a plurality of application programs, and the device includes:

a first acquiring module, configured to: the first application, in response to the user operation, obtain description information corresponding to the second application;

a startup module, configured to: the first application invokes a first protocol preset in the electronic device according to the description information, and implicitly opens a predefined startup page in the second application, where The first protocol is configured to implement an application process corresponding to the description information and allow the application process to be closed to feed back data to the first application, the feedback data being the second application startup page Data generated after startup;

a generating module, configured to generate authorization feedback data according to the authorization code when the second application acquires an authorization code before the second application is closed, where the feedback data includes authorization feedback data;

a feedback module, configured to: after the second application is closed, feed back the authorization feedback data to the first application by using a preset second protocol, so that the first application acquires the second application Authorization information, wherein the second protocol is for transmitting the feedback data to an application that allows the feedback data to be received after the second application is closed.
The device of claim 10, wherein the activation page comprises a description file, the device further comprising:

a second obtaining module, configured to obtain the description information corresponding to each of the applications, where the description information includes an application package name;

And adding a module configured to add the description information to a description file of the corresponding application.
The device according to claim 10, wherein the generating module is specifically configured to:

When the second application acquires the authorization code within a predetermined time, generating feedback data of authorization success according to the authorization code;

When the second application does not acquire the authorization code within a predetermined time, the feedback data of the authorization failure is generated according to the authorization code.
The device of claim 12 wherein:

The generating module is further configured to generate authorization failure feedback data when the second application fails to obtain authorization information before the second application is closed;

The feedback module is further configured to feed back the feedback data of the authorization failure to the first application by using a preset second protocol after the second application is closed.
The apparatus of claim 12 wherein said generating module is further configured to:

The second application calls the setResult(RESULT_OK, intent) function to return the authorization feedback data when the authorization code is obtained before the second application is closed, wherein RESULT_OK is an integer used to indicate that the result is successfully obtained. The feedback data is the feedback data of the authorization success, and the RESULT_OK corresponds to a preset integer; when the feedback data is the feedback data of the authorization failure, the RESULT_OK corresponds to the non-preset integer; the intent represents an intent object, and the encapsulation needs to be returned in the intent object. The authorization code passed; the intent object contains a bundle object, and the bundle object is used to store the authorization code; wherein the authorization code is stored by calling putString(AUTH_CODE, code) in the bundler object, where AUTH_CODE indicates The key name of the authorization code, code indicates the value of the authorization code.
The device of claim 14 wherein said device further comprises:

The parsing module is configured to parse the authorization success feedback data to obtain the authorization code when the first application determines that the received authorization feedback data is the authorization success feedback data.
The apparatus according to claim 15, wherein the parsing module is specifically configured to:

Call the getBundle function in the intent object to get the Bundle object.

The authorization code is obtained by calling the getString(AUTH_CODE) function in the Bundle object.
An electronic device, comprising:

Memory

Processor;

An authorization information acquisition device, the authorization information acquisition device being stored in the memory and comprising one or more software function modules executed by the processor, comprising:

a first acquiring module, configured to: the first application, in response to the user operation, obtain description information corresponding to the second application;

a startup module, configured to: the first application invokes a first protocol preset in the electronic device according to the description information, and implicitly opens a predefined startup page in the second application, where The first protocol is configured to implement an application process corresponding to the description information and allow the application process to be closed to feed back data to the first application, where the feedback data is the second application The data generated after the startup page is started;

a generating module, configured to generate authorization feedback data according to the authorization code when the second application acquires an authorization code before the second application is closed, where the feedback data includes authorization feedback data;

a feedback module, configured to: after the second application is closed, feed back the authorization feedback data to the first application by using a preset second protocol, so that the first application acquires the second application Authorization information, wherein the second protocol is for transmitting the feedback data to an application that allows the feedback data to be received after the second application is closed.
A readable storage medium, the readable storage medium comprising a computer program, characterized by:

The electronic device in which the readable storage medium is located is controlled to execute the authorization information acquiring method according to any one of claims 1-8.