Maps troubleshooting

Available in Classic and VPC

You might run into the following problems when using Maps. Find out causes and possible solutions.

Troubleshoot API authentication error in Web Dynamic Map issues

An API authentication error occurs in Web Dynamic Map.

Cause

• The service URL includes a port number and a URI.
• A parameter in the script has been entered incorrectly.

Solution

Check service URL
Service URLs should only register the host domain and exclude the port number and URI. To check the service URL:

1. In the NAVER Cloud Platform console, navigate to Menu > All Services > AI NAVER API > Application.
2. Confirm the name of the app, then click [Credentials].
3. Check the Web service URL information in the Service environment component.
4. If there is a port number or URI included in the service URL, delete it.
   Example:
   • http://localhost:8080 → http://localhost
   • http://127.0.0.1/main → http://127.0.0.1

Check script parameters
Check and edit the parameters in the script.

• ClientID → ncpClientID

Troubleshoot 429 error when searching an address on Web Dynamic Map issues

A 429 (too many requests) error occurs when searching an address in Web Dynamic Map.

Cause

To call the API that converts addresses to coordinates, you must subscribe to the Geocoding service. If you do not subscribe to the Geocoding service, this error may occur.

Solution

To subscribe to the Geocoding service:

1. In the NAVER Cloud Platform console, navigate to Menu > All Services > AI NAVER API > Application.
2. Confirm the name of the Maps app, then click [Edit].
3. Click to select the checkbox for Geocoding.
4. Click [Save].

Troubleshoot 500 error when calling Web Dynamic Map on Android 9 or above issues

A 500 error occurs when calling the Web Dynamic Map on Android 9 or above.

Cause

This phenomenon is unrelated to the Maps API and occurs because http plaintext communication is blocked in Android 9 and higher versions.

Solution

• Rather than using file://, host the HTML with the Maps interface on a web server with TLS enabled (https).
• Go to Network security configuration in the app and allow plaintext communication with *.map.naver.com and *.map.naver.net. However, since Android recommends applying TLS to all communications, allowing plaintext communications is not recommended.

Troubleshoot Marker locations are different when searching using coordinates and addresses issues

Marker locations are different when searching maps using coordinates than when searching maps using addresses.

Cause and solution

When searching using coordinates, the exact location value on the Maps is displayed as the marker location, while when searching using an address, the center point of the address range is displayed as the marker. As a result, marker locations may differ between searches using coordinates and searches using an address.

Troubleshoot Reverse Geocoding feature issues

Mobile Dynamic Map v3 does not have a Reverse Geocoding feature (feature that returns coordinate values as addresses).

Cause

Mobile Dynamic Map SDK v2 features Reverse Geocoding feature, but Mobile Dynamic Map SDK v3 does not.

Solution

To use this feature, you have to call the Reverse Geocoding APIs directly. For a detailed description of the Reverse Geocoding APIs, see Reverse Geocoding API.

Troubleshoot Korean domain authentication error issues

Korean domains are not authenticated in the Web Dynamic Map service.

Cause

As each browser handles Korean domains differently, there is a risk of authentication errors occurring.

Solution

If you need to register a Korean domain in the Application Web service URL, convert the value for the Korean domain to Punycode before registering it.

1. Go to Punycode converter to convert the Korean domain to Punycode.
2. In the NAVER Cloud Platform console, navigate to Menu > All Services > AI NAVER API > Application.
3. Take the value converted by the Punycode converter and register it in the Web service URL of the Maps app.

Troubleshoot CORS errors issues

A CORS error occurs when calling the Maps APIs.

Cause

If the Maps APIs does not allow Cross-Origin Resource Sharing (CORS) due to security issues in a JavaScript environment, the following error may occur:
Access to XMLHttpRequest at '' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: It does not have HTTP ok status.

Solution

If you are in a JavaScript environment, try the method of setting up a separate backend server within the same domain and then calling the API from that server.

Learning resources

We offer various materials for you to explore. To learn more about Maps, check out these helpful links:

• FAQs: Maps FAQs
• Developer forum: Maps developer forum
• NAVER Map's Github: NAVER Map's Enterprise API