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.
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
In my app, I want to launch Apple Maps and start turn-by-turn navigation when the user taps a button.
I referred to Apple’s documentation and sample projects and implemented the following code:
if let url = URL(string: "maps://?t=m&daddr=(addr)") {
self.carplayScene?.open(url, options: nil, completionHandler: nil)
}
This works only if Apple Maps has been launched at least once on the iPhone or in the CarPlay environment.
If Apple Maps has never been opened before, it launches the app but does not automatically start navigation.
However, once the user has opened Apple Maps at least once — either on the phone or through CarPlay — then navigation starts as expected from that point on.
Is this behavior expected? Or is it a bug?
I'm using CPListItem like this:
CPListItem(
text: "test",
detailText: "test",
image: nil,
accessoryImage: nil,
accessoryType: .none
)
However, when I tap the item in the list, a loading indicator appears on the right side, as shown in the image I attached. I didn’t configure anything that should cause this behavior.
Why is the loading indicator shown by default when tapping a list item?
Is there a way to prevent it from appearing?
I'm developing a CarPlay Fueling app with CarPlay entitlement properly configured. While testing, I ran into two issues and would appreciate any guidance:
UserDefaults access while iPhone is locked:
In my CarPlay implementation, I read values from UserDefaults that were previously saved in the iOS app. However, when the iPhone is locked and the CarPlay session is active, it seems that the CarPlay extension cannot read the stored values. Is this the expected behavior? If so, how can I persist and access data across the app and CarPlay reliably?
API calls while iPhone is locked:
The CarPlay interface in my app communicates with a server to display lists and detail views. When the iPhone is locked, are network calls still allowed from the CarPlay extension?
Currently, I do not have any background modes enabled in the app capabilities.
If I enable background modes and implement background network logic to ensure API calls complete properly, would this be considered acceptable usage for CarPlay in App Store review? Or could it raise any rejection concerns during the approval process?
Thanks in advance for your help.
I'm trying to implement a custom back button in a CPInformationTemplate using CPBarButton. It works as expected on iOS 18 — the button appears in the navigation bar and correctly pops the template when tapped.
However, on iOS 16 devices, the custom back button does not respond to taps at all.
The reason I need a custom back button is because I want to perform cleanup and reset logic before popping the template.
Is there any workaround for making this work on iOS 16? Or is there a recommended way to hook into the system back button behavior so that I can execute code when the template is dismissed?
I am currently developing a CarPlay application using CPPointOfInterestTemplate.
I am displaying a list of restaurants on a map, and when a user taps on a restaurant in the list, I present a detail view using CPPointOfInterest.
The list of restaurants is updated based on the user's location changes using the setPointsOfInterest method.
Is there a way to detect when they press the close button (typically an "X" button) to dismiss the detail view and return to the list?
Is there a delegate method or any other mechanism to determine whether the CPPointOfInterestTemplate is currently displaying the list of points of interest or the detail view of a specific point of interest? I need to know this so that I can avoid updating the list based on location changes when the detail view is being shown.
My current implementation updates the list of restaurants whenever the user's location changes. This works well when the user is Browse the list. However, if the user has navigated to the detail view of a restaurant, a location update currently causes the list to reload, which results in the detail view being dismissed and the user being taken back to the list. I would like to prevent this from happening and only update the list when the list view is visible.