简体   繁体   English

具有释放模式的黑屏,应用程序无法启动。 在调试模式下工作正常

[英]Blank screen with release mode, app does not start. Working fine in debug mode

I just created my release candidate with Android Studio in release mode and generating a signed apk. 我刚刚在发布模式下使用Android Studio创建了我的候选发布者,并生成了一个签名的apk。 Everything fine, but when I test it in my device or other devices, the app starts and just shows a blank screen. 一切正常,但是当我在设备或其他设备上对其进行测试时,该应用程序将启动并仅显示空白屏幕。 No login screen, nothing. 没有登录屏幕,什么都没有。

The logs of the release version doesn't say anything to me. 发布版本的日志没有对我说什么。 It's the first time that happens to me after 4 years of app development. 经过4年的应用程序开发,这是我第一次发生这种情况。 I don't really understand what's going on. 我不太了解发生了什么。

I've also tried the rolling back to the version that we have in Google Play Store, same happens. 我也尝试过回滚到我们在Google Play商店中拥有的版本,同样的情况也是如此。 Debug working fine, Release signed not working. 调试正常,发布签名不起作用。

I tried it with another computer and another phone, same issues. 我在另一台计算机和另一部电话上尝试过,同样的问题。

I will appreciate any help, because I never felt that lost. 我将不胜感激,因为我从没有感到失去。

These are the logs 这些是日志

09-13 17:27:07.837 16977-16977/? I/applabs.sharif: Late-enabling -Xcheck:jni
09-13 17:27:07.918 16977-16977/es.sharifyapplabs.sharify I/applabs.sharif: The ClassLoaderContext is a special shared library.
09-13 17:27:08.052 16977-16977/es.sharifyapplabs.sharify I/MultiDex: VM with version 2.1.0 has multidex support
    Installing application
    VM has multidex support, MultiDex support library is disabled.
    Installing application
    VM has multidex support, MultiDex support library is disabled.
09-13 17:27:08.080 16977-16977/es.sharifyapplabs.sharify D/FirebaseApp: com.google.firebase.crash.FirebaseCrash is not linked. Skipping initialization.
09-13 17:27:08.096 16977-16977/es.sharifyapplabs.sharify I/FirebaseInitProvider: FirebaseApp initialization successful
09-13 17:27:08.138 16977-16977/es.sharifyapplabs.sharify I/CrashlyticsCore: Initializing Crashlytics 2.6.1.23
09-13 17:27:08.151 16977-16977/es.sharifyapplabs.sharify I/CrashlyticsInitProvider: CrashlyticsInitProvider initialization successful
09-13 17:27:08.168 16977-16977/es.sharifyapplabs.sharify E/com.facebook.internal.a: getAttributionIdentifiers should not be called from the main thread
09-13 17:27:08.178 16977-17019/es.sharifyapplabs.sharify D/NetworkSecurityConfig: No Network Security Config specified, using platform default
09-13 17:27:08.276 16977-17002/es.sharifyapplabs.sharify I/FA: App measurement is starting up, version: 12451
    To enable debug logging run: adb shell setprop log.tag.FA VERBOSE
    To enable faster debug mode event logging run:
      adb shell setprop debug.firebase.analytics.app es.sharifyapplabs.sharify
09-13 17:27:18.273 16977-17014/es.sharifyapplabs.sharify W/Fabric: Could not call getAdvertisingIdInfo on com.google.android.gms.ads.identifier.AdvertisingIdClient
09-13 17:27:18.274 16977-17014/es.sharifyapplabs.sharify W/Fabric: Could not call getId on com.google.android.gms.ads.identifier.AdvertisingIdClient$Info
09-13 17:27:28.333 16977-17014/es.sharifyapplabs.sharify W/Fabric: Could not call getAdvertisingIdInfo on com.google.android.gms.ads.identifier.AdvertisingIdClient
09-13 17:27:28.334 16977-17014/es.sharifyapplabs.sharify W/Fabric: Could not call isLimitAdTrackingEnabled on com.google.android.gms.ads.identifier.AdvertisingIdClient$Info
09-13 17:27:28.658 16977-17006/es.sharifyapplabs.sharify D/skia: --- Failed to create image decoder with message 'unimplemented'
09-13 17:27:29.907 16977-17006/es.sharifyapplabs.sharify W/CrashlyticsCore: Expected method missing: registerOnMeasurementEventListener
    java.lang.NoSuchMethodException: parameter type is null
        at java.lang.Class.getMethod(Class.java:2060)
        at java.lang.Class.getDeclaredMethod(Class.java:2047)
        at com.crashlytics.android.c.u.a(DefaultAppMeasurementEventListenerRegistrar.java:89)
        at com.crashlytics.android.c.u.a(DefaultAppMeasurementEventListenerRegistrar.java:54)
        at com.crashlytics.android.c.k.a(CrashlyticsController.java:1574)
        at com.crashlytics.android.c.l.d(CrashlyticsCore.java:320)
        at com.crashlytics.android.c.l.e(CrashlyticsCore.java:44)
        at c.a.a.a.h.a(InitializationTask.java:63)
        at c.a.a.a.h.a(InitializationTask.java:28)
        at c.a.a.a.a.c.a$2.call(AsyncTask.java:311)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:458)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
        at java.lang.Thread.run(Thread.java:764)
09-13 17:27:38.083 16977-16996/es.sharifyapplabs.sharify E/FirebaseInstanceId: Token retrieval failed: SERVICE_NOT_AVAILABLE
09-13 17:28:38.101 16977-16996/es.sharifyapplabs.sharify E/FirebaseInstanceId: Token retrieval failed: SERVICE_NOT_AVAILABLE
09-13 17:30:08.126 16977-16996/es.sharifyapplabs.sharify E/FirebaseInstanceId: Token retrieval failed: SERVICE_NOT_AVAILABLE

1) Invalidate Cache/Restart Android Studio. 1)使缓存无效/重新启动Android Studio。

2) Refresh Build completely, Sign Apk & test! 2)完全刷新版本,登录并测试!

I just found the solution. 我刚刚找到了解决方案。 Basically Facebook messed up again. 基本上,Facebook再次陷入困境。

Related to the dependency in gradle. 与gradle中的依赖关系有关。

App getting stuck with E/com.facebook.internal.AttributionIdentifiers 应用陷入E / com.facebook.internal.AttributionIdentifiers

暂无
暂无

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 谷歌地图在发布apk中显示空白屏幕,在调试模式下工作正常 - Google Maps displaying blank screen in release apk, working fine in debug mode Android应用程式在侦错模式下运作良好,但在发布模式下当机 - Android app working fine in debug mode but crashing in release mode Firebase电话身份验证在调试模式下可以正常工作,但该应用在发行时崩溃 - Firebase phone authentication is working fine in debug mode but the app is crashing in release 应用程序在发布时崩溃,但在调试模式下工作正常 - App Crashes in release but works fine in Debug mode Flutter 应用程序在发布模式下显示灰屏,但在调试模式下工作正常 - Flutter app show grey screen in release mode but works fine in debug mode Flutter 应用程序在发布模式下显示灰屏,但在调试模式下工作正常 'DiagnosticsProperty 实例<void> '</void> - Flutter app show grey screen in release mode but works fine in debug mode Instance of 'DiagnosticsProperty<void>' Google地图无法在发布模式下运行,但在调试模式下可以正常运行 - Google maps not working in release mode but working fine in debug mode 无法在发布模式下构建 Flutter 应用程序,但在调试模式下工作正常 - Cannot Build Flutter App in Release Mode but works fine in debug mode Flutter 应用程序未在调试模式下启动 - Flutter app does not start in debug mode react-native-geolocation-service 按预期在调试模式下工作正常但在发布模式下不工作 - react-native-geolocation-service working perfectly fine in debug mode as expected but not working in release mode
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM