Table of Contents

Record EIF data: High-fidelity evidence for reproducing AR issues

In augmented reality (AR) applications, some complex spatial localization issues, such as tracking jitter, virtual-real misalignment, and content drift, are often difficult to fully reproduce only through screen recordings or logs. For this reason, we provide the EIF data recording feature, a proprietary high-fidelity data dump format that can synchronously record the following key information:

  • Basic device information, such as model, system, and SDK version
  • Camera image frames with timestamps
  • Device camera intrinsic matrix and extrinsic matrix
  • IMU sensor data
  • Additional data from external auxiliary inputs, such as GNSS

Why is recording EIF data important?

Important

EIF data that can reproduce an issue is priceless.

EIF data can completely reproduce the detailed context when an issue occurs, allowing the development team to accurately reproduce the user's scenario in an offline environment and greatly improve issue localization efficiency. Compared with screen recordings or logs, EIF has the following advantages:

  1. Accurate reproduction: Developers can directly play back EIF data in debugging tools to reproduce the Bug you encountered.
  2. Low-level diagnostics: Through comprehensive analysis of various types of data, such as images, sensors, and external inputs, developers can determine which technical stage caused the issue.
  3. Time saving: Avoids lengthy communication loops and significantly shortens the cycle from reporting an issue to resolving it.

How to record EIF data

EasyAR provides two ways to record EIF data.

  1. Directly use APIs provided by the SDK to implement EIF data recording in your application.
  2. Use the official Mega Toolbox App. This is usually suitable for EasyAR Mega development and issue feedback.

For detailed steps, refer to our technical documentation to obtain operation guides for your usage method and device.

Tip

Visit the following link to learn how to implement in-app EIF recording by calling APIs: Input frame recording and simulated runtime.

Visit the following link to view the operation guide for using Mega Toolbox App: Use Toolbox to record mobile EIF files.

Brief recording process overview, using Mega Toolbox App as an example:

  1. Open Mega Toolbox App and tap On-site Verification and Diagnostics Tool.
  2. Log in to your account, select your localization library, and start testing.
  3. Try to reproduce your issue. Find an operation pattern that can stably reproduce the issue, such as device orientation, browsing method, or shooting point.
  4. After everything is ready, tap the red "Record" button to start recording.
  5. After the issue appears, tap the red "Stop and Save" button.
  6. The system will automatically generate an EIF file. Connect the device to a computer, export it to local storage, and submit it.
Note

EIF files may be large, from hundreds of MB to several GB. It is recommended to record only the core segment containing the issue, usually 10-30 seconds is enough.

Best practice suggestions

To ensure your feedback can be processed efficiently, include the following four types of information at the same time when submitting:

Information type Description
EIF data file Core diagnostic evidence, must include the issue reproduction process
Subjective phenomenon description Clearly describe the behavior you observed, such as "the navigation arrow suddenly jumped to the ceiling when turning left"
Screen recording or screenshot Helps visualize the issue and intuitively shows "what the user finally saw"
Auxiliary context information Includes:
• Your device model and operating system version
• The EasyAR SDK version used by your application
• Description of the environment where the issue occurred (indoor/outdoor, lighting, space size)
• Mega applications need to additionally provide localization library information, which can be exported from the Unity tool
• CRS cloud recognition applications need to additionally provide cloud recognition library information
Tip

Example: "Using EasyAR Sense Unity Plugin 4000.0.1 on Apple Vision Pro (visionOS 26), navigating in an indoor shopping mall, the navigation route suddenly became incorrect at a certain location. EIF file recorded: avp_wrong_path_20251218.mkveif, with screen recording, environment photos, and localization library information attached: MegaStudio_ServiceInfo_myaccount_2025-12-18_10-33-26.json."

By providing the complete information package above, you will significantly accelerate issue analysis and repair. Thank you for your cooperation!