Skip to content

Conversation

@ovitrif
Copy link
Collaborator

@ovitrif ovitrif commented Aug 11, 2025

Related:

Description

This PR updates the build config to consume the bitkit-core dependency from GitHub packages instead of Jitpack.

Important Check the updated bindings README, you will need to Setup your GitHub credentials in order to be able to build locally using the dependency from the GitHub packages maven repository.

Preview

n/a

QA Notes

Test that building succeeds and the new app runs without errors (existing wallet).

@ovitrif ovitrif force-pushed the chore/core-gh-package branch from 6436aa0 to 532a579 Compare August 14, 2025 14:59
@ovitrif ovitrif marked this pull request as ready for review August 14, 2025 15:00
@ovitrif ovitrif requested a review from jvsena42 August 14, 2025 15:00
@ovitrif ovitrif enabled auto-merge August 14, 2025 16:24
@ovitrif ovitrif requested review from jvsena42 and removed request for jvsena42 August 14, 2025 16:58
@ovitrif
Copy link
Collaborator Author

ovitrif commented Aug 14, 2025

Fixed the issue with missing credentials in the GH workflows via 059ed83

jvsena42

This comment was marked as resolved.

@ovitrif
Copy link
Collaborator Author

ovitrif commented Aug 14, 2025

Could not GET 'https://maven.pkg.github.com/synonymdev/bitkit-core/com/synonym/bitkit-core-android/0.1.10/bitkit-core-android-0.1.10.pom'. Received status code 401 from server: Unauthorized

My bad, fixed the wrong README instructions in e7aa04f 🙏🏻

jvsena42
jvsena42 previously approved these changes Aug 15, 2025
Copy link
Member

@jvsena42 jvsena42 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested

  • Set credentials in local.properties
  • Sync and build the app

@ovitrif
Copy link
Collaborator Author

ovitrif commented Aug 15, 2025

Nice enhancement to also support local.properties!

Was thinking though...
Can you pls use the same name for the keys?

It's a bit confusing now, with different prop keys in local.properties vs gradle.properties.

That would also align with the readme, both in this repo and the repos of the dependencies.

@jvsena42
Copy link
Member

jvsena42 commented Aug 15, 2025

Nice enhancement to also support local.properties!

Was thinking though... Can you pls use the same name for the keys?

It's a bit confusing now, with different prop keys in local.properties vs gradle.properties.

That would also align with the readme, both in this repo and the repos of the dependencies.

Do you mean like this?

username = System.getenv("GITHUB_USER") ?: providers.gradleProperty("gpr.user").orNull
password = System.getenv("GITHUB_KEY") ?: providers.gradleProperty("gpr.key").orNull

@ovitrif
Copy link
Collaborator Author

ovitrif commented Aug 15, 2025

Nice enhancement to also support local.properties!

Was thinking though... Can you pls use the same name for the keys?

It's a bit confusing now, with different prop keys in local.properties vs gradle.properties.

That would also align with the readme, both in this repo and the repos of the dependencies.

Do you mean like this?

username = System.getenv("GITHUB_USER") ?: providers.gradleProperty("gpr.user").orNull
password = System.getenv("GITHUB_KEY") ?: providers.gradleProperty("gpr.key").orNull

No, I mean in local.properties, should also use if possible the same key names:

  • gpr.user
  • gpr.key 🙏🏻

@ovitrif ovitrif merged commit 5a3a822 into master Aug 15, 2025
5 checks passed
@ovitrif ovitrif deleted the chore/core-gh-package branch August 15, 2025 11:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants