Bug in UHRS Mobile App Scenario (HIT App ID: 64440) – Trapped in feedback error loop

There is no publicly documented user-controlled lease-release procedure for UHRS HitApp 64440, so reset the app’s local state once and, if the assignment immediately returns, ask the UHRS access vendor to investigate or escalate the active session.

Reset the local state

The screenshot appears to show Android despite the iOS tag. Force-stopping did not help because it closes the process but does not erase persistent app data.

For Android:

1. Open Settings → Apps → UHRS → Storage.
2. Select Clear cache.
3. Select Clear storage or Clear data.
   • This signs you out and removes locally stored UHRS app state.
4. Open UHRS, sign in again, and check whether HitApp 64440 still opens into the same error.
5. If the relevant account/vendor permits web access, test the HitApp once through the normal UHRS web entry or another device.

Clearing storage is a diagnostic reset, not a documented UHRS lease-release method. The public HitApp entry confirms ID 64440, but no reliable public documentation describes this exact getNewHits failure or a worker-accessible session-reset command.^1^

If this is actually iOS:

1. Open Settings → General → iPhone Storage → UHRS.
2. Choose Delete App, not Offload App. Offloading can retain app data.
3. Reinstall UHRS from the App Store and sign in again.

Deleting or clearing app data removes local settings, so ensure the sign-in method is available first.

If the broken assignment returns

If the same HitApp and error return after a clean local reset or on another device, that suggests—but does not prove—that UHRS is restoring the assignment or session from its service rather than reading only local state. Do not repeatedly submit, skip, or judge while the payload is failing.

Open a ticket with the marketplace/vendor through which the UHRS account is managed, because the in-app feedback path is also broken. Ask the vendor to:

• Investigate the active assignment/session for HitApp 64440.
• Escalate the malformed getNewHits response to the HitApp owner or UHRS operations.
• Release or expire the assignment if that operation is available.
• Confirm whether the HitApp has been disabled or has a known incident.

Include:

• HitApp: Mobile App Scenario (English)
• HitApp ID: 64440
• Exact errors: SyntaxError: "undefined" is not valid JSON and the getNewHits parsing failure
• Timestamp and time-zone offset shown in the dialog
• UHRS app version, phone model, and Android/iOS version
• The screenshot
• Confirmation that force-stop and a full local-state reset were attempted
• Whether the same state appeared on another device or web session

The syntax error means the client attempted to parse an undefined value as JSON; it identifies a parsing failure but does not, by itself, establish whether the missing value originated in the HitApp response, session state, or client storage.^2^

Because this concerns a specific third-party-managed UHRS assignment rather than an Edge browser crash, changing Edge settings or using Windows Feedback Hub is unlikely to release the session.

References

1. Universal Human Relevance System - UHRS
2. javascript - "undefined" is not valid JSON - Stack Overflow