Downloads Ignite Global Support Home Start a conversation Sign in
Start a conversation
  1. StreetSmart
  2. StreetSmart Articles
  3. Articles

StreetSmart Mobile App Activation Fails with “Invalid PIN!” on Android

Contents

Overview

You may see the activation error “Invalid PIN!” in the StreetSmart mobile app even when the PIN being entered is correct. This commonly occurs when the mobile worker’s assigned Security Role does not include the Mobile Device login permission (Mobile Device → Login/Allow Login).

In affected cases, the device often appears in the StreetSmart portal under Administration → Devices but shows it has never activated (the Activated Datetime field is blank) and is not linked to any worker. This is expected behavior when Mobile Device login is not permitted for the worker’s role, and it is not an app defect.

Solution

Symptoms

  • Error message during activation: “Invalid PIN!”
  • In the web portal under Administration → Devices, the device record exists but shows Activated Datetime as blank / Not Activated.
  • The device is not linked/assigned to the intended worker.

Cause

If the worker’s assigned Security Role does not allow Mobile Device login (Mobile Device → Login/Allow Login), StreetSmart can reject authentication during activation and surface the failure as “Invalid PIN!”, even when the digits entered match.

Diagnosis checklist

  1. In Administration → Users, open the affected worker and note the assigned Security Role (often a custom role such as <custom_security_role>).
  2. In Administration → Devices, open the device entry for <phone_number_or_device_description> and confirm whether it shows Not Activated / blank Activated Datetime and no worker linkage.

Fix: enable Mobile Device login in the Security Role

  1. Go to Administration → Roles.
  2. Edit the worker’s assigned Security Role (for example, <custom_security_role>).
  3. Under Mobile Device, enable:
    • Login / Allow Login

  4. Also enable any additional Mobile Device permissions needed for your use of StreetSmart (for example, access to Jobs/Forms/Timesheets as applicable).

  5. Save the role changes.

If you cannot edit roles/users: a user with Company Administrator / Super User privileges (or an equivalent custom admin role) must perform the role update.

Re-run activation after fixing the role

  1. In the web portal, go to Administration → Devices.
  2. Deactivate the device and ensure Prompt the worker to enter PIN is enabled/checked during deactivation.
  3. On the Android device, launch StreetSmart and activate normally:
    • Enter the phone number as required by your activation flow (for example, <phone_number>).
    • Enter the worker PIN.

If “Invalid PIN!” still appears: Clear Activation

  1. On the phone, open the StreetSmart app.
  2. Go to Settings → Advanced Options → Clear Activation.
  3. When prompted, use the default Clear Activation code: 4321.
  4. After clearing, repeat the standard activation (phone number → PIN).

How to Verify the Fix

  1. The app activation completes without “Invalid PIN!”.
  2. In Administration → Devices, the device shows an Activated timestamp/date.
  3. The device shows as linked/assigned to the intended worker.

Frequently Asked Questions

1. How do I know this is the same issue?

You see “Invalid PIN!” during mobile activation even though the PIN matches what is shown in Administration → Users, and the device in Administration → Devices shows it has never activated (blank Activated Datetime / Not Activated) and is not linked to a worker.

2. Why would StreetSmart say “Invalid PIN!” if the digits are correct?

The message can occur when the worker is not eligible for Mobile Device login due to Security Role permissions. If the role does not have Mobile Device → Login/Allow Login, authentication can be rejected and surfaced as “Invalid PIN!”.

3. What should I change in the Security Role?

In Administration → Roles, edit the worker’s assigned role and enable Mobile Device → Login/Allow Login. Add any other Mobile Device permissions required for your organization’s workflow.

4. I don’t have permission to edit users/roles—what now?

Have a Company Administrator / Super User (or equivalent admin role in your organization) update the worker’s Security Role to allow Mobile Device login, then retry activation.

5. What if the error persists after updating the role?

Perform Clear Activation in the app (Settings → Advanced Options, default code 4321), then run activation again. If it still fails, collect the exact steps and screenshots of the error and contact support with the affected <phone_number> and worker username for further verification.

Choose files or drag and drop files
ai_initiated
atlas_studio
kb_automation
Was this article helpful?
Yes
No

  1. Priyanka Bhotika

  2. Posted

Comments