HotCodePush

Support

Where to ask a HotCodePush question, Discord or email, what to check before you write and what to include in a request so the first reply can answer it.

A question goes to the HotCodePush Discord, where the team and other users answer. Anything about your account, billing or an incident goes to support@hotcodepush.com, and a request that carries the ids and the two JSON outputs below is usually answered in the first reply.

Before you write

  • Troubleshooting covers the common reasons a device did not update, with the tool that shows each one.
  • The FAQ answers the short questions about frameworks, store rules, pricing and migration.
  • The status page shows whether an incident is open.

What to include

  • The organization id and the app id. The organization id is under Support on the organization's settings page, the app id on the app's overview page. hotcodepush organization get and hotcodepush app get print them too.
  • The device id for a question about one device, from the debug screen or the device's page in the console.
  • The output of hotcodepush doctor --json, run in the project.
  • The output of hotcodepush device probe --device <id> --json for a device that did not update.
  • The SDK and its version, and the platform, iOS or Android.
  • What you expected, what happened and when, in UTC.

Never paste an API token, a private signing key or a user's personal data into a request.

Service levels

Pay-as-you-go and Enterprise carry a 99.9 percent uptime commitment with credits, on update delivery and on the API. Free has the same target without a commitment.

The commitment and the credit table are on the enterprise page. A credit claim goes to support@hotcodepush.com within 30 days of the month's end.

Last updated on

On this page