Keep push credentials and target tokens scoped to each app

Capability overview

What does per-app push setups do in TestDock?

Keep target-app push tokens, optional Expo access tokens, APNs .p8 signing bundles, and Firebase service-account JSON in operating-system secure storage for the app profile that uses them.

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.

In the workflow

Save reusable tests

Add deep links, share fixtures, push setups, notification templates, and manual scenarios to that app profile.

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

Test push delivery and repeatable app flows

Configure provider-specific push targets, reuse payload templates, and combine delivery checks with observable manual scenarios.

The guide covers create a push setup, build a reusable payload, validate, send, and inspect, turn behavior into a scenario. It is the best next step when you want to move from the product overview into a repeatable setup.

Direct answers

Questions about per-app push setups.