如何在Objective-C中使用CallKit？求入门指导及示例建议

Hey there! Since you already have a solid grasp of CallKit concepts from WWDC sessions, you're already ahead of the curve—let's get you started with actual development, and tackle that Swift-only SpeakerBox example issue too.

Don't jump straight into the complex SpeakerBox example first. Start with a tiny, functional demo to get your feet wet:

• Set up the basics:

  1. Import the CallKit framework:
     • For Swift: import CallKit
     • For Objective-C: #import <CallKit/CallKit.h>
  2. Initialize a CXProvider with a basic configuration (set your app name, supported call types like audio/video):

     let configuration = CXProviderConfiguration(localizedName: "MyCallApp")
     configuration.supportsVideo = true
     let provider = CXProvider(configuration: configuration)
     

     (Translate this to Objective-C by using CXProviderConfiguration and [[CXProvider alloc] initWithConfiguration:configuration]; if that's your preferred language)
  3. Implement the core CXProviderDelegate methods, starting with the essentials like provider:performAnswerCallAction: (for answering calls) and provider:performEndCallAction: (for ending calls). These are where you'll hook up your actual call logic (even if it's just a placeholder at first).
  4. Use CXCallController to trigger a simulated incoming call, so you can see CallKit's system UI pop up and test your delegate methods.

• Dissect SpeakerBox incrementally: Even though it's Swift, you can map each component to your target language. For example, the CallManager class in SpeakerBox handles call state tracking—replicate that logic in Objective-C by creating a similar manager class. Go through each file line by line, translate the logic, and build out pieces one by one instead of trying to port the whole thing at once.

If you're looking for non-Swift starting points or simpler demos:

• Build your own Objective-C equivalent of SpeakerBox: Focus on the core modules first:
  • A call manager to track active calls
  • A CXProviderDelegate implementation to handle system callbacks
  • CXCallController usage to initiate/respond to call requests
    This is actually a great exercise because it forces you to understand every part of the CallKit flow, instead of just copying code.
• Leverage official Objective-C code snippets: Apple's CallKit documentation includes plenty of Objective-C examples for key APIs (like setting up providers, handling call actions). Grab those snippets, drop them into a test project, and tweak them to fit your needs.
• Simplified third-party demos: Look for community-built Objective-C CallKit demos—many developers have shared minimal working examples that focus on the core functionality without the extra complexity of SpeakerBox.

• Use Xcode's built-in CallKit simulator: Go to Debug > Simulate Incoming Call to test incoming calls quickly on the simulator, no real phone needed.
• Focus on core objects first: Make sure you understand the roles of CXProvider (communicates with the system), CXCallController (sends call requests to the system), and CXCallUpdate (updates call state) before adding extra features.
• Don't forget audio permissions: If your app handles actual call audio, you'll need to request microphone access—add NSMicrophoneUsageDescription to your Info.plist with a clear explanation.

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