We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
On Real iOS devices, the await html.ToPdfAsync call doens't return 100% of the time and freeze the UI main thread On Android it works.
the called Task must return
it doesn't return 100% of the time.
try { if (Forms9Patch.ToPdfService.IsAvailable) { if (await htmlfile.ToPdfAsync(ReportFileName, PageSize.IsoA4) is ToFileResult pdfResult) { if (pdfResult.IsError) { await _userDialogs.AlertAsync(AppResources.StrReportGenerationError + pdfResult.Result); } else { await Launcher.OpenAsync(new OpenFileRequest { Title = AppResources.OpenWithString, File = new ReadOnlyFile(pdfResult.Result) }); } } } else { await _userDialogs.AlertAsync(AppResources.StrPdfNonDisponibile); } } catch (Exception err) { await _userDialogs.AlertAsync(AppResources.StrReportGenerationError + err); }
The text was updated successfully, but these errors were encountered:
I have very similar issue with the Android - nothing happens. Investigating.
Sorry, something went wrong.
Okay, here's the fix that I made:
That resolved the 'doing nothing' problem. Apparently, Webkit's WebView MUST be initialized on the main thread.
FYI - the same problem was on both Android and iOS, so you will have to make changes in the both of ToPDF() implementations.
No branches or pull requests
Description
On Real iOS devices, the await html.ToPdfAsync call doens't return 100% of the time and freeze the UI main thread
On Android it works.
Steps to Reproduce
Expected Behavior
the called Task must return
Actual Behavior
it doesn't return 100% of the time.
Basic Information
Screenshots
Reproduction Link - a link to a small demo project that reproduces this issue
Workaround
The text was updated successfully, but these errors were encountered: