Greenstand / Greenstand/treetracker-android
Bug: JitPack dependency resolution error for debug-db
- Dominant language
- Kotlin
- Stars
- 101
- Forks
- 116
- PR merge metrics
- No merged PRs in 30d
Description
## Bug: JitPack dependency resolution error for debug-db
**Description:**
The CI workflow is failing to build the project due to a dependency resolution error for the `debug-db` library. The build logs show a 401 Unauthorized error when trying to download the dependency from JitPack.
**Steps to reproduce:**
1. Trigger the `pull-request.yaml` workflow.
2. Observe the build logs.
**Expected behavior:**
The `debug-db` dependency should be resolved successfully.
**Actual behavior:**
The build fails with the following error:
```
Could not resolve com.amitshekhar.android:debug-db:1.0.6.
Required by:
project :app
Could not resolve com.amitshekhar.android:debug-db:1.0.6.
> Could not get resource 'https://jitpack.io/com/amitshekhar/android/debug-db/1.0.6/debug-db-1.0.6.pom'.
> Could not GET 'https://jitpack.io/com/amitshekhar/android/debug-db/1.0.6/debug-db-1.0.6.pom'. Received status code 401 from server: Unauthorized
```
**Solution:**
Updating the dependency to `com.github.amitshekhariitbhu.Android-Debug-Database:debug-db:v1.0.6` resolves the issue.
**Describe the bug**
A clear and concise description of what the bug is.
**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
**Expected behavior**
A clear and concise description of what you expected to happen.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Desktop (please complete the following information):**
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]
**Smartphone (please complete the following information):**
- Device: [e.g. Techno F?-)]
- OS: [e.g. Android Version: ]
- Browser [e.g. stock browser, safari]
- Version [e.g. 22]
**Additional context**
Add any other context about the problem here.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by inspecting the pull-request.yaml workflow and the project declaration for com.amitshekhar.android:debug-db:1.0.6. Reproduce the dependency-resolution failure, then update the declaration to the coordinate given in the issue and rerun the workflow; done means the dependency resolves without the 401 error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- build-system, ci-cd, mobile
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100