【问题标题】:java.lang.IllegalArgumentException: Expected URL scheme 'http' or 'https' but no colon was foundjava.lang.IllegalArgumentException:预期的 URL 方案“http”或“https”,但未找到冒号
【发布时间】:2020-10-20 22:22:37
【问题描述】:

我在 prod 上遇到了这样的崩溃,但不明白这是怎么发生的。我是具有正确链接的初始化 Zendesk SDK,该链接具有 https 方案,但在 prod 上仍然出现此错误。当我们对此进行测试时 - 一切都很好。它可能与一些firebase问题有关吗?我正在从 firebase 远程配置中获取此 url,但我也有在本地字符串中硬编码的 url 版本,如果远程配置获取失败 - 我正在使用默认值。

我正在使用:

api group: 'com.zendesk', name: 'support', version: '5.0.1' //Zendesk SDK for Android
com.squareup.retrofit2:retrofit:2.7.2
com.squareup.retrofit2:converter-gson:2.7.2
com.squareup.retrofit2:adapter-rxjava2:2.7.2
com.squareup.okhttp3:logging-interceptor:4.4.0

崩溃报告:

Fatal Exception: java.lang.RuntimeException: Unable to create application com.myApplication.application.MyApp: java.lang.IllegalArgumentException: Expected URL scheme 'http' or 'https' but no colon was found
   at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6079)
   at android.app.ActivityThread.access$1300(ActivityThread.java:207)
   at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1758)
   at android.os.Handler.dispatchMessage(Handler.java:106)
   at android.os.Looper.loop(Looper.java:193)
   at android.app.ActivityThread.main(ActivityThread.java:6898)
   at java.lang.reflect.Method.invoke(Method.java)
   at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:537)
   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)

第二部分:

Caused by java.lang.IllegalArgumentException: Expected URL scheme 'http' or 'https' but no colon was found
   at okhttp3.HttpUrl$Builder.parse$okhttp(HttpUrl.kt:1261)
   at okhttp3.HttpUrl$Companion.get(HttpUrl.kt:1634)
   at okhttp3.HttpUrl.get(:2)
   at retrofit2.Retrofit$Builder.baseUrl(Retrofit.java:492)
   at zendesk.core.ZendeskNetworkModule.provideCoreRetrofit(ZendeskNetworkModule.java:220)
   at zendesk.core.ZendeskNetworkModule_ProvideCoreRetrofitFactory.provideCoreRetrofit(ZendeskNetworkModule_ProvideCoreRetrofitFactory.java:43)
   at zendesk.core.ZendeskNetworkModule_ProvideCoreRetrofitFactory.get(ZendeskNetworkModule_ProvideCoreRetrofitFactory.java:32)
   at zendesk.core.ZendeskNetworkModule_ProvideCoreRetrofitFactory.get(ZendeskNetworkModule_ProvideCoreRetrofitFactory.java:11)
   at dagger.internal.DoubleCheck.get(DoubleCheck.java:47)
   at zendesk.core.ZendeskProvidersModule_ProvideBlipsServiceFactory.get(ZendeskProvidersModule_ProvideBlipsServiceFactory.java:22)
   at zendesk.core.ZendeskProvidersModule_ProvideBlipsServiceFactory.get(ZendeskProvidersModule_ProvideBlipsServiceFactory.java:9)
   at dagger.internal.DoubleCheck.get(DoubleCheck.java:47)
   at zendesk.core.ZendeskProvidersModule_ProviderZendeskBlipsProviderFactory.get(ZendeskProvidersModule_ProviderZendeskBlipsProviderFactory.java:45)
   at zendesk.core.ZendeskProvidersModule_ProviderZendeskBlipsProviderFactory.get(ZendeskProvidersModule_ProviderZendeskBlipsProviderFactory.java:9)
   at dagger.internal.DoubleCheck.get(DoubleCheck.java:47)
   at zendesk.core.ZendeskProvidersModule_ProviderBlipsCoreProviderFactory.get(ZendeskProvidersModule_ProviderBlipsCoreProviderFactory.java:22)
   at zendesk.core.ZendeskProvidersModule_ProviderBlipsCoreProviderFactory.get(ZendeskProvidersModule_ProviderBlipsCoreProviderFactory.java:8)
   at dagger.internal.DoubleCheck.get(DoubleCheck.java:47)
   at zendesk.core.ZendeskApplicationModule_ProvideZendeskFactory.get(ZendeskApplicationModule_ProvideZendeskFactory.java:44)
   at zendesk.core.ZendeskApplicationModule_ProvideZendeskFactory.get(ZendeskApplicationModule_ProvideZendeskFactory.java:8)
   at dagger.internal.DoubleCheck.get(DoubleCheck.java:47)
   at zendesk.core.DaggerZendeskApplicationComponent.zendeskShadow(DaggerZendeskApplicationComponent.java:251)
   at zendesk.core.Zendesk.init(Zendesk.java:81)
   at zendesk.core.Zendesk.init(Zendesk.java:66)
   at com.myApplication.application.App.initializeZendeskSdk(App.java:161)
   at com.myApplication.application.App.onCreate(App.java:101)
   at com.myApplication.application.MyApp.onCreate(MyApp.java:35)
   at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1165)
   at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6074)
   at android.app.ActivityThread.access$1300(ActivityThread.java:207)
   at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1758)
   at android.os.Handler.dispatchMessage(Handler.java:106)
   at android.os.Looper.loop(Looper.java:193)
   at android.app.ActivityThread.main(ActivityThread.java:6898)
   at java.lang.reflect.Method.invoke(Method.java)
   at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:537)
   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)

【问题讨论】:

    标签: android crash okhttp firebase-remote-config zendesk


    【解决方案1】:

    问题在于,我的 firebase 远程配置有 3% 的时间初始化失败,并且不知何故它返回了 zendesk 主机 url 的空值。所以我将我的代码移动到远程配置完全初始化的地方,并将它放在 try/catch 块中,以避免应用程序崩溃以防万一。使用 Zendesk android SDK 5.0.1。

    private void initializeZendeskSdk() {
            try {
                Zendesk.INSTANCE.init(context, firebaseRemoteConfigManager.getZendeskHostUrl(),
                        firebaseRemoteConfigManager.getZendeskApplicationId(),
                        firebaseRemoteConfigManager.getZendeskOAuthClientId());
    
                Logger.setLoggable(true);
                Support.INSTANCE.init(Zendesk.INSTANCE);
            } catch (Exception e) {
                if (e.getMessage() != null)
                    FirebaseCrashlytics.getInstance().log(e.getMessage());
            }
        }
    

    【讨论】:

      猜你喜欢
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      • 2010-12-14
      • 1970-01-01
      • 2012-04-09
      • 2012-12-31
      • 2012-11-25
      • 1970-01-01
      相关资源
      最近更新 更多