【问题标题】:React Native signed release builds but fails to startReact Native 签名版本构建但无法启动
【发布时间】:2017-03-12 14:48:02
【问题描述】:

我正在尝试在发布模式下运行我的 react 本机应用程序。 APK 已根据文档进行签名,并且第一次运行良好(无论是在模拟器中还是在真实设备中)。

经过一些更新(添加库、更改 gradle 配置、开发更多代码)后,发布安装不再起作用:

  • 在调试模式下一切正常(构建、模拟器和真机)
  • 在发布模式下构建正常,但应用程序在启动时崩溃(模拟器和真手机)

在日志中我看到以下错误:

adb logcat

....
Unable to instantiate application com.myfakeappname.MainApplication: java.lang.ClassNotFoundException: Didn't find class "com.myfakeappname.MainApplication" on path: DexPathList...
....

这是我的发布文件夹下的 AndroidManifest.xml

<manifest xmlns:android="http://schemas.android.com/apk/res/android"
      xmlns:tools="http://schemas.android.com/tools"
      package="com.myfakeappname">

      <application
        android:name=".MainApplication"
        >

      </application>
 </manifest>

编辑:添加 proguard-rules.pro

# Add project specific ProGuard rules here.
# By default, the flags in this file are appended to flags specified
# in /usr/local/Cellar/android-sdk/24.3.3/tools/proguard/proguard-android.txt
# You can edit the include path and order by changing the proguardFiles
# directive in build.gradle.
#
# For more details, see
#   http://developer.android.com/guide/developing/tools/proguard.html

# Add any project specific keep options here:

# If your project uses WebView with JS, uncomment the following
# and specify the fully qualified class name to the JavaScript interface
# class:
#-keepclassmembers class fqcn.of.javascript.interface.for.webview {
#   public *;
#}

# Disabling obfuscation is useful if you collect stack traces from production crashes
# (unless you are using a system that supports de-obfuscate the stack traces).
-dontobfuscate

# React Native

# Keep our interfaces so they can be used by other ProGuard rules.
# See http://sourceforge.net/p/proguard/bugs/466/
-keep,allowobfuscation @interface com.facebook.proguard.annotations.DoNotStrip
-keep,allowobfuscation @interface com.facebook.proguard.annotations.KeepGettersAndSetters
-keep,allowobfuscation @interface com.facebook.common.internal.DoNotStrip

# Do not strip any method/class that is annotated with @DoNotStrip
-keep @com.facebook.proguard.annotations.DoNotStrip class *
-keep @com.facebook.common.internal.DoNotStrip class *
-keepclassmembers class * {
    @com.facebook.proguard.annotations.DoNotStrip *;
    @com.facebook.common.internal.DoNotStrip *;
}

-keepclassmembers @com.facebook.proguard.annotations.KeepGettersAndSetters class * {
  void set*(***);
  *** get*();
}

-keep class * extends com.facebook.react.bridge.JavaScriptModule { *; }
-keep class * extends com.facebook.react.bridge.NativeModule { *; }
-keepclassmembers,includedescriptorclasses class * { native <methods>; }
-keepclassmembers class *  { @com.facebook.react.uimanager.UIProp <fields>; }
-keepclassmembers class *  { @com.facebook.react.uimanager.annotations.ReactProp <methods>; }
-keepclassmembers class *  { @com.facebook.react.uimanager.annotations.ReactPropGroup <methods>; }

-dontwarn com.facebook.react.**

# okhttp

-keepattributes Signature
-keepattributes *Annotation*
-keep class okhttp3.** { *; }
-keep interface okhttp3.** { *; }
-dontwarn okhttp3.**

# okio

-keep class sun.misc.Unsafe { *; }
-dontwarn java.nio.file.*
-dontwarn org.codehaus.mojo.animal_sniffer.IgnoreJRERequirement
-dontwarn okio.**

【问题讨论】:

  • 确保您在 java/com/myfakeappname/ 中有一个 MainApplication(相对于 AndroidManifest),并且在顶部您有:package com.myfakeappname;

标签: android react-native


【解决方案1】:

很可能您启用了 proguard 并且某些类被混淆了,因此在运行时找不到它们。

尝试在发布配置中禁用它,然后重试。如果需要,请发布您的 proguard.properties 文件。

【讨论】:

  • 禁用 proguard 确实有效。我将使用 proguar-rules.pro 编辑问题
  • 您发布的那些看起来不错。这些是 ReactNative 的基础。你有任何其他模块也可以向 proguard 配置添加规则吗?
猜你喜欢
  • 2019-12-05
  • 2022-08-17
  • 1970-01-01
  • 1970-01-01
  • 2019-11-20
  • 1970-01-01
  • 1970-01-01
  • 1970-01-01
  • 2019-01-16
相关资源
最近更新 更多