TickFlowTickFlowSDK
PricingFAQ
Sign In
Talk to us
Skip to content
  • Overview
  • How it works
  • Privacy & security
  • Developers
  • Pricing

TickFlow SDK · in-app bug reporting for mobile apps

Shake to report.Bugs arrive ready to fix.

TickFlow SDK turns every tester and beta user of your mobile apps into a precise bug reporter. One shake sends a screenshot, the recent logs, errors and network calls, redacted on the phone, as a ticket your developers can reproduce.

Talk to usSee how it works
To report
1 shake
Sent unasked
0 bytes
Plans from
$200/mo

TickFlow Web included. React Native & Expo available; native Android and iOS in early access.

14:32
‹ CartCheckout
  • Trail runnerSize 9 · Blue$129.00
  • Running socks3 pack$18.00
Saved card ···· 4242
Total$147.00
Payment failed. Please try again.
Pay $147.00
Report a problemSends a ticket to the team behind this app
ScreenshotInclude screenshot
Title *
What went wrong?Checkout fails after Pay
Attach diagnostics (logs.zip)212 log lines · 1 error · 34 network calls · iPhone 16, iOS 19.1
[LOG] POST /checkout Authorization: Bearer [redacted][WARN] Payment request failed, status 502[ERROR] TypeError: Cannot read property 'id' of undefined
Send report
Thanks, your report was sentQuote this reference if you follow up:TF-8F42-QKDone
TickFlow WebClient account · Acme
capturedLOGNavigated to CheckoutLOGGET https://api.shop.example/cart?session=8f2a91c4e7d0[redacted]LOGReceipt e-mail set to dana.k@example.com[email]LOGPOST /checkout Authorization: Bearer 0f9e8d7c6b5a4f3e[redacted]WARNPayment request failed, status 502ERRORTypeError: Cannot read property 'id' of undefinedredacted as it is captured · nothing leaves the phone yet
shakeReport card opens on Checkoutscreenshot taken before the card appears
review212 log lines · 1 error · 34 network calls · iPhone 16, iOS 19.1the reporter sees this first · screenshot ✓ · diagnostics ✓
sentTF-8F42-QK · screenshot + diagnostics zipthe reporter gets the reference to quote
ticketCheckout fails after Payscreenshotlogserrorsnetworkdevice
ClickUpTask created for your teamtwo-way sync with the ticket
  • “It just crashed”
  • Screen recordings from a camera roll
  • “Which version are you on?”
  • E-mail threads
  • “Can you send a screenshot?”
  • “What were you doing?”
  • “It just crashed”
  • Screen recordings from a camera roll
  • “Which version are you on?”
  • E-mail threads
  • “Can you send a screenshot?”
  • “What were you doing?”

From shake to fix, in one report

What happens when a tester shakes the phone.

One report from a beta build of an illustrative shop app whose checkout fails. Scroll through it.

  1. 01 Shake

    The tester shakes the phone. That is the whole bug report form.

    From the screen that went wrong, one shake opens a report card. If shaking does not suit your testers, a Report a problem item in your own menu opens the same card. No e-mail thread, no screen recording to dig out of a camera roll.

    Payment failed.
    • Screenshot · Checkout
    • Console · the last lines
    • JS errors · with stacks
    • Network · method, address, status, timing
    • Breadcrumbs & context
    • Device · OS · app version

    1 shake · or a Report a problem item in your menu

  2. 02 Redact

    Secrets become [redacted] the moment they are logged.

    Redaction runs on the phone as each value is captured, so a token or an e-mail address never sits in what the SDK keeps. Your own rules run on top, for anything that is sensitive in your app. Nothing leaves the phone until someone sends a report.

    console · captured on the phone3 secrets → tokens
    14:31:52 [LOG] Navigated to Checkout
    14:31:53 [LOG] GET https://api.shop.example/cart?session=8f2a91c4e7d0[redacted]
    14:31:58 [LOG] Receipt e-mail set to dana.k@example.com[email]
    14:32:01 [LOG] POST /checkout  Authorization: Bearer 0f9e8d7c6b5a4f3e[redacted]
    14:32:02 [WARN] Payment request failed, status 502
    14:32:02 [ERROR] TypeError: Cannot read property 'id' of undefined
    
    redacted as it is capturedkept on the phoneleaves only when someone sends a report
  3. 03 Review

    Nothing is collected invisibly. The reporter sees it first.

    The card shows the screenshot, a one-line summary of the diagnostics and, on request, the last log lines. The reporter adds a title and a few words, and can leave the screenshot or the diagnostics out.

    14:32
    ‹ CartCheckout
    • Trail runnerSize 9 · Blue$129.00
    • Running socks3 pack$18.00
    Saved card ···· 4242
    Total$147.00
    Payment failed. Please try again.
    Pay $147.00
    Report a problemSends a ticket to the team behind this app
    ScreenshotInclude screenshot
    Title *
    What went wrong?Checkout fails after Pay
    Attach diagnostics (logs.zip)212 log lines · 1 error · 34 network calls · iPhone 16, iOS 19.1
    [LOG] POST /checkout Authorization: Bearer [redacted][WARN] Payment request failed, status 502[ERROR] TypeError: Cannot read property 'id' of undefined
    Send report
    Thanks, your report was sentQuote this reference if you follow up:TF-8F42-QKDone
    • See it first. A one-line summary of the diagnostics, and the last log lines on request.
    • Leave it out. The screenshot and the diagnostics each have their own switch.
  4. 04 Ticket

    A TickFlow Web ticket, with the evidence attached.

    The report becomes a ticket for the right client account: the screenshot, a diagnostics zip and a short summary in the description, so support can read the essentials without opening anything. The tester gets TF-8F42-QK to quote.

    TickFlow WebClient account · Acme
    TF-8F42-QKnewfrom the app · Checkout

    Checkout fails after Pay

    Tapped Pay with a saved card. Spinner, then “Payment failed”.

    screenshot-….pngCheckout, as the tester saw ittickflow-diagnostics-….ziplogs · errors · network · device
    --- Diagnostics ---
    App: Acme Shop (com.acme.shop)
    Version: 2.4.0 (118)
    Device: iPhone 16, iOS 19.1
    Screen: Checkout
    Last JS error: TypeError: Cannot read property 'id' of undefined
    SDK: react-native/0.1.1
    Full logs: see the attached tickflow-diagnostics zip.
  5. 05 ClickUp

    And a ClickUp task your developers can reproduce.

    Your team works the report in ClickUp, where it already works. The screen name, the last taps and the last failing request come with the report, so the first question is not “what were you doing?”.

    TickFlow WebClickUp
    Acme Shop · QA

    Checkout fails after Pay

    To doTF-8F42-QK2 attachments
    • Task created from the ticket, with the evidence
    • Your developer works it in ClickUp
    • Public replies and status changes sync back to the ticket

    The tester quotes TF-8F42-QK. Nobody asks “what were you doing?”.

Open the report

Flip the switches the tester has. See what your developer gets.

The report card has two switches, one for the screenshot and one for the diagnostics. Try them, then open the files in the zip. The report is illustrative and already redacted, as it would be on the phone.

On the phone · the report card

Report a problemSends a ticket to the team behind this app

The title and description, with a short summary of the app, device and screen, plus the screenshot and the diagnostics zip.

In the ticket · what your developer opens

  • screenshot-….pngattached
  • tickflow-diagnostics-….zip7 files
2026-11-10T14:31:52.000Z [LOG] Navigated to Checkout
2026-11-10T14:31:53.000Z [LOG] GET https://api.shop.example/cart?session=[redacted]
2026-11-10T14:31:58.000Z [LOG] Receipt e-mail set to [email]
2026-11-10T14:32:01.000Z [LOG] POST /checkout  Authorization: Bearer [redacted]
2026-11-10T14:32:02.000Z [WARN] Payment request failed, status 502
2026-11-10T14:32:02.000Z [ERROR] TypeError: Cannot read property 'id' of undefined

Secrets and e-mail addresses were replaced on the phone, when each line was logged.

Built for testing and QA

Fewer “can’t reproduce” tickets. More fixes.

01Shake, or tap Report a problem
Testers and beta users report from the screen that went wrong. No e-mail thread, no screen recording to dig out of a camera roll.
02The evidence comes with it
Recent console logs, JavaScript errors with their stacks, network calls, your breadcrumbs and the device, OS and app version.
03Redacted on the device
Secrets and e-mail addresses are scrubbed on the phone, before anything is stored or sent. Add your own rules for anything else.
04A ticket, not a message
Each report becomes a TickFlow Web ticket for the right client account, and a ClickUp task for your team, with a reference the tester can quote.
05Faster repro for developers
The screen name, the last taps and the last failing request are in the ticket, so the first question is not “what were you doing?”.
06Only in the builds you choose
One switch keeps it to internal, QA or beta builds. Switched off, it does nothing at all.

Platforms

React Native today. Native Android and iOS in early access.

  • TypeScriptAvailable

    React Native & Expo

    Shake-to-report for React Native and Expo apps (Expo SDK 54 or later). Reports become TickFlow Web tickets. Your TickFlow contact sends the package and a setup guide.

  • KotlinEarly access

    Android

    A native SDK built for TickFlow Field: app logs, errors, breadcrumbs and context, redacted on the device. Ask us if you want it for app testing.

  • SwiftEarly access

    iOS

    A Swift package with a shake-to-report sheet, built for TickFlow Field and redacted on the device. Ask us if you want it for app testing.

Running payment terminals or field devices rather than consumer apps? The same SDKs feed TickFlow Field, with card data redacted on the device.

Setup

Three steps, one of them in TickFlow.

  1. 01

    Allow the app

    In TickFlow, an admin opens Collect Feedback for the client account, adds the app’s bundle id or package name and creates an embed key.

  2. 02

    Add it to the app

    Your developer installs the package and adds a few lines around the app. Your TickFlow contact sends the setup guide.

  3. 03

    Shake to report

    Testers shake the phone, check what will be sent, add a few words and send. The ticket arrives with the evidence attached.

Pricing

From $200/month

Available on plans (TickFlow Web included). Already on one? Your TickFlow contact sends the package and the setup guide.

See SDK pricingFor developers

Detailed technical briefing available on request

The how behind this page — how the SDK hooks into your app, the integration guide with code, and the redaction rules — is in our technical briefing for customers, security teams and assessors. Ask us for access, then sign in.

Sign in to the briefing →

Questions

What teams ask us first.

Which apps does TickFlow SDK work with?

React Native and Expo apps (Expo SDK 54 or later), available now. Native Android (Kotlin) and iOS (Swift) versions are in early access: they were built for TickFlow Field, so ask us if you want them for app testing.

What does a report contain?

A screenshot of the screen the person was on, plus recent console logs, JavaScript errors with their stacks, network calls (method, address, status and timing, never their contents), your breadcrumbs and context, and the device, OS and app version. The reporter can leave the screenshot or the diagnostics out.

How is sensitive data handled?

Secrets and e-mail addresses are removed on the device, before anything is stored or sent, and you can add your own rules. Nothing is collected invisibly: the reporter sees a summary of what will be sent and can leave the screenshot or the diagnostics out.

Can we keep it out of the App Store build?

Yes. One switch keeps it to the builds you choose, such as internal, QA or beta builds. Switched off, it does nothing at all.

What if shaking does not suit our testers?

Open the report form from a menu item instead, such as a Report a problem entry in your settings screen, and turn shake detection off if you like.

Where do the reports go?

Each report becomes a TickFlow Web ticket for the right client account, with the screenshot and the diagnostics attached, and a ClickUp task for your team. The tester gets a reference they can quote.

What does it cost?

TickFlow SDK is available on plans (TickFlow Web included) from $200/month. Already on one? Your TickFlow contact sends the package and the setup guide. On a smaller plan, talk to us about moving up.

Give your testers a better way to report.

TickFlow SDK comes with TickFlow Web plans from $200/month. Talk to us, or upgrade your plan, and your testers can shake to report.

Talk to usSee SDK pricing

Or write to hello@tickflow.co

Shake to report.
TickFlow SDK

In-app bug reporting and testing for mobile apps. Reports land as TickFlow Web tickets, built by Orthoplex Solutions in Canada.

hello@tickflow.co

TickFlow SDK

  • Overview
  • How it works
  • Privacy & security
  • Developers
  • Pricing

TickFlow

  • TickFlow Web
  • TickFlow Field
  • All pricing
  • FAQ
  • Privacy policy
  • Terms of service

Get started

  • Talk to us
  • SDK pricing
  • Technical briefing
© 2026 Orthoplex Solutions. TickFlow and TickFlow SDK are products of Orthoplex Solutions.The app, device and report shown on these pages are illustrative.TickFlow is an independent product and is not affiliated with, endorsed by, or sponsored by ClickUp. ClickUp™ is a trademark of Mango Technologies, Inc.