-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
AndroidInternalStoragePathHandler is crashing #1999
Comments
👋 @DougSig NOTE: This comment is auto-generated. Are you sure you have already searched for the same problem? Some people open new issues but they didn't search for something similar or for the same issue. Please, search for it using the GitHub issue search box or on the official inappwebview.dev website, or, also, using Google, StackOverflow, etc. before posting a new one. You may already find an answer to your problem! If this is really a new issue, then thank you for raising it. I will investigate it and get back to you as soon as possible. Please, make sure you have given me as much context as possible! Also, if you didn't already, post a code example that can replicate this issue. In the meantime, you can already search for some possible solutions online! Because this plugin uses native WebView, you can search online for the same issue adding Following these steps can save you, me, and other people a lot of time, thanks! |
Duplicate: #1980 |
Environment
Device information:
Google Pixel 4a
Description
Expected behavior:
App uses InternalStoragePathHandler successfully.
Current behavior:
Crash.
Steps to reproduce
Use the
InternalStoragePathHandler
on Android:There is a crash due to infinite recursion in the library:
https://github.com/pichillilorenzo/flutter_inappwebview/blame/751a104716b2c5158b5cad58347430d01965f00d/flutter_inappwebview_android/lib/src/webview_asset_loader.dart#L198
This was introduced in this PR.
Stacktrace/Logcat
Stacktrace/logcat is not informative, it just says that the InAppWebView widget crashed.
The text was updated successfully, but these errors were encountered: