Question 1

Why are duplicate custom chart buttons appearing in Aptabase and how do I remove them?

Accepted Answer

This bug was caused by deleting custom charts in a specific order (e.g., deleting the top one, then the bottom one). A fix has been implemented in [PR #150](https://github.com/aptabase/aptabase/pull/150). To resolve, update your Aptabase instance to a version that includes this fix. If you are unable to update immediately, avoid deleting charts in that sequence as a temporary workaround.

Question 2

Why do I get 'redirect_uri is not associated with this application' when trying to log in with Google or GitHub?

Accepted Answer

This was a known misconfiguration issue with the OAuth redirect URIs. The error has been fixed. If you still encounter it, try clearing your browser cache or using a private window. If the issue persists, report it on the GitHub repository.

Question 3

Why does Aptabase fail with 'exec /usr/bin/dotnet: exec format error' on ARM64?

Accepted Answer

Official Aptabase Docker images are only built for linux/amd64. To run on ARM64 (aarch64) machines, use the unofficial community image:
```bash
docker pull jcpsantiago/aptabase-arm:latest
```
Then update your `docker-compose.yml` to use `image: jcpsantiago/aptabase-arm:latest`. Note: This is an unofficial build and not maintained by the Aptabase team.

Question 4

Why does the 'All time' filter in Aptabase start from January 1, 1970?

Accepted Answer

This bug caused the time range to default to the Unix epoch instead of the app's actual creation date. Fixed in [PR #120](https://github.com/aptabase/aptabase/pull/120). Update to the latest version to resolve the issue.

Question 5

Why does my analytics tool show statistical aggregates instead of value breakdowns for boolean or numeric event properties?

Accepted Answer

When an event property is sent as a numeric or boolean type, some analytics tools (e.g., PostHog, Highlight) automatically treat it as a metric and display statistical aggregations (sum, avg, min, max) instead of a simple count per value. To get a per‑value count breakdown (e.g., how many events have `isCorrect: true` vs `false`), convert the property to a string on your side before sending the event:

```javascript
// Instead of
capture('presentQuestionAnswered', { isCorrect: true });
// Use string values
capture('presentQuestionAnswered', { isCorrect: 'true' });
```

Alternatively, check if your dashboard offers a 'count' view or 'property value' filter that ignores numeric treatment. This behavior is a known UX confusion—the interface shows the total count per value in a small tooltip (e.g., "59.1K events with true"), but the main chart defaults to aggregation.

Aptabase

Core Features

What It Can't Do

Use Cases

Tags

Getting Started

Similar Projects