Jenser Almeida

Results 19 comments of Jenser Almeida

> What about iOS? iOS has a different model for the file system, where we do not share files between applications, without using the Share option. Besides that, the lines...

I think we should change the iOS behavior and deduplicate the file name also. I'll work on the objective-C and push an update anytime next week. I do agree also...

Sorry, for the first question, about what happens to Android when the file name already exists, the answer is, the download fails, without any reasonable feedback. Please, look into the...

Hi @IlyaMax, I can take a look into it, and as I did not write it on Objective-C yet, and @bartekpacia feels that it does fit as a safe option...

Same here. We went down from an almost crash-free app to a couple of hundreds of daily crashes. The dent on the below graph was the rollout of a new...

Hi, I have some additional information to share. I have reverted the InAppWebView back from version 5.4.3 to 5.3.2, and the issue with the [WebKit::CompletionHandlerCallChecker::~CompletionHandlerCallChecker()] is still happening. For context,...

> The "problematic" events seem to be: > > * [webView(_:decidePolicyFor:preferences:decisionHandler:)](https://developer.apple.com/documentation/webkit/wknavigationdelegate/3223382-webview) > * [webView(_:didReceive:completionHandler:)](https://developer.apple.com/documentation/webkit/wknavigationdelegate/1455638-webview) > > I did some tests and checked again the native code but I can't find...

> @jenseralmeida which version of Flutter are you using right now? Have you tried to upgrade to the latest one? @pichillilorenzo , currently the application is running on flutter v3.0.5...

The new crashing report after upgrading to 5.5.0+4. Thanks to the team ≈for your awesome work. For context, check https://github.com/pichillilorenzo/flutter_inappwebview/issues/1221#issuecomment-1242406861 ![image](https://user-images.githubusercontent.com/660075/201191249-8f6bdf1f-bd68-4e8e-b224-0d47499d7c28.png) cc @pichillilorenzo

The issue happens while expanding the branch tree of a specific repository on a large workspace. It was fine last week, and I am assuming that this is a v12.2...