Table of Contents

Mega FAQ

Problems during development are inevitable. This article is intended to help you quickly locate and resolve common issues. We start with a list of frequently asked questions (FAQ). If you cannot find an answer here, refer to the following chapters or submit an issue report to us.

Frequently asked questions (FAQ)

The following are some of the most common issues and solutions developers encounter when integrating and using EasyAR Mega.

Q: Why does my application show Invalid Key?

A: This is usually caused by one of the following reasons:

  1. The License is invalid or expired
  2. The License does not match the Bundle ID / Package Name
  3. Headset devices require a separate XR License
  4. The custom camera feature requires an official License
Q: Why does my application have a watermark?

A: This indicates that the License you are using is a trial version rather than an official version.

Q: Why does my application show a countdown prompt, timeout within * seconds?

A: This is a limitation during the trial product period. Using an official EasyAR Sense license and official EasyAR Mega service can resolve this issue.

Q: Why does my application open to a black screen?

A: In this case, the error reason is usually printed in on-screen information or logs. You can resolve it according to the specific reason printed by the system. If it cannot be resolved, provide technical information, including logs, screenshots, detailed device information, and so on.

Q: Why can't my application localize, and why does the returned status remain NotFound?

A: This is usually caused by one of the following reasons:

  1. The localization service is still starting:
    At this time, the localization service has not completely loaded all Mega maps, so successful localization in a certain area cannot be guaranteed.
  2. Outside the map coverage:
    Make sure your current physical location is within the coverage area of the loaded Mega map.
  3. Incorrect simulation test configuration:
    The application is not running on site, but MegaLocationInputMode is incorrectly set to Onsite.
  4. Poor environmental conditions:
    Extreme lighting, too dark or too bright, large areas of solid-color walls or floors, such as white walls or polished floors, can affect visual localization.
Q: Why can't my application localize, and why is the returned status abnormal?

A: This is usually caused by one of 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. In general, such abnormalities correspond to failures during connection or transmission, or errors in the Mega service itself. You can obtain details through the MegaBlockLocalizationResponse.ErrorMessage interface.
Q: Why did my Mini Program plugin usage application fail?

A: This is because Mini Program plugins do not support use in “visitor mode” in WeChat Developer Tools, nor do they support Mini Programs whose subject is an individual. Apply using the AppId of a WeChat Mini Program under an enterprise subject.

Q: Why was my Mini Program authorization not approved?

A: You need to obtain a Mega Mini Program plugin license from the developer center and make sure that the AppId you use is the same as the one in the license.

Q: Why can't my Mini Program be used on XX phone?

A: Integrating Mega in a Mini Program depends on WeChat's VisionKit component. For its system requirements and device support list, refer to WeChat documentation.

Q: Localization succeeded, but why does the virtual content position look offset or drifting?

A: Issues involving localization effects often have complex causes. Possible causes include:

  1. Mapping accuracy issue:
    The Mega map of this area itself may have accuracy errors. This usually occurs during the map collection or reconstruction stage. Contact business support for confirmation.
  2. Jumping during initialization:
    In the first few seconds after localization starts, the position may jump slightly. This is caused by the device's SLAM system not having completed initialization. This process is especially obvious in WeChat Mini Program, and it may even take a relatively long time on some devices.
  3. Dynamic environment changes:
    If the physical environment changes significantly, such as moving large installations or adding temporary display boards, the map may no longer match reality. In this case, the map needs to be updated.
  4. Device system error:
    After most devices run continuously for a long time, accumulated errors in their SLAM systems can cause drifting.
  5. Localization accuracy issue:
    Visual localization itself has accuracy errors. Usually, this kind of error does not affect the visual experience of virtual content. If the error is large enough to cause obvious offset or drifting, detailed data is needed for analysis and resolution. Refer to the methods described in issue diagnosis and report to collect data and provide feedback.
Q: How do I collect and use EIF data for debugging?

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

  • How to collect: Read collect simulated runtime data to learn how to record EIF files on a phone or headset.
  • How to replay: Depending on your development environment, Unity or WeChat Mini Program, refer to the corresponding replay guide in that section.

Find more specific help

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

Report a new issue

If you encounter an issue not covered above that appears to be related to the SDK or platform itself, please help us improve the product. For detailed steps or guidance, see: issue report.

Before submitting a report, make sure you have prepared the following information, which will greatly help us resolve the issue:

  1. Issue description: Clearly describe the issue behavior, frequency, and operation steps.
  2. Device information: Device model, operating system version, and EasyAR SDK version.
  3. EIF data: Be sure to provide the EIF recording file that can reproduce the issue. This is the most important diagnostic evidence.
  4. Log files: Complete application logs, Logcat or Console output.
  5. Screen recording or screenshots: Screen recording or screenshots when the issue occurs.

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