libwebrtc | A build script of WebRTC library from Chromium | SDK library

Some of the libraries to link may not be built with the same toolchain. You can check with objdump.

Example (The "file format" may not be the exact result in your case):

I was able to fix all the issues related to linking built libwebrtc.a and the built executable works.

Could someone tell me other way to debug errors 1,2 and 3 as the symbols are there in libwebrtc.a

Was using cxx_std_17 and the required was cxx_std_14

The issue lies in usage of cxx_std_17. In the code that I was building has used certain methods which were not available with default cxx_std_11 so I just used cxx_std_17 but it caused a lot of issues with libwebrtc.a. Even though webrtc style guide says that the code is valid c++17 but faced issues. In the same style guide it's mentioned that webrtc code is written is c++14 and that gave me idea to switch to cxx_std_14 and the errors resolved. As mentioned in same webrtc style guide that "Some older parts of the code violate the style guide in various ways." so I think some older code is there which caused the errors

What could be the reason that linker error 1 and 3 refer to .cpp file opposed to .o file as in error 2

I think the reason behind .cpp or .o is that if error originated in my code then it shows .cpp but if it's in 3rd party library, as was the case with a few linker errors which originated from libwebrtc.a, then it shows the error in .o file as the library only has compiled files

how to find ninja target for webrtc build to resolve error 4's undefined reference?

Issue was with the commit I was trying to build.

From webrtc release notes I found out the stable m77 branch head commit and found out the commit I was using didn't have the functions the linker error was referring to but the head commit of stable m77 branch have those functions.

NOTE: In general to get the target which has the .o file with the required symbol we just need to do grep and it will list out where the symbol related function is defined and ninja -t targets all will display all the targets. So just go to corresponding .ninja file and copy all the .o files to the webrtc.ninja and build the libwebrtc.a again.

So @sharkyenergy found the real bug! I am placing his solution above my suggestions:

"I developed on windows, but due to the pinch/zoom problem, i had to move to a mac. I didnt know that on mac you must add every nuget package to the .ios project too, while on windows they are shared. after adding all the packages it didnt crash anymore."

If his solution doesn't work for you, you can try the following below the line:

Things you can try,

1. While creating the archive, we use the Release-iPhone config, which is different from the Release-iPhone Simulator config. So when you are testing, you may not be testing the ACTUAL configuration. To check this, open the iOS Project Options in Visual Studio and compare all the settings to be the same (particularly the Linker behavior). Then test it on the simulator again and it could catch the error.

2. Occasionally your app can crash on launch in prod only, and the Microsoft AppCenter package can help you with this for free. Here's something you can add in the AppDelegate just when your FinishedLaunching function begins:

So what I basically did was this:

• renamed the folder to libwebrtcx

• renamed the project