Table of Contents

Troubleshooting: content not displaying/activating

During the use of cloud image recognition, you may encounter issues where virtual content fails to display or activate. This article provides systematic troubleshooting methods. It is important to note that in most cases, the reasons for cloud image recognition failure are identical to those for local recognition failure. Please refer to the Troubleshooting section for planar image tracking. This section only supplements issues and solutions specific to cloud recognition.

Common causes and troubleshooting methods

Network connection issues

Symptom: No response after sending a recognition request, or an error code is returned.
Troubleshooting methods:

  • Check if the device is connected to the internet (Wi-Fi/4G/5G), try opening a webpage to verify.
  • Check if the app has network permission enabled.
  • Capture network error logs in the code.
  • Test CRS API connectivity in a browser (reference: Health Check | GET /ping).

Improvement suggestions:

  • Add network status detection within the app, providing prompts in weak network conditions.
  • Set request timeouts with retries or fallback to local tracking.

Service configuration errors

Symptom: Recognition request is rejected, returning Unauthorized or Invalid Key.
Troubleshooting methods:

  • Check if the CRS API Key and Secret entered in the code are correct.
  • Verify that the Client-end URL entered in the code is correct (e.g., not mistakenly filled with the Server-end URL).
  • Confirm the License Key is activated and not expired (view in the EasyAR official website account center).

Improvement suggestions:

  • Use the Copy button in the CRS image library to copy your relevant service configurations, ensuring accurate entry.

Target library/application configuration errors

Symptom: A target image that was recognized successfully in the past now fails.
Troubleshooting methods:

  • Retrieve the target status via the CRS API to confirm it is in the "activated" state ("active":"1").
  • Check if the target ID exactly matches the one in the code (case-sensitive).

Improvement suggestions:

  • Ensure specific targets in the app are always activated when the cloud image library is updated/modified.
  • Conduct thorough code reviews.

Local loading failure in hybrid mode

Symptom: Cloud recognition succeeds, but local tracking fails to start, and content does not display.
Troubleshooting methods:

  • Confirm no exceptions are thrown during local ImageTarget loading (check logs).
  • Verify if the ImageTracker is enabled.

Improvement suggestions:

  • Wrap local loading logic with try-catch, capture exceptions, and retry.
  • Ensure virtual content is a child object of ImageTarget and is not disabled.

Summary and best practices

Content not displaying issues in cloud recognition mainly focus on three aspects: network, service configuration, and target status. Hybrid mode also requires attention to the local loading process. It is recommended to troubleshoot in the following priority order:

  1. Check network connectivity and confirm CRS service accessibility;
  2. Verify service settings: License, API Key/Secret, Client-end URL.
  3. Check the status of target images in the CRS library, ensuring target IDs match between the library and the application;

For complex issues, enable EasyAR debug logs or contact technical support.