我在Xcode 9中编译应用程序时出现BoringSSL错误

时间:2022-10-06 09:39:46

I made an App with "Google Firebase" as my back-end.

我用“Google Firebase”作为我的后端制作了一个应用程序。

I want my App to be able to send push notifications, and actually, I have all setted up, however, when I compile my App, it builds perfectly and without errors and warnings, but in the console, this error appears:

我希望我的应用程序能够发送推送通知,实际上,我已经完成了所有设置,但是,当我编译我的应用程序时,它构建完美且没有错误和警告,但在控制台中,出现此错误:

[BoringSSL] Function boringssl_context_get_peer_sct_list: line 1754 received sct extension length is less than sct data length

[BoringSSL]函数boringssl_context_get_peer_sct_list:第1754行收到的sct扩展长度小于sct数据长度

And then, I send a push notification from "Google Firebase" to my app, but it never recieves it. I don't know how to handle this error. Has anyone had the same issue?

然后,我将“Google Firebase”的推送通知发送到我的应用,但它从未收到过。我不知道如何处理这个错误。有没有人有同样的问题?

I'm using Xcode 9 GM Seed / Build: 9A235. My device is an iPhone 6 with iOS 11.

我正在使用Xcode 9 GM Seed / Build:9A235。我的设备是带有iOS 11的iPhone 6。

Here I leave the complete sentence that appears in the console, appart from the error:

在这里,我留下出现在控制台中的完整句子,appart来自错误:

2017-09-14 09:39:17.042434+0200 pushApp[288:15360] [Firebase/Analytics][I-ACS023007] Firebase Analytics v.40003000 started
2017-09-14 09:39:17.111 pushApp[288] <Notice> [Firebase/Analytics][I-ACS023007] Firebase Analytics v.40003000 started
2017-09-14 09:39:17.111336+0200 pushApp[288:15360] [Firebase/Analytics][I-ACS023008] To enable debug logging set the following application argument: -FIRAnalyticsDebugEnabled (see http://goo .gl/RfcP7r)
2017-09-14 09:39:17.113 pushApp[288] <Notice> [Firebase/Analytics][I-ACS023008] To enable debug logging set the following application argument: -FIRAnalyticsDebugEnabled (see http://goo .gl/RfcP7r)
2017-09-14 09:39:17.249119+0200 pushApp[288:15366] [BoringSSL] Function boringssl_context_get_peer_sct_list: line 1754 received sct extension length is less than sct data length
Token: diArDpk_ugc:APA91bEEhAnZJlSr8nGUyGqGn8bSbxD3VpGAbIMoCLREBqeD2bkQcOVlpZJecc5g0ptosLtxpVOqboeIKiX7odWf28p551f0m1G_no-sAmNzXKAgSIM4nOtkNJJCMWJO1LJ6ItsYlgX2
2017-09-14 09:39:17.287687+0200 pushApp[288:15271] refreshPreferences: HangTracerEnabled: 1
2017-09-14 09:39:17.287784+0200 pushApp[288:15271] refreshPreferences: HangTracerDuration: 500
2017-09-14 09:39:17.287825+0200 pushApp[288:15271] refreshPreferences: ActivationLoggingEnabled: 0 ActivationLoggingTaskedOffByDA:0
2017-09-14 09:39:17.393859+0200 pushApp[288:15371] TIC Read Status [1:0x0]: 1:57
2017-09-14 09:39:17.394711+0200 pushApp[288:15371] TIC Read Status [1:0x0]: 1:57
2017-09-14 09:40:40.132473+0200 pushApp[288:15751] TIC Read Status [2:0x0]: 1:57
2017-09-14 09:40:40.132573+0200 pushApp[288:15751] TIC Read Status [2:0x0]: 1:57

1 个解决方案

#1


2  

Fix in the latest versions of Firebase, FirebaseMessaging and FirebaseInstanceID check this comments here and the last here

修复了最新版本的Firebase,FirebaseMessaging和FirebaseInstanceID,请在此处查看此评论

You should try to update your pods

您应该尝试更新您的pod

#1


2  

Fix in the latest versions of Firebase, FirebaseMessaging and FirebaseInstanceID check this comments here and the last here

修复了最新版本的Firebase,FirebaseMessaging和FirebaseInstanceID,请在此处查看此评论

You should try to update your pods

您应该尝试更新您的pod