Android build fails to resolve TalsecSecurity-Community-ReactNative 19.2.3

[SKYLARK-13]

Android build fails to resolve TalsecSecurity-Community-ReactNative 19.2.3

I'm integrating freerasp-react-native@5.2.1 into an existing React Native Android application.

Environment:

• React Native: 0.79.7
• freerasp-react-native: 5.2.1
• Android SDK dependency: 19.2.3

The package declares the following dependency:

com.aheaditec.talsec.security:TalsecSecurity-Community-ReactNative:19.2.3

The package's android/build.gradle also declares these Talsec repositories:

https://europe-west3-maven.pkg.dev/talsec-artifact-repository/freerasp

https://europe-west3-maven.pkg.dev/talsec-artifact-repository/common

However, Gradle fails with:

Could not find com.aheaditec.talsec.security:TalsecSecurity-Community-ReactNative:19.2.3

I also verified manually that the exact POM URL is accessible and returns HTTP 200:

https://europe-west3-maven.pkg.dev/talsec-artifact-repository/freerasp/com/aheaditec/talsec/security/TalsecSecurity-Community-ReactNative/19.2.3/TalsecSecurity-Community-ReactNative-19.2.3.pom

Could you please confirm the correct repository/configuration required for freerasp-react-native@5.2.1?

Is this a known Gradle/dependency-resolution issue with version 5.2.1?

Thanks.

[SirionRazzer]

Hi @SKYLARK-13 ,
I will check it out, thank you for letting us know :)

I will be right back.

Cheers,
Tomas

[SirionRazzer]

Hi @SKYLARK-13,

(I used LLM to generate this, seems to be a good direction to try out)

Two things to try, in order:

Force a refresh, which clears Gradle's cached "missing module" result:

cd android && ./gradlew :app:dependencies --configuration debugRuntimeClasspath --refresh-dependencies

If that doesn't do it, could you share your android/settings.gradle (or .kts)?

Our Maven repos are declared inside the library's own build.gradle, and a few setups — notably Expo apps after expo prebuild, and projects using dependencyResolutionManagement { repositoriesMode … } — drop or override those, which produces exactly this error while the URL stays reachable in a browser. That's been the cause in most previous reports of this (talsec/Free-RASP-ReactNative#141, talsec/Free-RASP-ReactNative#51).

Also worth mentioning: is this an Expo app, and do your builds go through an internal Nexus/Artifactory mirror rather than hitting pkg.dev directly? We republished 19.2.3 in place on Sep 7 to fix an unrelated crash (talsec/Free-RASP-ReactNative#161), and a proxy that cached a miss during that window would behave like this.

Cheers,
Tomas

[SKYLARK-13]

@SirionRazzer Thanks for the response,
I tried --refresh-dependencies, but the actual Android build still fails with the same TalsecSecurity-Community-ReactNative:19.2.3 resolution error.

This is a React Native 0.79.7 app and not an Expo app.

Our android/settings.gradle does not use dependencyResolutionManagement or repositoriesMode.

We also don't use an internal Nexus/Artifactory mirror for these dependencies.

[SirionRazzer]

OK, I will hand this over to my colleague to double check.

[tompsota]

Hi @SKYLARK-13 ,

I verified that the artifacts are accessible, so this is not a bug. Maybe there is something blocking the connection on your end, some other gradle prebuild script that removes our dependency, etc.

As a solution, you can try to declare the repos in your own project. Add in android/build.gradle:

allprojects {
repositories {
maven {url "https://europe-
west3-maven.pkg.dev/talsec-
artifact-repository/freerasp" } maven {url "https://europe-
west3-maven.pkg.dev/talsec-
artifact-repository/common" }
}

To confirm the diagnosis, you can check the full error block - specifically the Searched in the following locations: list. If our two pkg. dev URLs are missing from it, that confirms this

Kind regards,
Tomas

[SKYLARK-13]

Thanks for the guidance. Adding the Talsec Maven repositories to android/build.gradle resolved the issue.

One suggestion: these repository declarations could be mentioned in the React Native integration docs, as they weren't clear from the current documentation.

Thanks for the support!