Swift无法找到框架私有结构体及liblinphone中LinphoneCallParams未声明问题

1. Can't Locate Private Structs Defined in a Framework #

Private structs in Swift (marked with private access control) are intentionally hidden from outside their parent module, which is why you can't access them. Here's how to fix this based on whether it's your own framework or a third-party one:

• If it's your custom framework:

  • Adjust the struct's access control level. Swap private struct YourStruct { ... } for internal struct YourStruct { ... } (default access, visible within the framework) or public struct YourStruct { ... } (visible outside the framework).
  • Make sure any properties/methods inside the struct that you need to access also have non-private access levels (like internal or public).

• If it's a third-party framework:

  • Check the framework's docs or header files first—there’s almost always a public API that wraps the private struct’s functionality. Reliable frameworks don’t lock core features behind private types.
  • If you absolutely need direct access, you could use Objective-C bridging to bypass Swift’s access controls (since Objective-C is looser with private symbols), but this is risky—it can break if the framework updates.

2. "Use of undeclared type 'LinphoneCallParams'" Error with liblinphone #

The root issue here is that LinphoneCallParams is an opaque C struct—it’s defined as typedef struct _LinphoneCallParams LinphoneCallParams; without exposing its concrete implementation in the header. Swift doesn’t auto-import these opaque structs as native types; instead, you need to handle them as pointers. Here’s how to fix it:

• Use OpaquePointer instead of the struct type:
  In your Swift code, declare the variable like this:

  var callPara: OpaquePointer?
  

  You’ll then use liblinphone’s C APIs to manage this pointer—functions like linphone_call_params_new() or linphone_call_params_set_audio_enabled() will take/return OpaquePointer instances.

• Double-check your bridging header imports:
  Make sure your bridging header includes the full liblinphone header that defines LinphoneCallParams:

  #import <linphone/linphone.h>
  // Or specifically:
  #import <linphone/types.h>
  

  Partial imports can cause Swift to miss certain type definitions.

• Check for liblinphone's Swift support:
  Some versions of liblinphone provide an official Swift wrapper or module map. If available, using this instead of manual bridging will resolve type issues automatically. Look for a .swiftmodule file in the framework or check if there’s a CocoaPods/Carthage package with Swift support.

内容的提问来源于stack exchange，提问作者Angus