GuidesFlutter API ReferencesHERE SDK for Android API referencesHERE SDK for iOS API references
Guides

Community and support

We are here to help you. Find below comprehensive tips when encountering bugs, access assistance by joining our Slack community and benefit from other available support channels.

Getting help when bugs occur

If you experience a crash or unexpected behavior, please contact us and provide detailed information on how to reproduce the issue.

Note that when crashes occur in the native C++ stack of the HERE SDK, then in the crash logs you will see only the addresses where the crash occurred. These addresses need to be symbolicated in order to see the stack trace where the crash occurred.

Note

Since HERE SDK 4.15.3 we include debug symbols in the HERE SDK package. Beneath the Android Archive (AAR) ZIP and the documentation ZIP files you can find a ZIP folder with the debug symbols: inside, look for the .so files that are added for each device architecture.

In order to symbolicate crash logs on Android, you should have the NDK (Native Development Kit) stack tool and ADB (Android Debug Bridge) installed.

More information on symbolication and logs can be found here.

Make sure to use only the symbols that are shipped for the release you have integrated. Symbols from other releases will not work.

Provide meaningful bug reports

When you reach out to us, be sure to always include at least the HERE SDK version, platform, license and logs. Below you can find a bug report checklist that will help us to respond faster:

  • Type of the issue: For example, a crash or unexpected behavior.
    • In case of a crash, provide a crash log including stack trace.
    • In case of unexpected behavior, describe the expected versus the actual behavior.
  • Is the issue a regression and if yes, since when?
  • Description of the issue with detailed steps to reproduce it: Is the issue reproducible with one of our example apps, or can you provide code that isolates the issue?
  • What APIs are called (if applicable)? Try to list all parameters and options.
  • Reproducibility rate?
  • Provide information about the environment such as OS, IDE, device / simulator (OS, name).
  • Map data version / used catalog (if relevant).
  • List other frameworks or plugins that are used, including version information (if applicable).
  • Add screenshots or a video (if applicable).
  • In case of search or routing issues, provide the geographic coordinates where the issue occurred or a GPX trace.

Make sure to check our changelog where we list known issues. Please also make sure to follow the latest instructions and code examples listed in the related sections of this Developer Guide to avoid implementation issues.

Join our Slack community

If you need help with this or any other HERE product, join our Slack Workspace. Alternatively, try one of the below options:

  • If you have a HERE representative, contact them when you have questions/issues.
  • Log into your account and check the pages on the SLA report.
  • If you have purchased your plan/product from a HERE reseller, contact your reseller.
  • If you have questions about billing, your account, or anything else contact us.

Read our developer blogs

Our developer blog features engaging tutorials covering the HERE SDK product family and other related products.

A selection of tutorials can be found on our tutorials page.

How to sign up for HERE updates

To stay informed about HERE SDK updates, new features, and important announcements, you can sign up for email notifications through the HERE platform dashboard:

  1. Log in to the HERE platform.
  2. Open your account settings by clicking on the top-right icon with your initials, then select Account settings.
  3. Tick the box to confirm "I would like to receive relevant updates from HERE Technologies by email."

Note that you can also unsubscribe at any time.

Report documentation or example app issues on GitHub

If you encounter any issues with this documentation or the example apps provided with the HERE SDK, reporting them on GitHub is the most effective way to ensure they are addressed promptly.

Before reporting an issue, ensure that you can clearly identify the problem you're experiencing. This could be a discrepancy in the documentation, a bug in the example app, or any other issue you encounter while working with the SDK.

When creating a new issue, provide as much detail as possible about the problem you're encountering. Include steps to reproduce the issue, any error messages you're seeing, and the expected behavior. The above bug report checklist provides a guideline.