BoringSSL Error when I compile my App in Xcode 9

I’d like to clarify the overall flow of your app. It seems that you have two things in play:

• Someone is making an outgoing TLS connection, which is what’s generated the

  boringssl_context_get_peer_sct_list

  log message you’re worried about.

• You’re having problems sending push notifications to your app.

How are these related? You wrote:

And then, I send a push notification from "Google Firebase" to my app, but it never recieves it.

Are you sending the push from within your app? Or from a management console? If it’s the latter than your app’s inability to make outgoing TLS connections doesn’t seem like it’d be related.

Regardless, if you want to find out what’s going on with the

boringssl_context_get_peer_sct_list

Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

Well met Eskimo,

About your points:

Someone is making an outgoing TLS connection, which is what’s generated the

boringssl_context_get_peer_sct_list

Yes, I'm doing a TLS connection using Google's Firebase Cloud Messaging tool.

I got everything setted up. I have all of the certificates both in back-end and front-end well configured, and if I go to my App in Xcode and I go to "Capabilities", I have the "Notifications" Switch turned to "ON" and all of those two steps are correctly checked:

✅Add the Push Notifications feature to your App ID.

✅Add the Push Notifications entitlement to your entitlements file.

And this is the code I have on my "AppDelegate.swift" file:

import UIKit
import Firebase
import UserNotifications


@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate, UNUserNotificationCenterDelegate {


    var window: UIWindow?


    func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions:[UIApplicationLaunchOptionsKey: Any]?) -> Bool {
     
        // Override point for customization after application launch.
        FirebaseApp.configure()
     
        // For iOS 11 display notification (sent via APNS)
        UNUserNotificationCenter.current().delegate = self
     
        let authOptions: UNAuthorizationOptions = [.alert, .badge, .sound]
        UNUserNotificationCenter.current().requestAuthorization(
            options: authOptions,
            completionHandler: {_, _ in })
     
        application.registerForRemoteNotifications()
     
        if let token = InstanceID.instanceID().token() {
            print ("Token: \(token)")
        }
     
        return true
    }

Sincerely, I don't know what I'm missing.

Are you sending the push from within your app? Or from a management console? If it’s the latter than your app’s inability to make outgoing TLS connections doesn’t seem like it’d be related.

I'm sending a push notification from my Google's Firebase console.

Regardless, if you want to find out what’s going on with the

boringssl_context_get_peer_sct_list

How can I do that backtracking? To be sincere, I'm a completely novice with Xcode 9 & Swift 4.

Best Regards,

Gerard Riera Puig.

How can I do that backtracking?

One option would be to set a symbolic breakpoint on

boringssl_context_get_peer_sct_list

com.apple.CFNetwork.Connection

At that point it’s a ‘simple’ matter of tracking down who issued that request. If this were your own code it’d be pretty obvious:

1. Look for the code issuing the request

2. Set a breakpoint on the completion handler (or completion delegate callback)

3. If that indicates an error, you have something concrete to investigate

However, it’s most likely that this is Firebase code. I’m not familiar with that, so I don’t have any specific suggestions here.

Finally, I should stress that the message you’re seeing could be a complete red herring. The TLS client is having problems parsing the SCT (Signed Certificate Timestamps) extension, which is a part of the Certificate Transparency feature. That failure does not necessarily mean that the entire TLS connection is going to fail. Right now Certificate Transparency is an opt-in feature.

Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

Well met Eskimo,

With the newest release of Xcode 9, this error (BoringSSL), doesn't appear anymore, and I still can't recieve push notifications, therefore you were right. That BoringSSL error had nothing to do with my app being unable to recieve push notifications.

I will look back to my code and configuration.

Thank you very much for you help and support.

I consider this post closed.

Best Regards,

Gerard Riera Puig.