* Which was updated, the app or Android? (The app has not been updated to the production release since March)
* Are you able to see the script properly in the "Read" screen? I ask because the script is rendered for the "Read" screen and the "Write" screen using the same code. The PDF is generated by Android itself. If you updated Android and it stopped working, this may be a problem with Android, so it's good to know if you can see the document correctly.
* Are you able to print OTHER documents? Can you try creating a new script and copy and paste a test document to see if you can output it?
* FWIW, there was a new beta testing build posted a few days ago. Have you tried using that?
* As for the generated PDF, you said it is blank-- does it come out to the correct length? If you highlight text in it, is it there (that is, is it possible that it's somehow generating white-text-on-white-background?) or is the page short (one page) and blank? If it's blank with a single page, is it the correctly sized page?
* Do you have "Save as PDF" selected on the print preview screen? Are you able to see the script from that preview screen?
Answering these questions will help narrow down what the issue might be.
* I used app latest version for android (beta version).
* My android version latest version of android. I use poco F3 mobile phone.
* The problem start after i update the dubscript app.
*Yes, i can see the script on read mode. But when i convert to pdf file. It will become blank document.
* I try another document. Including document that can be converted to pdf before, and try new document to test . The result still same.
* Yes, the document become blank after convert to pdf files. But the length of document is same with the original fountain text on the reading mode. Including the pages.
* Sometimes i can see the text on the preview screen. But sometimes only blank pages. But, both of them still blank after save as/converted to pdf.
I need help please, i already support donate to dubscript. Because i love this app so much. And i used it everyday.
Thank you! This is VERY helpful information. It seems that something is wrong with Android's Webview to PDF conversion. You say that the problem occurred after an upgrade to DubScript and NOT an update to Android?
Because you can see the "Read" view, the problem does not appear to be the conversion.
Does it matter if you switch from the beta to the non beta or vice-versa?
Also- there was a report that if you turn on bolded scenes in the Settings that you can see only the scenes in the script in the PDF? As if non-bold text no longer works. Do you experience that?
If you put more of the script in bold (with the asterisk), are you able to see the bolded text?
A new thought-- perhaps this occurred with an update to the play store Webview component. The WebView component gets updated by Google occasionally via the Play store on most versions of Android, and if there is a new problem in WebView, it could be affecting DubScript.
Here is an experiment that you might try-- if you go to the Play Store, and then search for "Android System WebView", which should already be installed - this component contains some of the code that is used to convert to PDF. As I mentioned, It gets updated regularly by Google-- but perhaps they added something recently that is breaking the PDF conversion (?)
Maybe as an experiment try "Uninstall"ing any updates (I don't think Android will let you fully uninstall it, only uninstall the UPDATES- you probably don't want to uninstall it entirely because lots of programs use the WebView component). But if you're able to uninstall the updates only, then go to DubScript and try the PDF conversion again. If it works (or-- if it doesn't), be sure to go back to the Play Store and tell it to re-update the Android System Webview to be up to date again.
Try this at your own risk, because those updates are supposed to give your WebView the latest bugfixes and security updates... but it's a good way to test if maybe the problem was an update by google there? Before you do this, definitely make an off-site backup of your scripts and anything else. I don't anticipate any issues, but better to be over-cautious.
If removing updates to Android System WebView DOES eliminate the problem, it will tell us that it's the Android System WebView that introduced the issue, and hopefully it means they will introduce a fix soon!
Another experiment might be to-- instead of uninstalling new updates, to instead try the latest beta (open release) version of the Android System Webview. maybe the fix is in a newer version (rather than going back to an older one).
If you feel brave and want to try this, please post the results! Just again, be sure to back up everything first, which is always good practice, generally speaking.
Update: This very well may be a bug with the WebView component, particularly version 102.0.5005.78.
See here and here.
I am very curious as to whether this is fixed by reverting to an older version. It appears that a fix is on the way.
Note this only affects some devices (none of mine) so looking for any confirmation here!'
Thanks.
A few questions-- * What…
A few questions--
* What version of the App are you using?
* What version of Android?
* Which was updated, the app or Android? (The app has not been updated to the production release since March)
* Are you able to see the script properly in the "Read" screen? I ask because the script is rendered for the "Read" screen and the "Write" screen using the same code. The PDF is generated by Android itself. If you updated Android and it stopped working, this may be a problem with Android, so it's good to know if you can see the document correctly.
* Are you able to print OTHER documents? Can you try creating a new script and copy and paste a test document to see if you can output it?
* FWIW, there was a new beta testing build posted a few days ago. Have you tried using that?
* As for the generated PDF, you said it is blank-- does it come out to the correct length? If you highlight text in it, is it there (that is, is it possible that it's somehow generating white-text-on-white-background?) or is the page short (one page) and blank? If it's blank with a single page, is it the correctly sized page?
* Do you have "Save as PDF" selected on the print preview screen? Are you able to see the script from that preview screen?
Answering these questions will help narrow down what the issue might be.
Thanks!
Okey, i will answer all…
Okey, i will answer all those questions:
* I used app latest version for android (beta version).
* My android version latest version of android. I use poco F3 mobile phone.
* The problem start after i update the dubscript app.
*Yes, i can see the script on read mode. But when i convert to pdf file. It will become blank document.
* I try another document. Including document that can be converted to pdf before, and try new document to test . The result still same.
* Yes, the document become blank after convert to pdf files. But the length of document is same with the original fountain text on the reading mode. Including the pages.
* Sometimes i can see the text on the preview screen. But sometimes only blank pages. But, both of them still blank after save as/converted to pdf.
I need help please, i already support donate to dubscript. Because i love this app so much. And i used it everyday.
An experiment....
Thank you! This is VERY helpful information. It seems that something is wrong with Android's Webview to PDF conversion. You say that the problem occurred after an upgrade to DubScript and NOT an update to Android?
Because you can see the "Read" view, the problem does not appear to be the conversion.
Does it matter if you switch from the beta to the non beta or vice-versa?
Also- there was a report that if you turn on bolded scenes in the Settings that you can see only the scenes in the script in the PDF? As if non-bold text no longer works. Do you experience that?
If you put more of the script in bold (with the asterisk), are you able to see the bolded text?
A new thought-- perhaps this occurred with an update to the play store Webview component. The WebView component gets updated by Google occasionally via the Play store on most versions of Android, and if there is a new problem in WebView, it could be affecting DubScript.
Here is an experiment that you might try-- if you go to the Play Store, and then search for "Android System WebView", which should already be installed - this component contains some of the code that is used to convert to PDF. As I mentioned, It gets updated regularly by Google-- but perhaps they added something recently that is breaking the PDF conversion (?)
Maybe as an experiment try "Uninstall"ing any updates (I don't think Android will let you fully uninstall it, only uninstall the UPDATES- you probably don't want to uninstall it entirely because lots of programs use the WebView component). But if you're able to uninstall the updates only, then go to DubScript and try the PDF conversion again. If it works (or-- if it doesn't), be sure to go back to the Play Store and tell it to re-update the Android System Webview to be up to date again.
Try this at your own risk, because those updates are supposed to give your WebView the latest bugfixes and security updates... but it's a good way to test if maybe the problem was an update by google there? Before you do this, definitely make an off-site backup of your scripts and anything else. I don't anticipate any issues, but better to be over-cautious.
If removing updates to Android System WebView DOES eliminate the problem, it will tell us that it's the Android System WebView that introduced the issue, and hopefully it means they will introduce a fix soon!
Another experiment might be to-- instead of uninstalling new updates, to instead try the latest beta (open release) version of the Android System Webview. maybe the fix is in a newer version (rather than going back to an older one).
If you feel brave and want to try this, please post the results! Just again, be sure to back up everything first, which is always good practice, generally speaking.
Thanks!
Update: This very well may…