Table of Contents

Mega FAQ

During development, encountering issues is inevitable. This article aims to help you quickly locate and resolve common problems. We start with a list of frequently asked questions (FAQ). If you don’t find the answer here, please refer to the following sections or submit an issue report to us.

Frequently asked questions (FAQ)

Here are some of the most common issues developers face when integrating and using EasyAR Mega, along with their solutions.

Q: Why does my app prompt invalid key?

A: This is usually caused by the following reasons:

  1. License is invalid or expired
  2. License does not match Bundle ID/Package Name
  3. XR headset requires a separate XR License
  4. Custom camera functionality requires a commercial license
Q: Why is there a watermark on my app?

A: This indicates you are using a trial license instead of a commercial license.

Q: Why does my app show a countdown prompt (timeout within * seconds)?

A: This is a limitation during the trial period. Using a commercial EasyAR Sense license and commercial EasyAR Mega service will resolve this issue.

Q: Why does my app display a black screen upon opening?

A: This situation usually prints the error reason in screen information or logs. You can resolve it based on the specific cause printed by the system. If unresolved, please provide technical information (including logs, screenshots, detailed device information, etc.).

Q: Why can't my app localize, returning a NotFound status continuously?

A: This is usually caused by the following reasons:

  1. Localization service is still initializing:
    The localization service hasn't fully loaded all Mega maps yet, so localization in certain areas cannot be guaranteed.
  2. Outside map coverage area:
    Ensure your current physical location is within the coverage area of your loaded Mega map.
  3. Incorrect simulation test configuration:
    Not running on-site, but MegaLocationInputMode is incorrectly set to Onsite.
  4. Poor environmental conditions:
    Extreme lighting (too dark or bright) or large areas of plain-colored walls/floors (e.g., white walls, polished floors) will affect visual localization.
Q: Why can't my app localize, returning abnormal status?

A: This is usually caused by the following reasons:

  1. Request timeout:
    The system returns RequestTimeout.
  2. Request interval too short:
    The system returns RequestIntervalTooLow.
  3. Other abnormal errors:
    The system returns UnknownError. Typically, such exceptions indicate connection/transmission failures or errors in the Mega service itself. Details can be obtained via the MegaBlockLocalizationResponse.ErrorMessage interface.
Q: Why did my Mini Program fail to apply for plugin usage?

A: This is because Mini Program plugins do not support "guest mode" in WeChat Developer Tools, nor do they support Mini Programs with an individual account subject. Please apply using a corporate WeChat Mini Program AppId.

Q: Why was my mini-program authorization not approved?

A: You need to obtain the Mega mini-program plugin license from the development center and ensure that the AppId you are using matches the one in the license.

Q: Why can't my mini-program work on XX phone?

A: The integration of Mega in the mini-program relies on WeChat's VisionKit component. Refer to the WeChat documentation for system requirements and supported device lists.

Q: The localization succeeded, but the virtual content appears misaligned or drifting?

A: Issues related to localization effects are often complex. Possible reasons include:

  1. Mapping accuracy issues:
    The Mega map of the area itself may have accuracy errors. This usually occurs during the map collection or reconstruction phase. Please contact the business team for confirmation.
  2. Initialization jumps:
    During the first few seconds of localization, slight jumps may occur. This is due to the device's SLAM system not completing initialization, which is particularly noticeable in WeChat mini-programs (and may take longer on some devices).
  3. Dynamic environmental changes:
    Significant changes in the physical environment (e.g., moving large setups or adding temporary displays) may cause the map to mismatch reality. In such cases, the map needs to be updated.
  4. Device system errors:
    Most devices accumulate SLAM system errors over prolonged continuous operation, leading to drift.
  5. Localization error issues:
    Visual localization inherently has accuracy errors, which usually do not affect the visual experience of virtual content. If the error is large enough to cause noticeable misalignment or drift, detailed data is required for analysis and resolution. Refer to the methods described in Problem diagnosis and reporting to collect and provide feedback.
Q: How to collect and use EIF data for debugging?

A: EIF data is a powerful debugging tool. Refer to the following sections:

  • How to collect: Read Recording simulated runtime data to learn how to record EIF files on mobile devices or headsets.
  • How to replay: Depending on your development environment (Unity or WeChat mini-program), refer to the corresponding replay guide in that section.

Finding more specific help

If the above FAQ does not resolve your issue, you can visit the following topic pages for more in-depth solutions:

Reporting a new issue

If you encounter an issue not covered above, which may be related to the SDK or the platform itself, please help us improve the product. For detailed steps or guidance, refer to: Issue reporting.

Before submitting a report, ensure you have the following information ready, as it will greatly assist us in resolving the issue:

  1. Issue description: Clearly describe the problem, its frequency, and the steps to reproduce it.
  2. Device information: Device model, operating system version, and EasyAR SDK version.
  3. EIF data: Provide the EIF recording file that can reproduce the issue. This is the most critical diagnostic material.
  4. Log files: Complete application logs (Logcat or Console output).
  5. Screen recording or screenshots: A screen recording or screenshot of the issue occurring.

Please submit the above information via forum, email, or business contact. Thank you for your feedback!