Inspector troubleshooting

​

Download is unavailable

The install page validates the Nightly release manifest. It deliberately hides installers when the manifest cannot be fetched, contains an invalid version, has missing or extra artifacts, or includes an invalid SHA-256 value. Retry later or contact support; do not construct a download URL manually.

​

Installer verification fails

Download the artifact and its SHA256SUMS sidecar again, then compare the digest using the command on Install. A mismatch means the file is incomplete or altered; delete it and do not launch it.

​

An automatic macOS update does not finish

A failed update check does not interrupt your Inspector session. Finish any work in progress, then quit and reopen Inspector to allow another check. If an update download or relaunch still does not finish, use the manual recovery path:

1. Download the latest Nightly DMG from Install.
2. Verify the DMG against its SHA256SUMS sidecar.
3. Quit Inspector, open the DMG, and replace Polymorfa Inspector in Applications.
4. Open Inspector again.

Do not construct a download URL manually. If the install page is unavailable, retry later or contact support.

​

Device authorization does not complete

Inspector uses the browser device flow. Confirm that:

• You are signed in at polymorfa.com/console.
• The device page shows the same user code as Inspector.
• You selected at least one team where you still have an active membership.
• The requesting app, location details, request time, teams, and active projects match what you expect.
• You explicitly approve the request before the code expires.
• Your browser allows credentialed requests to api.polymorfa.com.

Expired and completed codes cannot be reused; request a new code in Inspector.

​

Session connection fails

• If Inspector shows Something went wrong, select Retry. Retry keeps the retained native device and reconnects the same session; it does not open WhatsApp’s pairing screen or create another device.
• Confirm the number still belongs to the active project and your Polymorfa account owns it through Inspector.
• Check that api.polymorfa.com, polymorfa.com, and the sandbox endpoint shown by the app are reachable over HTTPS/WSS.
• Use the Console’s Sandbox view to confirm the session and owner before reinstalling.

If a testing number repeatedly returns to Connecting after its first open, retry once. If the cycle continues, contact support with the Inspector version and the failing step. Keep the number and its retained device while diagnosing the failure; removing the number permanently clears its simulated state.

​

A sent message is missing from Inspector

Select the sending number and open the recipient’s chat. If the recipient received the message but it is absent from the sending number’s chat, contact support with your Inspector version and the message ID returned by the send. Do not send it again solely to refresh the chat: the recipient already received it. Keep the number and its retained device while support investigates.

​

Group messages fail to appear

If your message appears in your group chat but another participant sees a decryption placeholder, keep the group and its linked devices while diagnosing the failure. Contact support with your Inspector version, the message ID and which participant view failed. Do not remove and recreate the group or resend messages solely to refresh the other view.

​

Retained history is unavailable

A production session can remain live when retained history is temporarily unavailable. Continue with live messages or retry the session later. If the session says retained history is off, enable Hosted Message Storage for that number before expecting earlier chats, contacts, or messages. Testing numbers do not have retained production history.

​

Inspect session logs

Open View → Toggle DevTools (Active Session), then select Console. Inspector records session initialization stages and WhatsApp runtime messages in that console, including warnings and patch setup failures. The same command closes DevTools when you finish. Before sharing console output with support, remove message content, phone numbers, device codes, and credentials.

​

Get help

​

Diagnostic reporting preferences

If your installed release includes Share diagnostic error reports, review what the preference sends before enabling it. It is separate from permission to open a production number. Reports do not replace a support request or attach screenshots and console logs. If a preference change fails to save, check that Inspector can write its local settings and try again. Turning reporting off stops it for the running app even if saving fails; confirm that the preference is off after restarting Inspector.

​

Contact support

Email support@polymorfa.com with the Inspector version, operating system, the failing step, and redacted screenshots or logs. Never include team keys, project tokens, client tokens, QuickLink URLs, or device codes.

​

Where to go next