Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Using capacitor plugins inside error page of supported web views #7373

Open
1 of 3 tasks
sabereen opened this issue Apr 1, 2024 · 0 comments · May be fixed by #6247
Open
1 of 3 tasks

[Bug]: Using capacitor plugins inside error page of supported web views #7373

sabereen opened this issue Apr 1, 2024 · 0 comments · May be fixed by #6247
Labels

Comments

@sabereen
Copy link

sabereen commented Apr 1, 2024

Capacitor Version

...

Other API Details

latest

Platforms Affected

  • iOS
  • Android
  • Web

Current Behavior

It is possible to display an alternative page to the user in case of errors now (Using server.errorPath field in capacitor.config). But we cannot use capacitor plugins on this page and we are limited. One of the reasons for displaying the error page is the old webview, which is not supported by the capacitor, and such a limitation is reasonable in this case. But it is not the only reason for displaying the error page.

For example, if the user's internet is disconnected while navigating to the remote site, the error page will be displayed. In this case, the webview is not old and we should not have restrictions on using capacitor plugins inside that page.

It is better to include a separate field for the old webview error page in the capacitor config (which is limited) and keep the current field as well.

Expected Behavior

I expect to be able to use capacitor plugins in the error page if the webview is not old.

Project Reproduction


Additional Information

related pull request:

#6247

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant