Adobe Acrobat Reader DC app. is designed for mobile devices, I am not sure is a external keyboard will be supported, in most of the case it works but in some cases the drivers of the external device accessories might interrupt the application functioning due to which it might crash.
Have you tried uninstalling & reinstalling the application, make sure that you take a backup of you work before uninstalling the app.
I've tried un/re-installing and it didn't work. my issue is that crashes while i'm working, so backing up is kind of redundant. What else can i do?
Thanks for sharing the crash logs.
1 person found this helpful
I can give indirect solution
Before roughly coming to the solution detect the problem as to where the problem occuring by viewing the code. If you have already published your app, Android vitals can help make you aware of the problem.
Android vitals can help improve your app's performance by alerting you, via the Play Console, when your app is exhibiting excessive crashes. Android vitals considers crashes excessive when an app:having 1 crash in atleast 1.09% of its daily sessions,or having 2 or more crashes in at least 0.18% of its daily sessions.
A daily session refers to a day in which your app was used. For information on how Google Play collects Android vitals data, see the Play Console documentation.After you learn that your app is suffering from too many crashes, the next step is to diagnose them.
Diagnose the crashes i am answering this from the android training, i hadSolving crashes can be difficult. However, if you can identify the root cause of the crash, most likely you can find a solution to it.There are many situations that can cause a crash in your app. Some reasons are obvious, like checking for a null value or empty string, but others are more subtle, like passing invalid arguments to an API or even complex multithreaded interactions.
Reading a stack trace
The first step to fix a crash is to identify the place where it happens. You can see use the stack stack trace available in the report details if you are using Play Console or the output of the logcat tool. If you don’t have a stack trace available, you should locally reproduce the crash either by manually testing the app or reaching out to affected users, and reproduce it while using logcat.
i am answering this from the android training, i had