iOS TestFlight build gets stuck after Agora engine initialization

### iOS TestFlight build gets stuck after Agora engine initialization

Hi,

I’m using the agora_rtc_package in my Flutter application for video calling functionality. Everything works perfectly in both debug and release modes when running directly on an iOS device. However, when I deploy the app to TestFlight, the video call stops responding right after the Agora engine initializes.

There are no visible errors in the logs — the engine initialization callback is triggered, but the app does not proceed further (e.g., joining a channel does not work, remote/local video does not render).

---

Environment Details:

• 
  

  Platform: iOS

  
  


• 
  

  Distribution: TestFlight

  
  


• 
  

  Flutter version: 3.32.5

  
  


• 
  

  agora_rtc_package version: 6.5.3

  
  


• 
  

  iOS version tested: 18.3

  
  

---

What I Have Tried:

• 
  

  Verified app permissions for Camera & Microphone

  
  


• 
  

  Checked capability settings (Background Modes, VoIP, etc.)

  
  


• 
  

  Rebuilt multiple times and re-uploaded to TestFlight

  
  


• 
  

  Works perfectly in debug and release when run locally

  
  

---

Issue Summary:

Please help me identify the cause or provide guidance if any additional configuration is needed specifically for TestFlight deployments.

Thanks! 🙏

### Platforms affected

- [ ] Android
- [x] iOS
- [ ] macOS
- [ ] Windows
- [ ] Web

### Steps to reproduce

1. Build the Flutter app using flutter build ipa (or via Xcode) with the agora_rtc_package integrated

2. Upload the generated IPA to App Store Connect

3. Install the app from TestFlight on an iOS device

4. Log in and start a video call flow

5. Observe the behavior after Agora engine initialization

### Expected results

Video call should proceed normally after Agora engine initializes, just like in debug/release local builds.

### Actual results

1. The app gets stuck immediately after the Agora engine initializes

2. Join channel or video rendering does not proceed

3. No error logs are shown in the console (TestFlight environment)