05/15/2024 15:19:45

Problem description

There is no reported "XXX" information in the attachment information of the iOS Bugly console

Solution

Step 1: Refer to Set additional log/binary data reporting in case of crash documentation to check the code.

Note:
Bugly platform design; iOS only supports uploading additional logs but does not support binary files.

Step 2: After turning on the MSDK DEBUG switch, you can retrieve "attachmentForException message: " in the log and observe whether it has entered the OnCrashBaseRetEvent/OnCrashExtraMessageNotify callback.

1. If it can be retrieved, this means that it has entered the above callback. At this case, you can continue to perform Step 3.
   
2. If it cannot be retrieved, this means that it has not entered the above callback and that it may hit the exception reporting self-defined in Bugly SDK iOS and cannot trigger this callback. The logic can be triggered only when the game/app crashes. You can continue to perform Step 3 after you modify it.
   

Note:

1. The self-defined exception reporting in Android will trigger this callback.
   
2. Whether the game/app really crashes cannot be judged based on the phenomenon alone. iOS crashes mainly include nsexception and signal exception. This condition can be met by ensuring that the crash stack captured by the system can be seen in the log. Under normal circumstances, you can refer to the "int*p = null; p = 1;" code to get a null pointer exception for trial.
   

Step 3: When the above steps and self-check are all satisfied, you can go to the additional data of Bugly iOS console to view the reported "XXX" information. (View path: Bugly iOS console -> Corresponding exception details -> Tracking data -> The crash_attach.log file in the attachment information)

Note:
It is needed to ensure that BUGLY_APP_ID_IOS in MSDKConfig.ini is the same product as the Bugly iOS console accessed. You can confirm this through the link. For example, if BUGLY_APP_ID_IOS is 900005145, the corresponding Bugly iOS console link should also carry "900005145", such as https://bugly.qq.com/v2/crash-reporting/dashboard/900005145?pid=2.