PostHog / PostHog/posthog-android

Native C/C++ (NDK) crash capture, manual and automatic

Open
#638 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feat/error-tracking
Dominant language
Kotlin
Stars
90
Forks
49
Avg merge
2d 5h
Merged PRs (30d)
61

Description

Extracted from PostHog/posthog#43012.

Problem

There's no native code in the SDK: no signal handlers, JNI, or .so symbol handling. Capture is limited to JVM Throwables (manual plus the uncaught handler).

Scope

  • Native signal-handler capture (SIGSEGV, SIGABRT, and friends), a manual native capture API, symbol upload, and the server-side symbolication path.

Large, probably an epic rather than a single PR.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by mapping the existing JVM Throwable, manual-capture, and uncaught-handler flow, then break the native signal capture, manual API, symbol upload, and server-side symbolication scope into separately actionable work; done requires those areas to be specified and implemented.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, c, cpp
Domain
backend-api-design, mobile-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.