Maps troubleshooting

Available in VPC

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

Troubleshoot API authentication error in Dynamic Map

An API authentication error occurs in 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
For the service URL, register only the host domain, excluding the port number and URI. To check the service URL:

1. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > All Services > Application Services > Maps.
2. Click the Application menu.
3. From the list, select Application, then click [Authentication information].
4. In the Service environment component of the Authentication information window, check the Web service URL information.
5. 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 the parameters in the script
Check and correct the parameters in the script.

• ClientID → ncpClientID

Troubleshoot 429 error when searching for an address in Dynamic Map

A 429 (too many requests) error occurs when searching an address in 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 VPC environment of the NAVER Cloud Platform console, navigate to Menu > All Services > Application Services > Maps.
2. Click the Application menu.
3. Confirm the name of the Maps app, then click [Edit].
4. Select the checkbox for Geocoding.
5. Click [Save].

Troubleshoot 500 error when calling Dynamic Map on Android 9 or later

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

Cause

This issue is unrelated to the Maps API. It occurs because HTTP plaintext communication is blocked in Android 9 or later.

Solution

• Rather than using file://, host the HTML with the map interface on a web server with TLS enabled (https).
• Use Network security configuration in the app to 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 different marker locations between coordinate and address searches

Marker locations differ between coordinate searches and address searches.

Cause and solution

When searching using coordinates, the exact location value on the map 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 the Reverse Geocoding feature (converting coordinates into addresses).

Cause

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

Solution

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

Troubleshoot Korean domain authentication error

Korean domains are not authenticated in the Dynamic Map service.

Cause

As each browser handles Korean domains differently, authentication errors may occur.

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 VPC environment of the NAVER Cloud Platform console, navigate to Menu > All Services > Application Services > Maps > Application.
3. Take the value converted by the Punycode converter and register it in the Web service URL of the Maps app.

Troubleshoot CORS error

A CORS error occurs when calling the Maps APIs.

Cause

If the Maps API 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, set up a separate backend server on the same domain and call 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
• NAVER Map's Github: NAVER Map's Enterprise API