mapbox / mapbox/mapbox-maps-flutter

Gradle execution failed because no access token on version 1.1.0

Open
#495 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Dart
Stars
380
Forks
204
PR merge metrics
No merged PRs in 30d

Description

Debug console:
```
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:checkDebugAarMetadata'.
> Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
> Could not resolve com.mapbox.maps:android:11.3.0.
Required by:
project :app > project :mapbox_maps_flutter
> Could not resolve com.mapbox.maps:android:11.3.0.
> Could not get resource 'https://api.mapbox.com/downloads/v2/releases/maven/com/mapbox/maps/android/11.3.0/android-11.3.0.pom'.
> Could not GET 'https://api.mapbox.com/downloads/v2/releases/maven/com/mapbox/maps/android/11.3.0/android-11.3.0.pom'. Received status code 403 from server: Forbidden
```

link:
`{"message":"Not Authorized - No Token","url":"[GET] /downloads/v2/releases/maven/com/mapbox/maps/android/11.3.0/android-11.3.0.pom","auth":"","ua":"Amazon CloudFront"}`

I had my public access token set on launch.json btw (if related), it works fine before.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the reported Gradle task ':app:checkDebugAarMetadata' and the Mapbox Android dependency resolution failure for version 11.3.0. Check how the public access token in launch.json is supplied to the Android/Gradle build, then reproduce the 403 response and verify that dependency resolution succeeds with the intended configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
dart, flutter
Domain
build-system, mobile
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.