Skip to main content

INTLBugly and INTLCrashSight Plugin Removal Guide

  1. Remove the INTLBugly and INTLCrashSight plugins in the Assets/Plugins directory.

    • iOS: Remove the INTLBugly and INTLCrashSight plugins under the Assets/Plugins/iOS/INTLSDK path.

      Image: Plugin removal for iOS

    • Android: Remove the INTLCrashSight.aar and INTLBugly.aar files under the Assets/Plugins/Android path.

      Image: Plugin removal for Android

  2. Remove the CrashSight and CrashSight configurations in the INTLConfig.ini file.

    Image: RemoveINTLFirebaseCrashsight4

    Image: RemoveINTLFirebaseCrashsight5

    Image: RemoveINTLFirebaseCrashsight6

  3. Remove the INTLBugly and INTLCrashSight parts under the Assets/INTLSDK/Scripts path.

    1. Remove the INTLCrashSight and INTLBugly folders. The logic here is that when an Unity sample test exception occurs, the Unity project automatically locates the code captured after automatic initialization in the file under this path.

      Image: RemoveINTLFirebaseCrashsight3

    2. Remove the code related to CrashSight and CrashSight left in Assets/INTLSDK/Scripts/INTLCore/Scripts/INTLAPI.cs. For example, code related to SetCrashSightAppVersion and SetBuglyAppVersion.

      info

      The game team can choose to delete or retain this code, and also delete or retain the code related to the internal calls of CrashSight and CrashSight.

  4. If the project has integrated with the plugins for PC, remove the TQM64 folder, Gbspy64.dll file, GameBabyConfig64.dat file, and INTLCrashSight.dll file in Assets/Plugins/x86_64.

    Image: /RemoveINTLFirebaseCrashsight7