Open britsy83 opened 19 hours ago
Probably it could be related on web caching and not related to this plugin. You can try to set the cache mode, for example on Android you can set a custom InAppWebView cache mode setting: https://pub.dev/documentation/flutter_inappwebview/latest/flutter_inappwebview/InAppWebViewSettings/cacheMode.html and for iOS you can try to set the URLRequest cache Policy parameter: https://pub.dev/documentation/flutter_inappwebview/latest/flutter_inappwebview/URLRequest/cachePolicy.html
In any case, you should use an API (REST or whatever) to do what you are doing here for best performance. If there isn’t any API available other then doing web scraping, then you should expect possible delays as you are loading a full web page under the hood, with all assets etc.
Thanks for the quick feedback. Unfortunately, there is no API so web scraping is my only option. The performance is not bad overall, except as I said when I initiate the web view for the first time.
Sorry for my ignorance, but where am I supposed to set this cache mode?
Thanks!
On Oct 20, 2024, at 11:52 AM, Lorenzo Pichilli @.***> wrote:
Probably it could be related on web caching and not related to this plugin. You can try to set the cache mode, for example on Android you can set a custom InAppWebView cache mode setting: https://pub.dev/documentation/flutter_inappwebview/latest/flutter_inappwebview/InAppWebViewSettings/cacheMode.html and for iOS you can try to set the URLRequest cache Policy parameter: https://pub.dev/documentation/flutter_inappwebview/latest/flutter_inappwebview/URLRequest/cachePolicy.html
In any case, you should use an API (REST or whatever) to do what you are doing here for best performance. If there isn’t any API available other then doing web scraping, then you should expect possible delays as you are loading a full web page under the hood, with all assets etc.
— Reply to this email directly, view it on GitHub https://github.com/pichillilorenzo/flutter_inappwebview/issues/2361#issuecomment-2425059991, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWYTRFXW3CZUQFJ23OEJTVTZ4PGVJAVCNFSM6AAAAABQIT3F2CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRVGA2TSOJZGE. You are receiving this because you authored the thread.
Is there an existing issue for this?
Current Behavior
I am using a headless inappwebview in my Flutterflow application. Upon the first call to the headless webview (after a new app launch for example), the process is much longer than the subsequent requests and I cannot figure out why.
Expected Behavior
I am expecting the plugin to have a more constant performance.
Steps with code example to reproduce
Steps with code example to reproduce
```dart // Automatic FlutterFlow imports import '/backend/backend.dart'; import '/actions/actions.dart' as action_blocks; import '/flutter_flow/flutter_flow_theme.dart'; import '/flutter_flow/flutter_flow_util.dart'; import '/custom_code/actions/index.dart'; // Imports other custom actions import '/flutter_flow/custom_functions.dart'; // Imports custom functions import 'package:flutter/material.dart'; // Begin custom action code // DO NOT REMOVE OR MODIFY THE CODE ABOVE! import 'package:flutter_inappwebview/flutter_inappwebview.dart'; import 'dart:async'; FutureStacktrace/Logs
Stacktrace/Logs
```Flutter version
v3.22.0
Operating System, Device-specific and/or Tool
iOS
Plugin version
v6.1.5
Additional information
No response
Self grab