Issue Description
- I'm developing a hybrid iOS app and encountering WebView bridge communication issues after updating to Xcode 16 with iOS 18 SDK.
App Architecture
- AViewController: Initial view controller displayed at app launch
- Handles WebView setup and web-to-native bridge communication
- Pushes BViewController when receiving "B" bridge message from web
- BViewController: View controller stacked on top of AViewController
- Managed by navigation controller
- AViewController's WebView continues bridge communication even when BViewController is active
Problem Behavior
- Xcode 15 (iOS 18): WebView bridge communication in AViewController works normally while BViewController is active
- Xcode 16 (iOS 18 SDK): Server communication breaks or hangs without response while BViewController is active
- Communication resumes only after popping back to AViewController from BViewController
Questions
- Is the current architecture (configuring WebView in AViewController and maintaining bridge communication through AViewController's WebView while BViewController is presented) not a recommended pattern?
- Is Xcode 16's iOS 18 SDK the cause of this issue? If so, could you help me understand which specific changes are affecting this behavior?
This is urgent as we need to deploy soon. I would greatly appreciate a prompt response.