Feature guide iOSAndroid

Push diagnostics and logs

Check payload size, provider rules, and credential expiry before sending, then turn common provider errors into actionable guidance.

Capability overview

What does push diagnostics and logs do in TestDock?

Check payload size, provider rules, and credential expiry before sending, then turn common provider errors into actionable guidance.

TestDock is organized around persistent app profiles rather than artificial environment switching. A profile is scoped automatically to the platform running TestDock and holds that app's platform metadata, URL schemes, verified-link configuration, saved deep links, share fixtures, push-provider setups, notification payloads, and repeatable scenarios.

TestDock deep-link workspace with saved links and app-link verification
Save reusable navigation tests, open them through the operating system, and inspect universal-link or app-link association data.

In the workflow

Create an app profile

Record the app name, current-platform identifier, URL schemes, and verified-link settings that define the installed target.

TestDock keeps the app profile, resolved link or push input, protected provider setup, scenario state, and redacted outcome together on the device where the check runs.

Useful in practice

Where this capability earns its place.

Related manual

Privacy, safety, and troubleshooting

Understand TestDock's on-device boundary and diagnose deep-link, push, scenario, and profile-import problems without exposing secrets.

The guide covers understand the on-device model, protect provider credentials, troubleshoot deep links, troubleshoot push delivery, prepare a safe support report. It is the best next step when you want to move from the product overview into a repeatable setup.

Read the guide

Direct answers

Questions about push diagnostics and logs.

What does push diagnostics and logs do in TestDock?

Check payload size, provider rules, and credential expiry before sending, then turn common provider errors into actionable guidance.

Does TestDock switch the environment of the app under test?

No. An external app controls its own configuration. TestDock models the app identity and stores the links, push setups, payloads, and scenarios you can actually exercise from the device.

Does TestDock require an account or backend?

No. It has no TestDock account, synchronization service, analytics, advertising, or collaboration backend.

Next

See all TestDock capabilities.

Back to capabilities