Common Crash Workaround

1. Target Android 9 (API 28)  cause NoClassDefFoundError:
fix api 28 (Android 9) add inside <application> tag
<uses-library android:name="org.apache.http.legacy" android:required="false"/>
https://stackoverflow.com/questions/50461881/java-lang-noclassdeffounderrorfailed-resolution-of-lorg-apache-http-protocolve

2. /data/app/com.google.android.webview-1/lib/arm/libwebviewchromium.so:
Add ndk abifilters to gradle file
ndk {
            abiFilters 'armeabi', 'armeabi-v7a', 'armeabi-v8a', 'x86', 'x86_64', 'mips', 'mips64'
        }
https://bugs.chromium.org/p/chromium/issues/detail?id=547842

3. Invoke-customs are only supported starting with android 0 --min-api 26  https://stackoverflow.com/questions/49891730/invoke-customs-are-only-supported-starting-with-android-0-min-api-26
Fix:
android {
    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }
}

firebase-inapp-messaging + picasso

https://stackoverflow.com/questions/51933538/unable-to-use-firebase-in-app-messaging
=> remove picasso, can still using picasso without register

4. If still using android-support, maybe occur Gradle Compatible.
Reference: https://stackoverflow.com/questions/56895868/gradlecompatible-new-version
Fix: Migrate to AndroidX, Or add bellow dependencies:
implementation 'com.android.support:customtabs:28.0.0'
DO NOT add suppress: //noinspection GradleCompatible