Mega frequently asked questions

Encountering issues during development is inevitable. This guide aims to help you quickly locate and resolve common problems. We start with a frequently asked questions (FAQ) list. If you don't find your answer here, please refer to subsequent sections or submit an issue report to us.

Frequently asked questions (FAQ)

Below are some of the most common issues developers encounter 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. Head-mounted devices require a separate XR License
4. Custom camera features require a formal version License

Q: Why is there a watermark on my app?

A: This indicates that the License you are using is a trial version, not a formal version.

Q: Why is there a countdown prompt (timeout within * seconds) on my app?

A: This is a limitation during the trial product period. Using the formal version of EasyAR Sense authorization and formal version EasyAR Mega service can solve this problem.

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

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

Q: Why can't my app locate, and the return status is always NotFound?

A: This is usually caused by the following reasons:

1. Location service is still starting up:
   At this time, the location service has not fully loaded all Mega maps, so it cannot guarantee successful positioning in a certain area.
2. Not within the map coverage area:
   Ensure that your current physical location is within the coverage area of the Mega map you loaded.
3. Simulation test configuration error:
   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, polished floors) can affect visual positioning.

Q: Why can't my app locate, and the return status is abnormal?

A: This is usually caused by the following reasons:

1. Request timeout:
   At this time, the system will return RequestTimeout.
2. Request interval too short:
   At this time, the system will return RequestIntervalTooLow.
3. Other abnormal errors:
   At this time, the system will return UnknownError. Generally, such exceptions correspond to failures in the connection or transmission process, or errors in the Mega service itself. You can obtain detailed information through the MegaBlockLocalizationResponse.ErrorMessage interface.

Q: Why did my mini-program application for plugin usage fail?

A: This is because mini-program plugins do not support use in the "guest mode" of the WeChat developer tools, nor do they support use on mini-programs with an individual as the subject. Please use a WeChat mini-program AppId with an enterprise as the subject to apply.

Q: Why is my mini program authorization not approved?

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

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

A: Integrating Mega into the mini program relies on WeChat's VisionKit component. Refer to the WeChat documentation for its system requirements and supported device list.

Q: Localization succeeded, but the virtual content appears offset or drifting?

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

1. Mapping accuracy issues:
   The Mega map of this area may have inherent accuracy errors. This usually occurs during map collection or reconstruction. Contact business support for confirmation.
2. Initialization jitter:
   During the first few seconds of localization, the position may jitter slightly. This is caused by the device's SLAM system not completing initialization, which is particularly noticeable in WeChat mini programs (and may take longer on some devices).
3. Environmental dynamic changes:
   Significant physical changes (e.g., moving large furniture, adding temporary display boards) may cause the map to mismatch reality. Updating the map is required in such cases.
4. Device system error:
   Most devices accumulate SLAM system errors during prolonged continuous operation, leading to drift.
5. Localization error issues:
   Visual localization inherently has accuracy errors, which usually don't affect the visual experience of virtual content. If the error causes noticeable offset or drift, detailed data is needed for analysis and resolution. Refer to the methods described in Problem diagnosis and reporting to collect data 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 phones 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 doesn't resolve your issue, you can visit the following specialized pages for more in-depth solutions:

• Content not displayed - Focuses on troubleshooting content rendering issues.
• Content drift - In-depth analysis of content drift.
• WeChat Mini Program integration known issues - Summary of special issues specific to the mini program platform.

Reporting a new issue

If you encounter an issue not covered above, suspected to be related to the SDK or platform itself, please help us improve our product. Detailed steps or guidance can be found in: Issue reporting.

Before submitting a report, ensure you have the following information ready, as it greatly assists us in resolving the problem:

1. Issue description: Clearly describe the problem's symptoms, occurrence frequency, and steps to reproduce.
2. Device information: Device model, operating system version, EasyAR SDK version.
3. EIF data: Must provide the EIF recording file that can reproduce the issue. This is the most critical diagnostic evidence.
4. Log files: Complete application logs (Logcat or Console output).
5. Screen recording or screenshots: Screen recordings or screenshots captured when the issue occurs.

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