Step 4's dashboard navigation is outdated. Credentials live under Apps → [App], not "project settings"

Open Beginner friendly
#11 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
84/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Domain
documentation

Research direction

Open the codelab at https://revenuecat.github.io/codelabs/google-play.html#2 and locate Step 4, “Register the Credentials JSON in RevenueCat.” Update the navigation text and any Step 4 screenshots to use Dashboard → Apps → [app name] → Service account credentials. The change is done when new users can find the JSON upload area using the instructions.

Written by the indexing model from the issue text.

Description

Description:
Codelab: https://revenuecat.github.io/codelabs/google-play.html#2

What the codelab currently says (Step 4 — Register the Credentials JSON in RevenueCat)

"head over to your RevenueCat dashboard and open your project settings. Locate the JSON
credentials file you saved earlier (from Step 2), and either drag and drop it into the setup
area or browse for it manually using the file picker."

What the dashboard actually shows

There's no generic "project settings" page with a credentials drop zone. The current path is:

Dashboard → Apps → [your specific app, e.g. "xxxx (Play Store)"] → Service account credentials

That per-app page is where the JSON upload area actually lives.

Suggested fix

Update Step 4's text/screenshots to point to Apps → [app name] → Service account credentials
instead of a generic "project settings" area, so new users aren't stuck searching for a page
that doesn't exist in that location anymore.

Dominant language
Go
Stars
15
Forks
3
PR merge metrics
No merged PRs in 30d

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.

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.