Update react-native libraries under node_modules to androidx

androidx-class-mapping.csv

androidx.sh

#!/usr/bin/env bash

# I've found that the "Migrate to AndroidX" converter in Android Studio doesn't work very
# well, so I wrote my own script to do the simple job of converting package names.
#
# You can download a CSV of package names here: https://developer.android.com/topic/libraries/support-library/downloads/androidx-class-mapping.csv
#
# It'll run faster on a clean build because then there are fewer files to scan over.
#
# Uses `gsed` because I'm on a Mac. Can easily replace with `sed` if you don't have `gsed`.
#
# This isn't perfect; it won't find every conversion issue. You break it you buy it. Viewer discretion is advised.

MAPPING_FILE=scripts/androidx-class-mapping.csv
PROJECT_DIR=node_modules

replace=""
while IFS=, read -r from to
do
	replace+="; s/$from/$to/g"
done <<< "$(cat $MAPPING_FILE)"

find $PROJECT_DIR \( -name "*.java" -o -name "*.xml" \) -type f -not -path '*/\.git*' -print0 | xargs -0 gsed -i "$replace"

Hey there! A few react-native folks saw this and I attempted to integrate it into our plan for AndroidX migration - you can see the result here https://github.com/mikehardy/jetifier - if you'd like to collaborate, please feel free!

Also you may notice that I altered the find/xargs/gsed - for me anyway I couldn't make it work reliably without getting "argument list too long" errors in various stages no matter I did, so I just made a boring loop. I might allow a black list of modules you could specify that don't need the transform though - or something similar - to increase performance, it's pretty slow now. But it seems to work, which is amazing!

Cheers

hi !

I have the following error when running your script on a Mac xargs: gsed: No such file or directory. Do you have a solution ?

@kiralex install gsed for mac brew install gnu-sed

You can try the jetifier npm package, which was inspired by and integrates this idea, but uses the standard macOS sed, if you like.

@kiralex @michalakjan may i know how to run this script?

@nolife08021 - at this point I have to recommend jetifier, based on (and with thanks to) this script, and currently getting very heavy usage and community testing https://github.com/mikehardy/jetifier/graphs/traffic - this AndroidX changeover is a little difficult but the community is working together pretty well to get through it I think

What a shit storm. Imagine the number of people this fiasco scared away from react native.

Thanks @janicduplessis, my issue fixed for now.

@mikehardy thanks for the tool, so is this the list you're using? https://developer.android.com/jetpack/androidx/migrate
it appears to be missing: androidx.appcompat:appcompat?

@export-mike
I am yes, and I just made it so you can verify the checksum if you want (because who am I, really? :-) ), I’m going to operate under the general assumption it isn’t missing anything except renderscript (a known AndroidX migration thing) though as it’s in use by lots of people, has a test suite, and is getting about 1000 downloads a day.

At the same time, software is always surprising so if you can alter the associated rn-androidx-demo test suite and show a failure please log an issue! There are 4 of us working on it to make the AndroidX transition smooth, and we’ll try to get a fix in

Right that’s awesome! Just been having issues you’ve already helped me with. Again thanks for you help. Took some time to catch up and figure out what’s going on!

Thanks for this tool, it was very difficult to figure out mapping AndroidX support library without this..I am using react-native and had to manually change imports in third party libraries..Not sure if there any tool to automate this..

@gururajphadnis If only someone would write an automated tool and take the time to comment here about it! (which means: read the comments here) ;-)

Unable to resolve dependency for ':app@debug/compileClasspath': Could not find any version that matches androidx.appcompat:appcompat:27.+. |  
Unable to resolve dependency for ':app@debugAndroidTest/compileClasspath': Could not find any version that matches androidx.appcompat:appcompat:27.+. |  

i'm encountering this since last few days already.. any idea about it?? I tried this "https://github.com/mikehardy/jetifier" but nothing happens also.. still encountering this issue.. I was wondering how come my library became 27.+? i imported it like this "compile 'androidx.appcompat:appcompat:1.0.2'".. should be fine right? :|

I tried with jetifier eventhough i am getting this error:

FAILURE: Build failed with an exception.

• What went wrong:
  Could not determine the dependencies of task ':app:preDebugBuild'.

Could not resolve all task dependencies for configuration ':app:debugRuntimeClasspath'.
Could not find androidx.appcompat:appcompat:28.0.0.
Required by:
project :app
Could not find androidx.appcompat:appcompat:28.0.0.
Required by:
project :app > project :react-native-signature-capture
Could not find androidx.appcompat:appcompat:28.0.0.
Required by:
project :app > project :react-native-share
project :app > project :react-native-fbsdk
project :app > project :lottie-react-native
Could not find androidx.appcompat:appcompat:28.0.0.
Required by:
project :app > project :react-native-smart-splash-screen
Could not find androidx.appcompat:appcompat:28.0.0.
Required by:
project :app > com.facebook.react:react-native:0.60.0
Could not find androidx.appcompat:appcompat:28.0.0.
Required by:
project :app > project :lottie-react-native > com.airbnb.android:lottie:2.5.6
project :app > project :react-native-scratch-card > com.clock.scratch:Scratch:1.0.0
project :app > project :react-native-fbsdk > com.facebook.android:facebook-android-sdk:4.34.0 > com.facebook.android:facebook-common:4.34.0
project :app > project :react-native-fbsdk > com.facebook.android:facebook-android-sdk:4.34.0 > com.facebook.android:facebook-login:4.34.0

same here +1.

@ganico, @PravsRedddy, you guys find the solution?

This isn't the right place to discuss anything anymore at this point. The jetifier package is fully integrated with react-native-community/cli under the covers now, for react-native 0.60 and is working for everyone that migrates their app correctly, and updates their dependencies correctly assuming all their libraries are up to date. Those are big ifs, but have nothing really to do with the core classname translation idea / implementation

@mikehardy, Here is what I did.

1. Migrate to AndroidX via Android Studio 3.4.2
2. npx jetify
3. react-native run-android

There is something I missed?

I'm not offering support for random projects on a random gist, sorry :-). I support discovered bugs in jetifier filed as issues there with good reproduction cases