fix(all, android): purge jcenter() from android build #5195
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Only remaining jcenter usage is in our tests app, not used by
library consumers, where we must retain it until react-native itself
is jcenter-free
Also bumped everything in the template to current and bumped kotlin in tests app to 1.4.32 from 1.4.31 but no one will notice or care ;-)
Related issues
Tracking remaining usage: react-native-community/releases#221 (comment)
Release Summary
It's a conventional commit message
Checklist
Android
iOS
e2e
tests added or updated inpackages/\*\*/e2e
jest
tests added or updated inpackages/\*\*/__tests__
Test Plan
I ran
yarn tests:build:test
to make sure everything still built after. It still builds, unless you comment out the final jcenter line, then it fails on known problems (link above).Think
react-native-firebase
is great? Please consider supporting the project with any of the below:React Native Firebase
andInvertase
on Twitter