Native App build fails

0
Hello Community,I'm currently working an our Native Application and recently moved this project from Mendix 11.7 to Mendix 11.8 and ever since I'm having problems with my build process.I running against a 403 while my NPM install statement runs:Could not resolve com.github.doublesymmetry:kotlinaudio:v2.1.0. > Could not get resource 'https://packages.rnd.mendix.com/jcenter/com/github/doublesymmetry/kotlinaudio/v2.1.0/kotlinaudio-v2.1.0.pom'. > Could not HEAD 'https://packages.rnd.mendix.com/jcenter/com/github/doublesymmetry/kotlinaudio/v2.1.0/kotlinaudio-v2.1.0.pom'. Received status code 403 from server: Forbiddento try and couteract on this I rebuild our Github, added nothing and let Mendix handle everything but still when running my build it crashes on the same error as above.Anyone any recommendations on this problem?
asked
2 answers
0

Hi Niek,

The interesting part of the error is not actually the Mendix upgrade itself, but the 403 Forbidden:


Plain Text



Could not resolve com.github.doublesymmetry:kotlinaudio:v2.1.0

Received status code 403 from server: Forbidden

This suggests Gradle is able to find the repository URL, but it is not allowed to download the artifact.

A few things I'd check:

1. Verify Native Mobile dependencies

Did you also upgrade:

  • Native Mobile Resources
  • Native Template
  • Make It Native / Native Builder dependencies

when moving from 11.7 → 11.8?

I've seen build failures after Studio Pro upgrades where the native project was still using older dependency definitions.

2. Clear Gradle caches

Try removing:


Plain Text



~/.gradle/caches

and then regenerate the native project and build again.

Sometimes Gradle retains metadata pointing at repositories that are no longer valid.

3. Check custom native libraries

kotlinaudio is commonly pulled in through audio/media-related React Native packages.

If your app contains:

  • Audio widgets
  • Custom native modules
  • React Native dependencies added manually

I'd inspect the generated:


Plain Text



android/build.gradle

android/app/build.gradle

and search for:


Plain Text



kotlinaudio

to identify which package is requesting it.

4. Test with a freshly generated native project

Since you mentioned:

I rebuilt our Github and let Mendix handle everything

I'd create a completely fresh Native Builder project from the current Mendix 11.8 application and compare the generated Gradle files with the failing one.

5. Repository access issue

The URL:


Plain Text



https://packages.rnd.mendix.com/jcenter/...

returning a 403 makes me wonder whether:

  • the artifact has moved,
  • the repository configuration is outdated,
  • or a dependency is requesting an old repository path that is no longer publicly accessible.

Since the failure occurs during dependency resolution, I would inspect which dependency pulls in:


Plain Text



com.github.doublesymmetry:kotlinaudio:v2.1.0

because that is likely the actual component that needs updating.

My suspicion is that the 11.8 upgrade exposed an outdated native dependency rather than there being a problem with the Mendix application itself. The dependency tree (gradlew dependencies) usually reveals the offending package quite quickly.

Hope this helps.


answered
0

Hi Niek,


The interesting part of the error is not actually the Mendix upgrade itself, but the 403 Forbidden:


Plain Text

Could not resolve com.github.doublesymmetry:kotlinaudio:v2.1.0


Received status code 403 from server: Forbidden


This suggests Gradle is able to find the repository URL, but it is not allowed to download the artifact.


A few things I'd check:


1. Verify Native Mobile dependencies


Did you also upgrade:


Native Mobile Resources

Native Template

Make It Native / Native Builder dependencies


when moving from 11.7 → 11.8?


I've seen build failures after Studio Pro upgrades where the native project was still using older dependency definitions.


2. Clear Gradle caches


Try removing:


Plain Text

~/.gradle/caches


and then regenerate the native project and build again.


Sometimes Gradle retains metadata pointing at repositories that are no longer valid.


3. Check custom native libraries


kotlinaudio is commonly pulled in through audio/media-related React Native packages.


If your app contains:


Audio widgets

Custom native modules

React Native dependencies added manually


I'd inspect the generated:


Plain Text

android/build.gradle

android/app/build.gradle


and search for:


Plain Text

kotlinaudio


to identify which package is requesting it.


4. Test with a freshly generated native project


Since you mentioned:


I rebuilt our Github and let Mendix handle everything


I'd create a completely fresh Native Builder project from the current Mendix 11.8 application and compare the generated Gradle files with the failing one.


5. Repository access issue


The URL:


Plain Text

https://packages.rnd.mendix.com/jcenter/...


returning a 403 makes me wonder whether:


the artifact has moved,

the repository configuration is outdated,

or a dependency is requesting an old repository path that is no longer publicly accessible.


Since the failure occurs during dependency resolution, I would inspect which dependency pulls in:


Plain Text

com.github.doublesymmetry:kotlinaudio:v2.1.0


because that is likely the actual component that needs updating.


My suspicion is that the 11.8 upgrade exposed an outdated native dependency rather than there being a problem with the Mendix application itself. The dependency tree (gradlew dependencies) usually reveals the offending package quite quickly.


Hope this helps.

answered