Otherwise all the xml, gradle, resources are identical (except the package and app name). The classes in these files are not used so I have no idea how they can be causing the crash. Now if I do the same in my main project, except don't delete the.
This then worked, I was even able to add in a lot of the code and get the google map to load. The provider functions were empty (save for the return value of 0/false/null/whatever), the application class just initialized Crashlyitcs and the Activity class was empty. java file except the Application, Activity and provider. Downloaded Crashlytics and it also did not catch the crash. So, does anyone have any idea on what I can do to solve this, or what tools I can use to catch whatever sort of errors happen so early in the apps lifecycle? If there is any code anyone wants to see just ask, but I'm unsure what exactly to post up since everything else was stripped out. The app also uses Google maps and a provider for search suggestions. I have pulled out all the code from the activity so the only thing that happens in code is that ACRA gets initialized in the derived Application class (note that the crash exists without ACRA). Can it be that whatever is going wrong is happening too early for ACRA to catch? I'm pretty sure I've set up ACRA correctly given that I've used it in several projects before and see nothing wrong this time. This time however, the app is crashing without any information from ACRA and so I'm not quite sure what is going wrong. With other apps I have developed, I have just set up ACRA in the project so I can still get debug information from a crash. The app was developed using Android Studio.
The tablet I'm using is a Tesco Hudl 2, which, although being a good quality low cost device, lacks adb drivers and so you can't debug apps through USB and get the Logcat data. I'm having a problem where an app I'm developing is working on mobile devices (tested on 4 different devices), but crashing when I try to test it on my tablet.
0 kommentar(er)
