[Android] HTTP 403 downloading React Android 0.86.3 and Hermes debug AARs
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- android, react-native
- Domain
- build-system, mobile
Research direction
Start by checking the reported artifact URLs and the Android dependency resolution path for React Android 0.86.3 and Hermes Android 250829098.0.17; the issue does not name repository files or tests. First establish whether the 403 responses are reproducible and capture response headers and error bodies. Done means identifying the responsible artifact or infrastructure path and confirming the Android build can download the required artifacts.
Written by the indexing model from the issue text.
Description
Description
On October 25, 2026, HTTPS GET requests for these Android debug artifacts returned HTTP 403 Forbidden, with zero artifact bytes downloaded:
React Android 0.86.3:
https://repo.reactnative.dev/maven2/com/facebook/react/react-android/0.86.3/react-android-0.86.3-debug.aar
Hermes Android 250829098.0.17:
https://repo.reactnative.dev/maven2/com/facebook/hermes/hermes-android/250829098.0.17/hermes-android-250829098.0.17-debug.aar
The Android build is blocked before APK generation. A preceding HEAD request to Maven Central redirected to the React Android URL above, consistent with Sonatype’s documented policy:
https://central.sonatype.org/faq/429-operational-dependencies/
Expected: published Android artifacts download successfully.
Actual: both GET requests returned HTTP 403.
This occurred in an Expo 57.0.27 project using React Native 0.86.3, before the application could run. Please advise whether this belongs here, in Expo’s tracker, or in a separate artifact-infrastructure channel.
Response headers and error bodies were not retained, so the cause is unknown. These are recorded failures, not a fresh availability check. Related issue #58427 concerns an earlier iOS 404; we are not assuming the same cause.
Steps to reproduce
Historical steps performed on October 25, 2026:
- Attempt an Android Debug build requiring React Android 0.86.3 and Hermes Android 250829098.0.17.
- Observe Maven Central redirecting the React Android artifact to repo.reactnative.dev.
- Attempt one HTTPS GET for each artifact URL in the description.
- Both return HTTP 403 Forbidden with zero artifact bytes downloaded; no APK is generated.
No retries or version changes were performed. We have not established whether all clients are affected. HEAD requests may behave differently from the failed GET requests.
React Native Version
0.86.3
Affected Platforms
Build - MacOS, Runtime - Android
Output of npx @react-native-community/cli info
Leave this pending. We need actual output from the Mac, with private paths reviewed before sharing. Don’t paste an invented environment report. Running npx can download software if the CLI isn’t installed, so we should check the existing local CLI first.
8Leave this pending. We need actual output from the Mac, with private paths reviewed before sharing. Don’t paste an invented environment report. Running npx can download software if the CLI isn’t installed, so we should check the existing local CLI first.
Stacktrace or Logs
Summary of recorded outcomes, not raw response headers:
React Android 0.86.3-debug.aar:
HTTPS GET returned HTTP 403 Forbidden.
Artifact bytes downloaded: 0.
Hermes Android 250829098.0.17-debug.aar:
HTTPS GET returned HTTP 403 Forbidden.
Artifact bytes downloaded: 0.
Failure record saved: 2026-10-25 21:55:43 UTC.
Individual request timestamps, response headers and error bodies were not retained.
No APK was generated.
MANDATORY Reproducer
https://github.com/disruptdesignsllc-ai/react-native-android-aar-403-repro
Screenshots and Videos
No response
- Dominant language
- C++
- Stars
- 127k
- Forks
- 25.5k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 235
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from react/react-native
-
Needs: Author Feedback Needs: Repro
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
react/react-native#60059 · 1 comment ·
Maintainers usually reply within 2 days
-
Needs: Triage :mag:
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
react/react-native#60000 ·
Maintainers usually reply within 2 days
-
`yarn test-ios` exits before building RNTester: `objc-test.sh` launches the WebSocket server script #59433 deletedPossibly taken @lazerg claimed this 4 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
react/react-native#59939 ·
Maintainers usually reply within 2 days
-
iOS Fabric pointer-handler reset leaves the next lone touch non-primaryPossibly taken @alleneubank claimed this 6 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
react/react-native#59919 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
react/react-native#59722 ·
Maintainers usually reply within 2 days
All issues in react/react-native
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
petercorke/robotics-toolbox-python#943 · 1 comment ·
Maintainers usually reply within 1 day
-
area:build bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
NatronGitHub/openfx-arena#71 ·
Maintainers usually reply within 1 day
-
upstream-blocked
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ROCm/FastFlowLM#1057 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
NatronGitHub/openfx-gmic#45 ·
Maintainers usually reply within 1 day