Main focus

Send in-app debug information when support asks for technical details about a crash, sync problem, import failure, missing data, or device-specific behavior.

Applies to

  • Android
  • iOS

Use this when support asks for diagnostics

Most questions only need a screenshot and a short description. Send the debug package when support needs device, account, app, inventory, log, or backup details to reproduce the issue.

What to collect before sending

  • What you were trying to do and the result you expected.
  • The exact screen, inventory, product, entry, import file, or user affected, when it is safe to share.
  • Screenshots or a short screen recording that show the problem.
  • Approximate date and time when the problem happened.
  • The in-app debug information package generated from the steps below.

Android steps

  1. Open Mobile Inventory to the first inventory list screen.
  2. Long-press the help icon (?) in the top bar.
  3. On the Debug screen, tap Send info to the support team.
  4. Choose the email or share app that opens.
  5. Keep the generated text and attached files in the message, then add your short problem description and screenshots.

Android screens

Start from the inventory list and long-press the help icon.
The Debug screen shows the information categories and prepares the support package.
Choose the email or share app and keep the generated files attached.

iOS steps

  1. Open Mobile Inventory to the first inventory list screen.
  2. Long-press the help icon (?) in the top bar.
  3. If the debug information action appears, use it and keep the generated details attached.
  4. If your iOS version does not show that action, send the manual details listed above: app version, iOS version, device model, affected inventory, screenshots, and issue time.

What the debug package contains

  • Account identifiers such as authenticated user ID, name, and email.
  • Device identifiers and device model information.
  • Mobile Inventory app version and selected app settings.
  • Inventory names and IDs, including shared-inventory sync timestamps where available.
  • Local backup or database files, encrypted request logs, and encrypted app preferences used for troubleshooting.
  • Storage, memory, network, locale, time zone, system time, battery-saver state, and theme information.

Do not add passwords, payment details, customer secrets, or unrelated business documents. Check screenshots and screen recordings before sending because those files may show product names, quantities, customer names, or internal notes.

Web availability

No Web diagnostics export found

Verified in the Web frontend and API source on May 5, 2026: the signed-in Web app has a support page and internal super-admin log views, but no user-facing debug or diagnostics export. For Web-only issues, collect the page URL, browser and version, account email, inventory name, issue time, screenshots, and exact steps.

Before sending

Quick review

  • Keep the generated debug files attached if the app created them.
  • Add the short problem description and reproduction steps in the message.
  • Confirm the affected inventory, product, entry, or import file name is mentioned when relevant.
  • Remove unrelated screenshots or attachments that are not needed for the issue.

After sending, keep the app installed and avoid clearing app data until support confirms whether the backup or logs were readable.