Testing, debugging

Available in Classic and VPC

You might run into the following problems when using App Safer. Find out causes and possible solutions.

Check correct application of App Safer

I want to check whether App Safer has been applied correctly.

Solution

Check logs

• On the NAVER Cloud Platform console, navigate to Menu > Services > Security > App Safer > App Management to check whether the app's fingerprint has been collected.
• If integrated with Effective Log Search & Analytics, check the initialization and detection logs on the event log page.

Additional security testing

• For rooting or emulator, root or use an emulator directly on the device.
• For debugging detection, click [Debug] in the IDE.
• Perform signature detection. To perform signature detection:
  1. Set the app's fingerprint to Collected status.
  2. Run the normal app to collect the correct fingerprint.
  3. Set the app's fingerprint to Uncollected status.
  4. Collect with an uncollected developer signature.

Debugging not possible

Debugging is not possible when App Safer is applied.

Cause

When App Safer is applied, the debugging protection function is also applied, which prevents debugging. Additionally, debugging logs may be difficult to access in IDEs (Android Studio, Xcode).

Solution

• For Android apps, use ''Logcat'' for debugging.
• For iOS apps, use the console app on Mac to perform debugging.

Android exceptions

An exception occurs when applying App Safer on Android, or exception logs are observed in Logcat.

ClassNotFoundException

Cause

When the antivirus policy is enabled during App Safer application, Kotlin classes are used internally, which may cause a ClassNotFoundException: kotlinx.coroutines.BuildersKt error in Java-based apps.

Solution

Add org.jetbrains.kotlinx:kotlinx-coroutines-core to the app-level dependencies.