Comment préparer mon application pour la version 64 bits pour React Native?

Question

Voici mon build.gradle:

    apply plugin: "com.Android.application"

import com.Android.build.OutputFile

/**
 * The react.gradle file registers a task for each build variant (e.g. bundleDebugJsAndAssets
 * and bundleReleaseJsAndAssets).
 * These basically call `react-native bundle` with the correct arguments during the Android build
 * cycle. By default, bundleDebugJsAndAssets is skipped, as in debug/dev mode we prefer to load the
 * bundle directly from the development server. Below you can see all the possible configurations
 * and their defaults. If you decide to add a configuration block, make sure to add it before the
 * `apply from: "../../node_modules/react-native/react.gradle"` line.
 *
 * project.ext.react = [
 *   // the name of the generated asset file containing your JS bundle
 *   bundleAssetName: "index.Android.bundle",
 *
 *   // the entry file for bundle generation
 *   entryFile: "index.Android.js",
 *
 *   // whether to bundle JS and assets in debug mode
 *   bundleInDebug: false,
 *
 *   // whether to bundle JS and assets in release mode
 *   bundleInRelease: true,
 *
 *   // whether to bundle JS and assets in another build variant (if configured).
 *   // See http://tools.Android.com/tech-docs/new-build-system/user-guide#TOC-Build-Variants
 *   // The configuration property can be in the following formats
 *   //         'bundleIn${productFlavor}${buildType}'
 *   //         'bundleIn${buildType}'
 *   // bundleInFreeDebug: true,
 *   // bundleInPaidRelease: true,
 *   // bundleInBeta: true,
 *
 *   // whether to disable dev mode in custom build variants (by default only disabled in release)
 *   // for example: to disable dev mode in the staging build type (if configured)
 *   devDisabledInStaging: true,
 *   // The configuration property can be in the following formats
 *   //         'devDisabledIn${productFlavor}${buildType}'
 *   //         'devDisabledIn${buildType}'
 *
 *   // the root of your project, i.e. where "package.json" lives
 *   root: "../../",
 *
 *   // where to put the JS bundle asset in debug mode
 *   jsBundleDirDebug: "$buildDir/intermediates/assets/debug",
 *
 *   // where to put the JS bundle asset in release mode
 *   jsBundleDirRelease: "$buildDir/intermediates/assets/release",
 *
 *   // where to put drawable resources / React Native assets, e.g. the ones you use via
 *   // require('./image.png')), in debug mode
 *   resourcesDirDebug: "$buildDir/intermediates/res/merged/debug",
 *
 *   // where to put drawable resources / React Native assets, e.g. the ones you use via
 *   // require('./image.png')), in release mode
 *   resourcesDirRelease: "$buildDir/intermediates/res/merged/release",
 *
 *   // by default the gradle tasks are skipped if none of the JS files or assets change; this means
 *   // that we don't look at files in Android/ or ios/ to determine whether the tasks are up to
 *   // date; if you have any other folders that you want to ignore for performance reasons (gradle
 *   // indexes the entire tree), add them here. Alternatively, if you have JS files in Android/
 *   // for example, you might want to remove it from here.
 *   inputExcludes: ["Android/**", "ios/**"],
 *
 *   // override which node gets called and with what additional arguments
 *   nodeExecutableAndArgs: ["node"],
 *
 *   // supply additional arguments to the packager
 *   extraPackagerArgs: []
 * ]
 */

project.ext.react = [
    entryFile: "index.js"
]

apply from: "../../node_modules/react-native/react.gradle"

/**
 * Set this to true to create two separate APKs instead of one:
 *   - An APK that only works on ARM devices
 *   - An APK that only works on x86 devices
 * The advantage is the size of the APK is reduced by about 4MB.
 * Upload all the APKs to the Play Store and people will download
 * the correct one based on the CPU architecture of their device.
 */
def enableSeparateBuildPerCPUArchitecture = false

/**
 * Run Proguard to shrink the Java bytecode in release builds.
 */
def enableProguardInReleaseBuilds = false

Android {
    compileSdkVersion 28
    buildToolsVersion "27.0.3"

    configurations {
        all*.exclude group: 'com.Android.support', module: 'support-v4'
        all*.exclude group: 'com.Android.support', module: 'support-annotations'
        compile.exclude group: "org.Apache.httpcomponents", module: "httpclient"
    }

    signingConfigs {
        release {
            if (project.hasProperty('MYAPP_RELEASE_STORE_FILE')) {
                storeFile file(MYAPP_RELEASE_STORE_FILE)
                storePassword MYAPP_RELEASE_STORE_PASSWORD
                keyAlias MYAPP_RELEASE_KEY_ALIAS
                keyPassword MYAPP_RELEASE_KEY_PASSWORD
            }
        }
    }


    defaultConfig {
        applicationId "com.example"
        minSdkVersion 16
        targetSdkVersion 28
        versionCode 1075
        versionName "1.0.75"
        multiDexEnabled true

        ndk {
            abiFilters 'armeabi-v7a' , 'x86'
        }


    dexOptions {
    javaMaxHeapSize "4g"
    preDexLibraries = false
    incremental true
}

compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }

    }
    splits {
        abi {
            reset()
            enable enableSeparateBuildPerCPUArchitecture
            universalApk false  // If true, also generate a universal APK
            include "armeabi-v7a", "x86"
        }
    }




    buildTypes {
        release {
            minifyEnabled enableProguardInReleaseBuilds
            matchingFallbacks = ['release', 'debug']
            proguardFiles getDefaultProguardFile("proguard-Android.txt"), "proguard-rules.pro"
            signingConfig signingConfigs.release
        }
    }

    // applicationVariants are e.g. debug, release
    applicationVariants.all { variant ->
        variant.outputs.each { output ->
            // For each separate APK per architecture, set a unique version code as described here:
            // http://tools.Android.com/tech-docs/new-build-system/user-guide/apk-splits
            def versionCodes = ["armeabi-v7a":1, "x86":2]
            def abi = output.getFilter(OutputFile.ABI)
            if (abi != null) {  // null for the universal-debug, universal-release variants
                output.versionCodeOverride =
                        versionCodes.get(abi) * 1048576 + defaultConfig.versionCode
            }
        }
    }
}


dependencies {

    compile project(':RNWebView')
    compile project(':react-native-share')
    implementation project(':lottie-react-native')

    implementation project(':react-native-smart-splashscreen')


    implementation fileTree(dir: 'libs', include: ['*.jar'])
    implementation "com.facebook.fresco:fresco:1.0.1"
    implementation "com.facebook.fresco:animated-gif:1.0.1"
    compile "com.facebook.react:react-native:+" // From node_modules

}



// Run this once to be able to run the application with BUCK
// puts all compile dependencies into folder libs for BUCK to use
task copyDownloadableDepsToLibs(type: Copy) {
    from configurations.compile
    into 'libs'
}

J'ai essayé d'ajouter 64 bits hier et je suis tombé sur un tas de problèmes, j'ai donc tout reconverti en 32. L'application fonctionne parfaitement en 32 bits, mais existe-t-il un moyen d'utiliser les 32 et 64 bits sans que l'application se bloque une fois que je l'ouvre ?

J'ai recherché quelques solutions mais la plupart d'entre elles étaient très déroutantes à suivre. J'ai mis à jour ndk avec le "x86", "x86_64", "armeabi-v7a", "arm64-v8a". Je ne sais pas si je mets également à jour le abi. Toute aide sur ce problème est très appréciée!

Answer 1

React Native 0.59 prend entièrement en charge les versions 64 bits Android, il possède déjà les modifications nécessaires pour les scripts Gradle, il n'est donc pas nécessaire de rechercher ce qu'il faut ajouter exactement.

Si vous avez la possibilité de mettre à niveau RN dans votre projet, il se peut que faites cela en utilisant great rn-diff-purge et l'aide qui l'entoure . Mais gardez à l'esprit que certaines autres dépendances pourraient également devoir être mises à niveau vers des versions plus récentes prenant en charge RN 0.59.