Carpuride W702P - Error: read property ‘type’ of undefined

Hi Kurviger Team,

I am contacting you because I am experiencing an unrecoverable crash in the Kurviger application when attempting to download maps for offline use directly on a standalone Android motorcycle screen (Carpuride W702 Plus, running native Android 12, with 4GB RAM and 64GB internal storage).

Every time I try to initiate a map or region download within the app, a continuous red error popup appears on screen:

Message: Uncaught TypeError: Cannot read property ‘type’ of undefined - URL: undefined - Line: 2 - Column: undefined - Error object: {}

I have performed the following troubleshooting steps without success:

  1. Verified a stable Wi-Fi connection.

  2. Performed a complete app data wipe and cache clearance from system settings.

  3. Granted full storage management permissions (“Allow management of all files”).

  4. Checked that storage path selection fails due to system folder mapping limitations on this device.

  5. Attempted downloads using smaller regional map files.

The issue persists and appears to be a compatibility bug with the WebView / JavaScript libraries used by the app’s download manager interface on this firmware.

My goal is to use the app 100% standalone on the motorcycle screen without relying on a smartphone. Is there a technical workaround, patch, or previous APK build that resolves this variable reading error in the map manager?

I look forward to your guidance and have attached a screenshot of the error.

Best regards,

Jesús

Hello Jesús and welcome to the forum!

If you suspect a Webview problem - have you tried updating the webview?

Also, please go to the bottom of the settings menu, copy the debug info and post it here. That would give developers a better idea about your configuration.

We only have the a Carpuride Plus running Android 14. With Android 14 it worked for us to download offline maps. Could you check if an OS update is available for you?

We are pretty sure this is due to the old Webview used with Android 12. If you can update to 14 or update your Chrome version, that should fix the issue.