fix: Select conversation issue on iOS #71
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On Android, the Zendesk messaging view worked as expected because it was displayed as part of the regular screen flow. On iOS, using rootController.show(viewController, sender: self) pushed the Zendesk view onto the navigation stack. However, the Zendesk view was just a single screen, and there was no deeper navigation (i.e., tapping on a conversation to open a detailed view), so the interaction issues didn't appear. After the update that introduced multi-conversation support, where tapping on a conversation opens a deeper screen, the previous approach caused issues because the Zendesk view was not properly integrated into the app's navigation stack. This prevented the deeper navigation from functioning correctly (e.g., tapping on a conversation didn't lead to a new screen).
Solution:
navigation (e.g., tapping on a conversation now pushes a new screen).
This fix resolves the interaction issue by ensuring the Zendesk view is correctly integrated into the app’s navigation stack, enabling the deeper screen navigation introduced by the multi-conversation update and providing a smooth user experience.