How to eliminate boringssl log warning?

Developer Tools & Services Xcode
habeebmhd2020 OP
Created
Replies 5
Boosts 2
Views 15k
Participants 5

I built a currency converter app, which gets the live currency value through API and display it.

Testing on a physical phone my app works fine & no crash.

But whenever I do API call I am getting warning in the simulator as below:

[boringssl] boringssl_metrics_log_metric_block_invoke(144) Failed to log metrics

I have tried changing some values but nothing works

  • OS_ACTIVITY_MODE = default
  • DEBUG_ACTIVITY_MODE -> Debug -> any iOS simulator SDK = default

here my doubts are:

  1. How to eliminate this warning?
  2. Can I just ignore this warning?
  3. Will Apple accept my app with this warning?
Answered by habeebmhd2020 in 701999022

I got some relevant answer from stack overflow and it helped me something.

Let me share here, If we run the app on physical device with Xcode simulator we don't get any issue and boringssl log warning also on Xcode simulator. This issue might be because of Xcode couldn't able to connect to internet when running the app or call API.

Hope this answer help someone!

Replies  5
Boosts 2
Views  15k
Participants  5
habeebmhd2020 OP

Here how I used URLSession ` let session = URLSession(configuration: .default)

            let task = session.dataTask(with: url) {(data, response, error) in
pittsylvania OP

I get this problem as soon as my app starts, no API call is even made. Depressing, as nothing is worse than consoleLog filling up with stuff and developer having zero clue if its leading to OTHER problems in the app.
habeebmhd2020 OP
Accepted Answer

I got some relevant answer from stack overflow and it helped me something.

Let me share here, If we run the app on physical device with Xcode simulator we don't get any issue and boringssl log warning also on Xcode simulator. This issue might be because of Xcode couldn't able to connect to internet when running the app or call API.

Hope this answer help someone!
AnnArborMark OP
Accepted Answer

This is answered here, to some extent: https://stackoverflow.com/questions/44410572/failed-to-register-for-boringssl-log-debug-updates
habeebmhd2020 OP

it was accidentally marked as right answer. 

@ AnnArborMark This is not the soultion and I have mentioned in my question itself that I tried it before which was not working to resolve the issue.