You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As previously mentioned in issue #23058, Ionic does not support redirecting from tab1 → non-tab1 → non-tab2 → tab2. The reason given was that Ionic aims to mimic native tab behavior and does not allow programmatic navigation between different tabs.
Apart from this limitation, I am facing another issue: Suppose a user navigates to a non-tab2 page through the flow described above. If the user then puts the app in the background and later, on the web, clicks a link intended to open tab2, the navigation fails. From Ionic’s perspective, this action is treated as an attempt to programmatically push a new tab, which is not supported.
This behavior causes significant issues, breaking the app in multiple scenarios and making deep linking unreliable in production environments. The problem is identical to the one described in the previous issue.
Expected Behavior
After triggering a deep link, the app should navigate to and show the correct tab.
Steps to Reproduce
The reproduction steps are outlined in the previous issue. The only change is the addition of the App Capacitor plugin to listen for deep links. When a deep link event occurs, the plugin pushes the page in the same manner as the button in the old reproduction.
I attempted to modify the Ionic library to address the issue, but I was unable to resolve it, even when exposing and utilizing non-public methods like changeTab or resetTab. I understand the goal of closely matching native behavior, but this limitation presents a significant issue.
The text was updated successfully, but these errors were encountered:
Prerequisites
Ionic Framework Version
v8.x
Current Behavior
For more context, please refer to issue #23058.
As previously mentioned in issue #23058, Ionic does not support redirecting from
tab1 → non-tab1 → non-tab2 → tab2
. The reason given was that Ionic aims to mimic native tab behavior and does not allow programmatic navigation between different tabs.Apart from this limitation, I am facing another issue: Suppose a user navigates to a
non-tab2
page through the flow described above. If the user then puts the app in the background and later, on the web, clicks a link intended to opentab2
, the navigation fails. From Ionic’s perspective, this action is treated as an attempt to programmatically push a new tab, which is not supported.This behavior causes significant issues, breaking the app in multiple scenarios and making deep linking unreliable in production environments. The problem is identical to the one described in the previous issue.
Expected Behavior
After triggering a deep link, the app should navigate to and show the correct tab.
Steps to Reproduce
The reproduction steps are outlined in the previous issue. The only change is the addition of the App Capacitor plugin to listen for deep links. When a deep link event occurs, the plugin pushes the page in the same manner as the button in the old reproduction.
Code Reproduction URL
Ionic Info
Additional Information
I attempted to modify the Ionic library to address the issue, but I was unable to resolve it, even when exposing and utilizing non-public methods like
changeTab
orresetTab
. I understand the goal of closely matching native behavior, but this limitation presents a significant issue.The text was updated successfully, but these errors were encountered: