Introduction
Build Error Code E012—“Custom Git repo is misconfigured. Please check the Repository URL and Access Token settings at buddyboss.com. Also, check package.json file in the Git repo.”—occurs when BuddyBoss App cannot fetch or merge your custom code because the Git settings or repository contents are invalid.
The build system tried to pull code from your specified Git repository and failed due to an incorrect repository URL, invalid access token, or missing/invalid package.json at the repo root.
Secure Dev Access
You need to have access to Developer Access to configure the Git repository for your BuddyBoss App.
Connect Your Git Repository
- In your BuddyBoss.com account, go to Apps and click Manage on the relevant app.
- Under Custom Development, set Provider to GitHub or GitLab.
- Enter the SSH Repository URL:
- GitHub: [email protected]:your-org/your-repo.git
- GitLab: [email protected]:your-org/your-repo.git
- Create a Personal Access Token with the scopes below and paste it into the Access Token field:
- GitHub: repo
- GitLab: read_api, read_repository
- Click Save to connect the repository.
Set Up Your Git Repository
- Initialize or clone your repository on GitHub or GitLab.
Ensure a valid package.json exists at the repo root, containing at minimum:
json
Copy
{
“name”: “your-app-name”,
“version”: “1.0.0”,
“main”: “index.js”
}
- Copy or merge the BuddyBoss custom code template into your repo (see the BuddyBoss GitHub starter template).
- Add your React Native code to index.js (importing any other modules as needed).
- Commit and push your changes to the branch you configured for custom development.
Trigger a New Build
- In WordPress, go to BuddyBoss App > Build.
- Select your custom branch under Step 1: Choose Source.
- Click Send Build Request to pull the updated repo and build your app.
Do I Need to Generate a New Build?
Yes. After connecting or updating your Git repo, you must trigger a new build so BuddyBoss can fetch the code and include it in your next release.
Troubleshooting and FAQs
Q: My build still fails with “package.json” not found.
A: Ensure package.json resides at the root of the default branch or the branch you selected, and that it’s valid JSON.
Q: Which branch should I point to?
A: Use a dedicated branch (e.g., custom-code) that holds your customizations to avoid merging unstable code.