IOS application login state unified management method and device, equipment and medium
By introducing a routing center module to uniformly manage the login status of iOS applications, the problem of repeated pop-ups on the login page caused by multiple entry points was solved, thus improving the user experience.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- SHENZHEN LEAGSOFT TECH
- Filing Date
- 2026-01-08
- Publication Date
- 2026-05-15
AI Technical Summary
The existing technology suffers from the problem of repeated pop-up windows on the login page of iOS applications due to the decentralized and independent processing logic of multiple entry points.
A routing center module is introduced to uniformly manage the login status of iOS applications. It detects user operation events and determines whether to redirect to a preset login navigation page or execute business logic based on the login status.
This effectively avoids the problem of repeated pop-ups on the login page caused by the decentralized and independent processing logic of multiple entry points, thus improving the user experience.
Smart Images
Figure CN122053590A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of iOS applications, and in particular to a method, apparatus, device and medium for unified management of iOS application login status. Background Technology
[0002] With the deep penetration of the mobile internet and the continuous iteration of smart terminal functions, mobile applications have evolved from a single launch point to a multi-scenario, multi-dimensional interactive ecosystem. Various entry channels have increasingly become the norm for users' daily interactions. Users can launch applications by clicking on traditional application icons, or quickly access core functions through desktop shortcuts and system push notifications. These multi-channel entry points greatly reduce the user's operation path, improve the efficiency of function access, and have become a core highlight of the modern mobile application experience.
[0003] Currently, existing technologies employ a fragmented processing approach to implement multi-channel entry functionality. Specifically, developers write independent processing logic for each entry channel.
[0004] However, because the processing logic for each entry point is independent, it can easily lead to a fragmented user experience and inconsistent states. For example, when a user is not logged in, the application page repeatedly pops up pop-ups prompting the user to log in. This phenomenon severely impacts the user experience. Summary of the Invention
[0005] This application provides a unified management method, apparatus, device, and medium for iOS application login status, aiming to solve the technical problem of repeated pop-up windows on the login page caused by the decentralized and independent processing logic of multiple entry points in the prior art.
[0006] In a first aspect, embodiments of this application provide a unified management method for login status of an iOS application. The method is applied to an iOS application, which includes a routing center module. The method includes: In response to a first operation triggered by the user, receive a first event corresponding to the first operation; Transmit the first event to the routing center module; Upon receiving the first event, the routing center module detects the current login status of the iOS application. If the current login status of the iOS application is detected to be not logged in, the routing center module triggers the iOS application to jump to the preset login navigation page; If the current login status of the iOS application is detected to be logged in, the routing center module triggers the iOS application to execute the business logic corresponding to the first event.
[0007] Optionally, the first event can be any of the following: a quick operation command, a remote push message, or a local notification message.
[0008] Optionally, before the routing center module detects the current login status of the iOS application, and after transmitting the first event to the routing center module, the method further includes: The routing center module triggers the iOS application to perform an application badge correction operation.
[0009] Optionally, before the routing center module triggers the iOS application to jump to the preset login navigation page, the method further includes: The integrity of the iOS application's package body is checked according to preset verification rules; If the iOS application is detected to be currently logged out, the routing center module triggers the iOS application to redirect to a preset login navigation page, including: If the iOS application is detected to be currently not logged in, and the iOS application's package integrity check passes, the routing center module triggers the iOS application to redirect to a preset login navigation page.
[0010] Optionally, if the first event is used to trigger the iOS application to jump to a preset sensitive page, before the routing center module triggers the iOS application to execute the business logic corresponding to the first event, the method further includes: The routing center module triggers the iOS application to disable the screen recording function.
[0011] Optionally, if the first event is used to trigger the iOS application to receive an external file, and if the current login status of the iOS application is detected to be logged in, then the routing center module triggers the iOS application to execute the business logic corresponding to the first event, including: If the current login status of the iOS application is detected as "logged in", the routing center module triggers the iOS application to receive the external file and sets the received external file to read-only mode.
[0012] Optionally, if the first event is used to trigger the iOS application to receive an external file, and if the current login status of the iOS application is detected to be logged in, then the routing center module triggers the iOS application to execute the business logic corresponding to the first event, including: If the current login status of the iOS application is detected as "logged in", the routing center module triggers the iOS application to receive the external file and store the received external file in a preset sandbox environment.
[0013] Secondly, embodiments of this application also provide an iOS application login status unified management device, which includes a unit for performing the above-described method.
[0014] Thirdly, embodiments of this application also provide a computer device, which includes a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the above-described method.
[0015] Fourthly, embodiments of this application also provide a computer-readable storage medium storing a computer program that, when executed by a processor, can implement the above-described method.
[0016] This application provides a unified management method, apparatus, device, and medium for iOS application login status. The method is applied to an iOS application, which includes a routing center module. The method includes: responding to a first operation triggered by a user, receiving a first event corresponding to the first operation; transmitting the first event to the routing center module; after receiving the first event, the routing center module detects the current login status of the iOS application; if the current login status is detected as not logged in, the routing center module triggers the iOS application to redirect to a preset login navigation page; if the current login status is detected as logged in, the routing center module triggers the iOS application to execute business logic corresponding to the first event. Therefore, in this application's technical solution, responding to a first operation triggered by a user, receiving a first event corresponding to the first operation, and then transmitting the first event to the routing center module. Furthermore, upon receiving the first event, the routing center module checks the current login status of the iOS application. If the iOS application is not logged in, the routing center module triggers the iOS application to redirect to a preset login navigation page. If the iOS application is logged in, the routing center module triggers the iOS application to execute the business logic corresponding to the first event. Therefore, in this technical solution, when the iOS application receives the first event, it does not directly trigger the execution of the corresponding business logic. Instead, it first sends the first event to the routing center module, which performs a unified detection and determination of the application's current login status. If the detection result is not logged in, the routing center module will trigger the iOS application to redirect to the preset login navigation page. If the detection result is logged in, the routing center module will then trigger the iOS application to execute the business logic corresponding to the first event. This mechanism fundamentally avoids problems such as duplicate login page pop-ups caused by the dispersed and independent processing logic of multiple entry points, significantly improving the user experience. Attached Figure Description
[0017] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.
[0018] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0019] One or more embodiments are illustrated by way of example with reference numerals in the accompanying drawings. These illustrations do not constitute a limitation on the embodiments. Elements with the same reference numerals in the drawings are denoted as similar elements. Unless otherwise stated, the figures in the drawings are not to be limited by scale.
[0020] Figure 1 A flowchart illustrating a unified management method for iOS application login status provided in an embodiment of this application; Figure 2 A schematic block diagram of an iOS application login status unified management device provided in this application embodiment; Figure 3 A computer device provided in an embodiment of this application. Detailed Implementation
[0021] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0022] The following disclosure provides numerous different embodiments or examples for implementing various structures of this application. To simplify the disclosure, specific examples of components and arrangements are described below. These are merely examples and are not intended to limit the scope of this application. Furthermore, reference numerals and / or letters may be repeated in different examples. Such repetition is for simplification and clarity and does not in itself indicate a relationship between the various embodiments and / or arrangements discussed.
[0023] It should be understood that, when used in this specification and the appended claims, the terms "comprising" and "including" indicate the presence of the described features, integrals, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or collections thereof.
[0024] It should also be understood that the terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to limit the scope of the application. As used in this specification and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless the context clearly indicates otherwise.
[0025] It should also be further understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.
[0026] As used in this specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection." Similarly, the phrase "if determined" or "if [described condition or event] is detected" may be interpreted, depending on the context, as "once determined," "in response to determination," "once [described condition or event] is detected," or "in response to detection of [described condition or event]."
[0027] To address the technical problem of repeated pop-up windows on the login page caused by the decentralized and independent processing logic of multiple entry points in the prior art, this application provides a unified management device for iOS application login status, which can avoid the technical problem of repeated pop-up windows on the login page caused by the decentralized and independent processing logic of multiple entry points.
[0028] Figure 1 This is a flowchart illustrating a unified management method for iOS application login status provided in an embodiment of this application. In one embodiment, the method is applied to an iOS application, which includes a routing center module, and the method includes steps S101-S105.
[0029] S101. In response to a first operation triggered by the user, receive a first event corresponding to the first operation.
[0030] The first operation can be an interaction between the user and the iOS application through the UI, or a message sent by the user to the iOS application through third-party software or platform, causing the iOS application to trigger a corresponding event. It should be noted that the entity receiving the first event can be a business module within the iOS application or the notification module of the iOS application. This application does not impose any restrictions on this.
[0031] In one embodiment, the first event is any one of the following: a quick action command, a remote push message, and a local notification message. The quick action command is an operation command provided by the iOS application to quickly access the corresponding function of the iOS application. The remote push message can be a message pushed to the iOS application by a remote server, third-party software, or third-party platform. The local notification message can be a notification message received locally by the iOS application.
[0032] It's worth noting that when an iOS app launches, it reads font preferences and pre-sets the font format for display to prevent jittering during runtime. Simultaneously, iOS registers at least one quick action upon launch, creates a preset login navigation page, and sets it as the root entry point. Next, it registers various notification listeners to monitor and retrieve remote push notifications and local notifications.
[0033] S102, Transmit the first event to the routing center module.
[0034] The routing center module is used for global routing notifications for iOS applications. In this embodiment, all events triggered by entry channels are transmitted to the routing center module, which then uniformly detects the current login status of the iOS application.
[0035] S103. After receiving the first event, the routing center module detects the current login status of the iOS application.
[0036] S104. If the current login status of the iOS application is detected as not logged in, the routing center module will trigger the iOS application to jump to the preset login navigation page.
[0037] When an iOS application detects that it is not logged in, the routing center module triggers the iOS application to jump to the preset login navigation page and records the current login status of the iOS application for subsequent detection of the login status of the iOS application, effectively avoiding the problem of repeated pop-up windows on the login page.
[0038] S105. If the current login status of the iOS application is detected as "logged in", the routing center module triggers the iOS application to execute the business logic corresponding to the first event.
[0039] When the iOS application detects that the current login status is "logged in", the routing center module triggers the iOS application to execute the business logic corresponding to the first event.
[0040] It should be noted that in this embodiment, corresponding business logic is configured for each event.
[0041] This application provides a unified management method for iOS application login status. The method is applied to an iOS application, which includes a routing center module. The method includes: responding to a first operation triggered by a user, receiving a first event corresponding to the first operation; transmitting the first event to the routing center module; after receiving the first event, the routing center module detects the current login status of the iOS application; if the current login status is detected as not logged in, the routing center module triggers the iOS application to redirect to a preset login navigation page; if the current login status is detected as logged in, the routing center module triggers the iOS application to execute business logic corresponding to the first event. Therefore, in this application's technical solution, responding to a first operation triggered by a user, receiving a first event corresponding to the first operation, and then transmitting the first event to the routing center module. Furthermore, upon receiving the first event, the routing center module checks the current login status of the iOS application. If the iOS application is not logged in, the routing center module triggers the iOS application to redirect to a preset login navigation page. If the iOS application is logged in, the routing center module triggers the iOS application to execute the business logic corresponding to the first event. Therefore, in this technical solution, when the iOS application receives the first event, it does not directly trigger the execution of the corresponding business logic. Instead, it first sends the first event to the routing center module, which performs a unified detection and determination of the application's current login status. If the detection result is not logged in, the routing center module will trigger the iOS application to redirect to the preset login navigation page. If the detection result is logged in, the routing center module will then trigger the iOS application to execute the business logic corresponding to the first event. This mechanism fundamentally avoids problems such as duplicate login page pop-ups caused by the dispersed and independent processing logic of multiple entry points, significantly improving the user experience.
[0042] In one embodiment, before S103 and after S102, the method further includes S106.
[0043] S106. The routing center module triggers the IOS application to perform an application badge correction operation.
[0044] It should be noted that different channel entry points may have a certain impact on the display status of application badges. To ensure the accuracy of application badge display, in this implementation, the routing center module triggers the iOS application to perform application badge correction operations based on the content of the first event. This effectively avoids conflicts caused by multiple channel entry point processing logics simultaneously performing application badge correction operations, which could lead to incorrect application badge display.
[0045] In one embodiment, prior to S104 above, the method further includes S107.
[0046] S107. Perform integrity checks on the iOS application package according to preset verification rules.
[0047] The preset verification rules are used to instruct the detection of the integrity of the iOS application's package. In this embodiment, the preset verification rules can be set according to the characteristics of the iOS application itself, for example, verifying the iOS application's own signature or description file.
[0048] The above S104 specifically includes the following steps: S1041.
[0049] S1041. If the current login status of the iOS application is detected as not logged in, and the integrity check of the iOS application's package body passes, the routing center module will trigger the iOS application to jump to the preset login navigation page.
[0050] It's important to note that before the iOS application redirects to the preset login navigation page, a check on the integrity of the iOS application's data package is performed. If the integrity check passes, the routing center module triggers the iOS application to redirect to the preset login navigation page. This mechanism effectively prevents security issues caused by tampering with the iOS application's data package.
[0051] It should be noted that, in this embodiment, the integrity of the iOS application's package can be checked periodically or at preset critical business nodes to monitor in real time whether the iOS application's package has been tampered with. If the iOS application's package integrity check fails, a pop-up window can be used to notify the user and terminate the operation of critical business processes.
[0052] In one embodiment, if the first event is used to trigger the iOS application to jump to a preset sensitive page, the method further includes S108 before S105.
[0053] S108, The routing center module triggers the iOS application to disable the screen recording function.
[0054] It should be noted that the applicant set the preset sensitive page based on actual business scenarios. When the first event triggers the iOS application to jump to the preset sensitive page, the routing center module triggers the iOS application to disable screen recording to prevent the leakage of sensitive information.
[0055] In one embodiment, if the first event is used to trigger the iOS application to receive an external file, the above S105 specifically includes the following steps: S1051.
[0056] S1051. If the current login status of the iOS application is detected as "logged in", the routing center module triggers the iOS application to receive external files and sets the received external files to read-only mode.
[0057] It should be noted that, to prevent external files from carrying viruses, when an iOS application needs to receive external files, the received external files are set to read-only mode in this embodiment. Users are only allowed to read the content of the external files, and are not allowed to run or modify them.
[0058] In one embodiment, if the first event is used to trigger the iOS application to receive an external file, the above S105 specifically includes the following steps: S1052.
[0059] S1052. If the current login status of the iOS application is detected as "logged in", the routing center module triggers the iOS application to receive external files and stores the received external files in the preset sandbox environment.
[0060] It should be noted that, to prevent external files from carrying viruses, when an iOS application needs to receive external files, this embodiment stores the received external files in a preset sandbox environment. Users can perform read, write, or run operations on external files within the sandbox environment. Even if the external file carries a virus, it will not affect the host environment, effectively reducing the security risks to the host machine.
[0061] See Figure 2 , Figure 2 This is a schematic block diagram of an iOS application login status unified management device provided in an embodiment of this application. Corresponding to the above-described iOS application login status unified management method, this application also provides an iOS application login status unified management device. This iOS application login status unified management device includes a unit for executing the above-described iOS application login status unified management method, and the iOS application login status unified management device can be configured in terminals such as desktop computers, tablet computers, and laptops. Specifically, the iOS application login status unified management device includes: The receiving module 201 is configured to receive a first event corresponding to the first operation in response to the first operation triggered by the user; Transmission module 202 is used to transmit the first event to the routing center module; The routing center module 203 is used to detect the current login status of the iOS application after receiving the first event; if the current login status of the iOS application is detected to be not logged in, the routing center module triggers the iOS application to jump to a preset login navigation page; if the current login status of the iOS application is detected to be logged in, the routing center module triggers the iOS application to execute the business logic corresponding to the first event.
[0062] In one embodiment, the first event is any one of the following: a quick operation command, a remote push message, and a local notification message.
[0063] In one embodiment, the routing center module 203 is also used to trigger the iOS application to perform an application badge correction operation. In one embodiment, the device further includes a detection module 204, used to detect the integrity of the iOS application's package body according to preset verification rules; The routing center module 203 is further configured to, if it detects that the current login status of the iOS application is not logged in and the package integrity detection of the iOS application passes, trigger the iOS application to jump to a preset login navigation page.
[0064] In one embodiment, if the first event is used to trigger the iOS application to jump to a preset sensitive page, the routing center module 203 is also used to trigger the iOS application to disable the screen recording function.
[0065] In one embodiment, if the first event is used to trigger the iOS application to receive an external file, the routing center module 203 is further configured to, if it detects that the current login status of the iOS application is logged in, trigger the iOS application to receive the external file and set the received external file to read-only mode.
[0066] In one embodiment, if the first event is used to trigger the iOS application to receive an external file, the routing center module 203 is further configured to, if it detects that the current login status of the iOS application is logged in, trigger the iOS application to receive the external file and store the received external file in a preset sandbox environment.
[0067] like Figure 3As shown, this application provides a computer device including a processor 31, a communication interface 32, a memory 33, and a communication bus 34. The processor 31, the communication interface 32, and the memory 33 communicate with each other through the communication bus 34. The memory 33 is used to store computer programs. In one embodiment of this application, when the processor 31 executes the program stored in the memory 33, it implements the control method for unified management of iOS application login status provided in any of the foregoing method embodiments.
[0068] It will be understood by those skilled in the art that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program may be stored in a storage medium, which is a computer-readable storage medium. The computer program is executed by at least one processor in the computer system to implement the process steps of the embodiments of the above methods.
[0069] Therefore, embodiments of this application also provide a computer-readable storage medium storing a computer program thereon, wherein when the computer program is executed by a processor, it implements the steps of the unified management method for iOS application login status as provided in any of the foregoing method embodiments.
[0070] The storage medium is a physical, non-transient storage medium, such as a USB flash drive, external hard drive, read-only memory (ROM), magnetic disk, or optical disk, or any other physical storage medium capable of storing program code. The computer-readable storage medium can be non-volatile or volatile.
[0071] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.
[0072] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For example, the division of each unit is merely a logical functional division, and there may be other division methods in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.
[0073] The steps in the methods of this application embodiment can be adjusted, merged, or deleted according to actual needs. The units in the apparatus of this application embodiment can be merged, divided, or deleted according to actual needs. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.
[0074] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, a terminal, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application.
[0075] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.
[0076] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Since these modifications and variations fall within the scope of the claims and their equivalents, this application also intends to include these modifications and variations.
[0077] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. A unified management method for iOS application login status, characterized in that, The method is applied to an iOS application, which includes a routing center module, and the method includes: In response to a first operation triggered by the user, receive a first event corresponding to the first operation; Transmit the first event to the routing center module; Upon receiving the first event, the routing center module detects the current login status of the iOS application. If the current login status of the iOS application is detected to be not logged in, the routing center module triggers the iOS application to jump to the preset login navigation page; If the current login status of the iOS application is detected to be logged in, the routing center module triggers the iOS application to execute the business logic corresponding to the first event.
2. The method according to claim 1, characterized in that, The first event is any one of the following: a quick operation command, a remote push message, or a local notification message.
3. The method according to claim 1, characterized in that, Before the routing center module detects the current login status of the iOS application after receiving the first event, and after transmitting the first event to the routing center module, the method further includes: The routing center module triggers the iOS application to perform an application badge correction operation.
4. The method according to any one of claims 1 to 3, characterized in that, Before the routing center module triggers the iOS application to redirect to the preset login navigation page, the method further includes: The integrity of the iOS application's package body is checked according to preset verification rules; If the iOS application is detected to be currently logged out, the routing center module triggers the iOS application to redirect to a preset login navigation page, including: If the iOS application is detected to be currently not logged in, and the iOS application's package integrity check passes, the routing center module triggers the iOS application to redirect to a preset login navigation page.
5. The method according to any one of claims 1 to 3, characterized in that, If the first event is used to trigger the iOS application to redirect to a preset sensitive page, before the routing center module triggers the iOS application to execute the business logic corresponding to the first event, the method further includes: The routing center module triggers the iOS application to disable the screen recording function.
6. The method according to any one of claims 1 to 3, characterized in that, If the first event is used to trigger the iOS application to receive an external file, and if the current login status of the iOS application is detected to be logged in, then the routing center module triggers the iOS application to execute the business logic corresponding to the first event, including: If the current login status of the iOS application is detected as "logged in", the routing center module triggers the iOS application to receive the external file and sets the received external file to read-only mode.
7. The method according to any one of claims 1 to 3, characterized in that, If the first event is used to trigger the iOS application to receive an external file, and if the current login status of the iOS application is detected to be logged in, then the routing center module triggers the iOS application to execute the business logic corresponding to the first event, including: If the current login status of the iOS application is detected as "logged in", the routing center module triggers the iOS application to receive the external file and store the received external file in a preset sandbox environment.
8. A unified management device for iOS application login status, characterized in that, The device is used in iOS applications, and the device includes: The receiving module is used to receive a first event corresponding to the first operation triggered by the user in response to the first operation; The transmission module is used to transmit the first event to the routing center module; The routing center module is used to detect the current login status of the iOS application after receiving the first event; if the current login status of the iOS application is detected to be not logged in, the routing center module triggers the iOS application to jump to a preset login navigation page; if the current login status of the iOS application is detected to be logged in, the routing center module triggers the iOS application to execute the business logic corresponding to the first event.
9. A computer device, characterized in that, The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement the method as described in any one of claims 1 to 7.
10. A computer-readable storage medium, characterized in that, The storage medium stores a computer program that, when executed by a processor, can implement the method as described in any one of claims 1 to 7.