FAQ

Source code protection means protecting application source code from unauthorized access, modification, and misuse. LIAPP prevents unauthorized app analysis through code obfuscation and encryption.

Source code leaks expose sensitive information such as API keys, security logic, and server addresses, leading not only to corporate intellectual property infringement but also to exposure of security vulnerabilities. LIAPP protects source code to prevent various risks arising from such leaks.

Source code obfuscation is just basic defense and should be used together with tampering detection, integrity checks, debugging detection, RASP, etc. to be effective. LIAPP provides integrated protection with all these technologies to enhance security.

Reverse engineering is an attack method that analyzes apps to identify internal logic or vulnerabilities. LIAPP defends against this by applying source code obfuscation, debugger detection, and encryption technologies to mobile apps.

Hackers can tamper with apps to insert malicious code, bypass authentication, etc. LIAPP prevents tampering and blocks it in advance with functionality that verifies tampering when the app runs.

Rooted and jailbroken devices have disabled system protections, allowing malicious apps to steal sensitive data. LIAPP restricts app execution in dangerous environments through rooting/jailbreak detection functionality.

Hackers attempt to analyze internal information or tamper by connecting debuggers or using memory manipulation tools. LIAPP detects these through various methods including debugging connection detection, memory area access detection, hooking, and library exploration, and can respond immediately by terminating the app or collecting logs.

RASP (Runtime Application Self Protection) is technology that detects and blocks security threats occurring during app execution in real-time. It can detect rooting, tampering, debugging, etc. in the app runtime environment and respond immediately. LIAPP can apply RASP functionality without separate development.

RASP detects rooting, tampering, debugging, etc. while the app is running and immediately stops app execution to block security risks. LIAPP can apply RASP functionality without separate development.

If there are parts that should be excluded from obfuscation targets in advance, it is possible if you inform the LIAPP team beforehand.

No, app developers have nothing separate to do. After obfuscation, compatibility testing is all handled by the LIAPP team.

Once obfuscation is complete, a function to download MAP files is provided in the LIAPP console. You can check which parts were obfuscated and how through the files.

*TEST
TEST is a service provided to allow you to experience LIAPP and decide whether to purchase before buying tickets or licenses.
You can apply LIAPP for free using TEST and check functionality and compatibility in advance.
When using TEST, LIAPP ON-SITE functionality is applied.
Apps applied with TEST can be used for 2 days, and after 2 days the app will not run.

*PROTECT
PROTECT is the function used when officially applying LIAPP using tickets or licenses.
To apply LIAPP using PROTECT, you must use tickets or have a valid license.
When using tickets, one ticket is used each time PROTECT is applied, and apps with licenses can apply PROTECT unlimited times during the validity period.

TEST and PROTECT have the above characteristics, and there are no functional differences in LIAPP.

Uploaded files are immediately deleted after LIAPP application and are not stored separately.

If LIAPP application fails, please check the following and retry:
1) File upload did not complete normally.
2) Filename contains characters other than English letters, numbers, -(Hyphen), _(Underscore).
3) File is damaged or not in correct APP file format
4) Wrong OS or APP selection
5) LIAPP is already applied or another security program is applied

If none of the above applies but application continues to fail, please send the following to support@lockincomp.com:
- Email, APP Name, Application Type (TEST/PROTECT), Application Time, Error Message
If possible, sending the APP file together will allow for faster and more accurate guidance.

You can easily check LIAPP application status using compression programs (Android APK files only).
1) Download file after LIAPP application
2) Open downloaded file using compression programs like 7-Zip, WinZip
3) Check if LIAPP-related files exist in the assets folder

The above method is for simply checking LIAPP application status as a first step.
Please conduct installation and operation testing before distribution.

Android APK files downloaded after LIAPP application must be signed and zip-aligned.
Unsigned APP files cannot be installed on devices.
Non-zip-aligned APP files may not be registered in markets.
Please ensure signing and zip alignment for APP files protected with LIAPP.

For detailed information on signing and zip alignment, please refer to the Android developer site.
Google Signing Guide
Google zipalign Guide

There are various reasons why apps won't install.
Among them, reasons for installation failure after protection with LIAPP are broadly divided into three categories:

1) When signing is not done
This is situation 1) if you try to install immediately after downloading APP files protected with LIAPP.
Please proceed with installation after signing.

2) When android:extractNativeLibs='false' setting is applied in AndroidManifest
extractNativeLibs is an option to compress and store native libraries in apk, with default value true.
If the following error message appears during apk installation, please change the AndroidManifest setting to android:extractNativeLibs='true'.
[INSTALL_FAILED_INVALID_APK: Failed to extract native libraries]

3) When signing is done but APK Signature Scheme v2 was applied before protection with LIAPP
You can check APK Signature Scheme v2 application using the following command:
- java -jar [apksigner.jar_PATH] verify -v --print-certs [apkfile_PATH]
Apk files previously signed using APK Signature Scheme v2 cannot be installed if content is changed.
To use APK Signature Scheme v2, you must sign using apksigner after applying LIAPP.
APK Signature Scheme v2 requires zipalign before signing.
For application methods and detailed information about APK Signature Scheme v2, please refer to the links below.

[LIAPP TECH] Signing with apksigner and APK Signature scheme v2
[Android Official] APK Signature Scheme v2
[Android Official] APK Signature Scheme v2

If you are using APK Signature Scheme v1, please refer to the link below.

[LIAPP TECH] Signing with jarsigner and APK Signature scheme v1

If none of the above applies but installation continues to fail, please send the APK file protected with LIAPP to support@lockincomp.com.

If apps won't run, please check and change the following protection options:
Class Protection: If unnecessary Classes are protected, check after deleting Classes
NLP(Native Library Protection): If multiple files are protected or security programs or external library files are protected, check after excluding files
When using DRM provided by Market: Apply Used Market DRM function in additional features menu and check
When using Google Play App Signing provided by Google Play Console: Apply Used Google Play App Signing function in additional features menu and check
If the app still doesn't run after checking the above or if you have questions, please send the APK file protected with LIAPP and the following information to support@lockincomp.com:
- Email, device model name, OS version, carrier, error message or unusual symptoms

The procedure for distributing apps with LIAPP applied is no different from previous distribution procedures.
Just follow the same procedure you used to distribute to each APP market.
However, depending on the market, files for distribution may need signing and zip alignment.
For Google store, signing and zip alignment must be done before uploading files.
Amazon App Store requires uploading unaligned files.

Apps may not register in markets for the following reasons:
1) When the signing key differs from previously registered apps
2) When signing with apksigner instead of jarsigner is required (when targetSdkVersion=30 or higher is set)
3) When zip alignment is not done (does not apply to Amazon App Store)
4) When debug mode is enabled
5) When file size limit is exceeded
6) Others

If registration fails, please send the relevant information to support@lockincomp.com and we will check and provide guidance.

LIAPP service is only provided to registered users and can be used after membership registration.
Membership registration is free and you can use LIAPP service immediately after logging in after registration.

Yes, it is possible. LIAPP can perfectly protect mobile games developed with various frameworks including not only Unity but also Native, Unreal Engine, and Cocos.

Yes, LIAPP also supports mobile apps developed with Flutter. Security application can be applied to completed APK (or AAB), iPA files after development, so Flutter apps can also apply LIAPP security based on .apk or .aab files. Therefore, obfuscation, tampering prevention, RASP, etc. can be applied to Flutter apps without separate plugin development.

Yes, LIAPP also supports apps developed with React Native. Security is applied to final built Android (.apk or .aab) and iOS (.ipa) files, so native code-based protection is possible. React Native apps can also apply various security functions such as code obfuscation, tampering prevention, runtime protection (RASP) through LIAPP.

Yes, LIAPP perfectly supports mobile apps developed with Unity engine. Security is applied based on final built Android (.apk or .aab) and iOS (.ipa) files generated from Unity apps, and can obfuscate source code and defend against tampering and hacking attempts. LIAPP provides effective security solutions especially in environments requiring response to game hacking, payment bypass, and memory manipulation.

Yes, LIAPP also supports mobile apps developed with Unreal Engine. LIAPP can be applied to Android (.apk or .aab) and iOS (.ipa) files that are build results of apps created with Unreal to use various security functions such as code obfuscation, tampering prevention, and runtime protection. LIAPP can work effectively in Unreal-based game apps requiring game hacking response or payment security.

Yes, LIAPP also supports apps developed based on Cocos including Cocos2d-x and Cocos Creator. LIAPP can be applied to final built Android (.apk or .aab) and iOS (.ipa) files of apps created with Cocos to use code protection, tampering prevention, and runtime detection functions. LIAPP is a suitable security service for Cocos-based games requiring security such as game hacking, reverse engineering, and payment bypass prevention.

Yes, LIAPP also supports iOS apps developed with Objective-C. Security application is based on final built .ipa files and can apply obfuscation, tampering prevention, runtime protection (RASP), etc. for Objective-C code. LIAPP protection functions can be used without problems even in projects mixed with Swift.

Yes, LIAPP fully supports iOS apps developed with Swift. It can be applied to Swift-only apps as well as projects mixed with Objective-C, providing code protection, tampering prevention, and runtime security functions based on built .ipa files. Apps developed with Swift can enhance app security by integrating well with Apple platform security features.

Yes, LIAPP perfectly supports Android apps developed with Java. Various security functions such as obfuscation, integrity checks, and tampering prevention can be applied to Java-based source code. LIAPP can effectively protect Java apps that are particularly vulnerable to reverse engineering and memory hacking.

Yes, LIAPP perfectly supports Android apps developed with Kotlin just like Java. LIAPP can equally apply various security functions such as obfuscation, tampering prevention, debugging detection, and runtime protection (RASP) to Kotlin code as well. It works without problems even in projects where Java and Kotlin are mixed, supporting LIAPP protection based on built .apk or .aab files.

When developing apps, personal information should be stored encrypted and transmitted safely through HTTPS and SSL Pinning. Additionally, various security functions such as key input protection (secure keypad), screen capture prevention, and rooting detection should be applied together to safely protect personal information. LIAPP provides integrated provision of these functions without code modification, allowing rapid enhancement of personal information protection levels.

Official app stores only check pre-installation security during review, so they cannot prevent personal information leaks during app execution. LIAPP detects and defends against threats during execution, protecting personal information in actual user environments.

Input values in mobile apps should be protected from the input stage with secure keypads to be safe from attacks such as keylogging and hooking. LIKEY is a mobile app secure keypad that provides a safe input environment and supports screen capture blocking.

Rooted and jailbroken devices have basic system protections disabled, making sensitive information easily stolen. In particular, modified devices bypass basic security protocols and become pathways for cyber attacks, causing data breaches and security threats to entire networks, potentially exposing personal information. LIAPP automatically detects rooting/jailbreak status and restricts app execution.

LIAPP detects based on threat behaviors rather than checking installed apps, so it safely protects apps without requesting the QUERY_ALL_PACKAGES permission that general mobile app security companies require. LIAPP minimizes unnecessary permissions to protect user privacy.

QUERY_ALL_PACKAGES permission is a sensitive permission that allows querying the list of all apps installed on the device in Android 11 (API 30) and above. Most mobile app security companies use this permission to detect the presence of remote control apps, hacking tools, and malicious apps to enhance security during app execution. However, LIAPP detects based on threat behaviors rather than checking installed apps, so it safely protects apps without requesting QUERY_ALL_PACKAGES permission.

No, LIAPP does not collect user personal information or input values. When threat behaviors such as tampering, rooting, and debugging are detected in the app execution environment, only OS version and device model information is collected, and user identification information is not stored or transmitted. LIAPP prioritizes personal information protection and complies with major regulations such as GDPR and domestic personal information protection laws.

To use LIAPP service, you must first register as a member.
After membership registration and login, you can proceed with payment through the payment menu.

Payment is only possible with credit cards. If you want to pay with other payment methods besides credit cards, please contact us.

Ticket and Monthly License are items that can be used after purchase and have the following characteristics:

*Ticket
Ticket is a consumable item and can be used in LIAPP ON-SITE service.
Tickets can be acquired through purchase or participation in events conducted by our company.
Owned tickets are used one by one each time PROTECT is applied.
Used tickets cannot be recovered, so we recommend sufficient review using TEST application service before using tickets.

*Monthly License
Monthly License is a term-based product and can use LIAPP ON-SITE or LIAPP BUSINESS service.
To purchase Monthly License, apps must be registered first.
Monthly License is not applied to all owned apps when purchased but requires individual purchase for each app.
When Monthly License is purchased, the corresponding app can apply PROTECT unlimited times during the validity period.

Apps protected with LIAPP using tickets or licenses can be used permanently.
However, apps applied with TEST can be used for 2 days and will not run after 2 days.

Annual licenses can also be purchased.
However, direct payment through the website is not possible.
For inquiries about products that cannot be paid for on the website such as annual licenses, please use CONTACT at the top or contact the company.

Recurring billing refers to a service where payment is made regularly every month based on the time of Monthly License purchase.
It is a payment service provided for your convenience so you don't have to repurchase Monthly License every month.
When purchasing Monthly License, recurring billing is automatically activated and payment proceeds on the same date every month with usage period automatically extended.
If you don't want to use recurring billing, please send related information (Email, name, contact, payment date, purchased product, license purchase app, order number) to support@lockincomp.com.

Purchased tickets have no separate expiration date.

Purchased tickets can only be canceled (withdrawal of subscription) within 7 days if unused after payment.
Purchased licenses can be canceled (withdrawal of subscription) or refunded according to the following conditions:

✔Cases where payment cancellation (withdrawal of subscription) is possible
Payment cancellation is possible if requested within 7 days only when there is no PROTECT history using tickets or licenses after payment.
To cancel payment, please send related information (Email, name, contact, payment date, purchased product, license purchase app, order number, cancellation reason) to support@lockincomp.com.

Mobile app security is technology that protects apps to operate safely from various external attacks such as hacking, tampering, and data leaks. The core is to defend app source code, data, and execution environment in multiple layers, and LIAPP is a mobile app security service that comprehensively protects entire apps.

Mobile app hacking can cause serious problems such as personal information leaks, payment fraud, and corporate credibility decline.
If apps themselves are not protected, both users and companies are exposed to danger. LIAPP plays a role in blocking such threats in advance.

Various technologies such as source code protection, tampering/modification prevention, memory protection, game engine protection, debugging, rooting, virtual machine, and hacking tool detection can be applied to mobile apps. LIAPP provides all these security functions comprehensively.

Of course developers can implement directly, but implementation complexity and maintenance costs are very high. LIAPP is a security service that can be quickly applied without separate code modification.

LIKEY is a mobile security keypad service designed to strongly protect user personal information entered through virtual keypads. LIKEY is a mobile-only security keypad that ensures strong security for user information protection, convenience for server administrators, and allows design settings that match brand image.

A mobile app security keypad is a dedicated input tool that protects sensitive information such as passwords and card numbers entered by users from keylogging, screen capture, and hooking attacks. While regular keypads can expose input values at the system level, mobile app security keypads encrypt screen output and input values and strengthen security through randomization of number or character arrangements.

As mobile financial transactions and e-commerce rapidly increase, entering important personal information such as passwords through virtual keypads on touch screens in mobile environments is becoming common. Security-vulnerable virtual keypads are major attack targets for hackers, and personal information is stolen and leaked through illegal routes such as keyloggers and hooking, being used for serious secondary crimes, so security keypads should be used to prevent this.

Financial/payment apps handle sensitive data such as passwords, card numbers, and account information, so security keypad use is practically essential according to electronic financial transaction laws and electronic financial supervision regulations. LIKEY provides input protection functions optimized for financial environments and protects against information leak risks through keylogging and input hooking.

Yes, LIKEY encrypts key input values during key input to block hooking or keylogging attacks.

Rooted/jailbroken devices have weakened system security, making key inputs easily stolen, so protection with regular keypads is difficult. Mobile app security keypads can minimize risks even in such environments by encrypting input paths or protecting screen output itself. LIKEY maintains key input security even in rooting/jailbreak environments.

LIKEY is a custom app security keypad that allows developers to set desired designs and functions. You can directly set keypad colors, themes, button sizes, etc. and customize designs to provide user-friendly layouts that improve user UX. The ability to apply brand colors and logos to keypads provides consistent brand experience. LIKEY is a customized mobile security keypad that can consider both security and user experience simultaneously.

Customization is possible for mobile app security keypads. LIKEY breaks away from existing stuffy and crude keypad designs and can be designed to match customer company BI, CI colors and atmosphere, and can change keypad background, top bar, button size, margin settings, arrangement spacing, colors, etc. according to customer requests to match applications.

Generally, security keypads are designed with lightweight structures and do not significantly affect overall app performance. LIKEY is performance-optimized and can satisfy both security and UX.

LISS is a powerful mobile app screen protection service that detects remote control apps and prevents screen capture in mobile environments. LISS blocks visual information leaks that can occur during app execution, dramatically enhancing security levels of apps handling sensitive information such as finance, healthcare, and commerce, and protects content copyrights. It provides SDK in library form to be embedded in apps, providing consistent protection functions across various device environments without additional development.

Detection is necessary to prevent mobile app systems from being remotely controlled due to malware infection. If attackers use remote control tools, they can cause various security threats such as malware infection, personal information leaks, and cyber attacks.

The screen capture prevention function blocks visual replication activities such as screenshots, screen recording, and mirroring while the app is running. LISS blocks screen capture itself based on this method and prevents information leaks by blur-processing only sensitive screens with black screens.

Screen recording prevention is very useful when personal information, financial information, authentication codes, paid content, etc. are displayed on app screens. For example, if OTP display, payment screens, healthcare personal data, educational content, etc. are recorded, information leaks or unauthorized copying can occur. LISS blocks recording/copying attempts of such sensitive screens or blur-processes them with black screens to prevent visual information leaks.

LISS can be applied to all apps handling sensitive information such as finance, payment, healthcare, games, education, commerce, and enterprise internal apps (B2E). It is particularly useful for apps that need protection from visual leak threats such as screen capture, recording, and mirroring of user personal information, authentication information, and paid content.

LISS provides SDK in library form to be embedded in apps, minimizing resource investment from app service development teams.

LISS has almost no impact on app execution speed or user experience. Security processing occurs in the background, and screen capture/recording detection or blocking operates with minimal resources. LISS is designed considering both performance and security, enabling stable operation even in sensitive app environments.

Apps protected with LIAPP can also use DRM functions provided by Markets.
To use DRM provided by Markets, select the Used Market DRM option in the additional features menu when applying LIAPP.

To use DRM provided by Google Play Console, select the Used Google Play App Signing option in the additional features menu when applying LIAPP.

When LIAPP functions or modules are updated, we will send guidance to your registered email.
After receiving guidance, you must reapply LIAPP on the site for updated content to be reflected.
Updated content cannot be automatically updated to already applied LIAPP without reapplication.

When apps are modified, LIAPP must be reapplied and distributed.
If distributed without reapplication, unprotected apps will be installed.
When modifying or updating apps, please ensure to apply LIAPP before distribution.

While protection functions are maintained even with one-time LIAPP application, regular maintenance is necessary because security threats continue to evolve. To respond to regular app updates, operating system changes, and new hacking techniques, it is safe to periodically reapply LIAPP protection or adjust settings. LIAPP supports easy modification of security policies and rebuilding through the console.

This is possible with LIAPP's Premium PLAN.
On-SITE and BUSINESS PLANs are lightweight versions that do not communicate with servers and are not supported, while Premium PLAN allows real-time security policy changes through the LIAPP management console.

LIAPP is a solution that protects APPs installed on smart devices.
To prevent smart device hacking, you must directly install and use security programs such as antivirus software.

LIAPP supports Android and iOS.
Android apps can apply all LIAPP functions.
Supported Android versions range from 2.2 (Froyo) to recently released versions.

iOS apps cannot apply some functions according to Apple Store policies.
Supported iOS versions range from 5.2 to recent versions.

If Rooting Detection function is not applied, it can be used on rooted devices.
Rooted devices are relatively vulnerable to security and can pose threats to apps, so caution is needed.
Rooting Detection function can be changed in the APP Protection menu.

Apps protected with LIAPP may have slower speed during initial execution because decryption processes are required.
Only during the first execution after installation may take less than 1 second longer depending on the device.
However, from subsequent executions, there is almost no difference from before LIAPP protection.

Apps installed on devices to bypass payments can be defended through Hacktools Detection function.
Hacktools Detection function can be set in the APP Protection menu.
Rather than detecting payment bypass, it is better to apply a method of verifying paid receipts.

Apps protected with LIAPP can be used regardless of device network connection status.
If user information function is applied, user information is not transmitted in offline status.
*User information function is scheduled to be provided later.

LIAPP protects mobile games while respecting game companies' operating methods as much as possible. LIAPP can customize settings to enable operation on specific virtual machines or emulators.

Even in environments where LIAPP allows virtual machines or emulators, it safely protects game apps by providing powerful variable encryption functions that prevent changes to important assets or items in games and cloud device detection functions that provide various threat environments.