Could not resolve com.mapbox.maps:android:10.18.4.

[jyotykumari63]

Environment

• Dev OS: Win10, web, Android emulator
• @rnmapbox/maps version: "^10.1.33"
• React Native version: "0.76.5"
• Expo version: "~52.0.24"

Steps to reproduce

[<!--- We don't troubleshoot existing projects, please reproduce the issue in a brand new project. If you can't then create a new working project and compare with the one you're having trouble with. --->

Followed the link to setup rnmapbox.
](https://rnmapbox.github.io/docs/install?rebuild=expo#rebuild)

1." npm run android " throws below error -
Could not determine the dependencies of task ':app:compileDebugJavaWithJavac'.

Could not resolve all dependencies for configuration ':app:debugCompileClasspath'.
Could not resolve com.mapbox.maps:android:10.18.4.
Required by:
project :app
> Could not resolve com.mapbox.maps:android:10.18.4.
> Could not get resource 'https://api.mapbox.com/downloads/v2/releases/maven/com/mapbox/maps/android/10.18.4/android-10.18.4.pom'.
> Could not GET 'https://api.mapbox.com/downloads/v2/releases/maven/com/mapbox/maps/android/10.18.4/android-10.18.4.pom'. Received status code 403 from server: Forbidden

• Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
Get more help at https://help.gradle.org.

BUILD FAILED in 1m 33s

2. npm start and pressing "w" for web is working and showing map with rnmapbox
3. npm start and pressing "a" for android showing error on emulator screen :
   "Error: @rnmapbox/maps native code not available. Make sure you have linked the library and rebuild your app. See https://rnmapbox.github.io/docs/install?rebuild=expo#rebuild"
   

[gezquinndesign]

Any joy on a workaround?

[jyotykumari63]

Yes, I created the mapbox token with Download:read permission. With Newly created secret token I am able todo android build. For web platform newly created secret token is not working , web platform need public key.

[gezquinndesign]

Ah, thanks @jyotykumari63 - you helped me find the source of the problem. I'd selected the wrong permission in my secret token.