I have an app with many downloads and good reviews, but yesterday I got one 1-star review of someone. He said my app won't start on his specific device. I don't own that device. So what can I do to find out what causes the error?
I know I can see crash reports in the Google developer console, but that was just a review. I can still see what device he owns and want to improve my app that he would be satisfied and can start the app. What possibilites do I have?
Depending on the device it might be availible on Amazons device farm. It will save you from having to buy the device and you're able to build tests on the platform to fit into your workflow.
List of current devices
Use BlueStack for testing. Make an android AVD having version that is causing the crash and then find the errors in it
use emulater,
there are so many emulators available in android studio.
Genymotion.
BlueStacks
Droid4X
Windroy
Related
I started learning android and I'm learning from the book Head First Android Development. In each chapter, a small android application is created there. I have written several such applications and run them in the Genymotion emulator. All of them started without problems. I then decided to run these apps on my Honor 8X device using Android Studio. They also started without problems. But after a while, I run each of these already installed apps on my smartphone and Avast informs me that all these apps are infected. I checked the .apk files of these apps are on Virustotal and it informed me that the files contain Android virus: Evo-gen [Trj]. How could there be a virus, if at first everything started without problems? I'm sure my apps don't contain malicious code.
https://www.virustotal.com/gui/file/d12c7096e7502ea67f84af58d447c2f881eba41da0bffa8de5d305a8dfc726d6/detection
I can reassure you. This is an Avast problem with the heuristic process.
I had the same problem and have it again with two applications. These are reported as EVO-GEN
You need to contact Avast. There is an Avast website that they can use to report this issue. Then send the app to Avast. The signature is then taken from the database.
https://www.avast.com/de-de/false-positive-file-form.php#android
I have seen that In my phone. The superintendent of police here installed hacking app in my phone and it is one of them. I haven't intentionally remov d it for evidence. To be on the safe side get it rooted and use VPN security or Bitdefender antivirus free.
Can anyone with Genymotion installed please download and check if the Amazon Register app will run.
It gives an error about the device being modified/jailbroken and won't start in BlueStacks.
Please let me know if the app runs in Genymotion. https://play.google.com/store/apps/details?id=com.amazon.localregister.android&hl=en
Anyone know any alternatives that can run the app?
Payment apps like Amazon Register and Android Pay will not run on rooted or modified devices for obvious security reasons. Both BlueStacks and Genymotion fall into this category.
Just to be sure, and since you asked, I tried to install Register into a Genymotion VM running the "Google Nexus 5 - 5.1.0 - API 22 - 1080x1920" image with Google Play Services installed. Installation is fine, but running it gives the same result you describe for BlueStacks. FWIW, my rooted HTC One (M7) running AICP 10 does the same thing as well.
To overcome this, you might try something like Xposed RootCloak. There are folks reporting that they got Register working using this, but I didn't in my brief experimentation.
UPDATE: I can personally attest to the fact that Amazon Register will run on a RootCloaked device (HTC mentioned above). When I get a chance, I will try the same in a Genymotion VM.
I've searched online about getting crash logs from android and/or ios devices but could not find anything. I am testing an external app atm and have solid steps to reproduce a crash. Though, I can get a crash log/dump for the developer by using Eclipse... any guides on how to do so? Thanks.
To be able to see log calls and other info, you have to enable Debug Mode in your device.
You also need a specific driver to use your device with ADT. If you don't have that driver you can download a generic one from google in SDK Manager > Extras.
But be aware that "commercial" apps (downloaded from Google Play) are not debuggable,
or at least should not be.
First install the driver software for your mobile. Enable your debugging mode in your mobile. Go to DDMS->windows->show view click device. Here u can able to know wether ur device is connected or not.
I'm using a mac machine to build a android application, but it will crashed when run on device. but with the same code and key I build the application using another machine (windows). it is working well on devices.
Using my mac I already build several other apps and those are working well.
Can any one give me a solution?
First get the feedback of your client device as Kumar suggested.
get the clients device specifications,screenshots and try to reproduce on emulator.Exactly what caused the error may want you to ask him what steps to follow to reproduce the error.etc
is it possible to test this app on emulator with out any code changes?
Yes.You have a DDMS perspective.Just go to the top right corner above the coding window.There's a sort of plus (+) button there.From there you have a DDMS perspective.In this perspective,you can control emulator.You can feed the GPS co-ordinates here.
Look at this
Sounds like you are using some new API that your client doesn't have. He might be running an older OS. Run Android Lint checks and see if you get an API warnings.
Check your client's OS version and your own. Create emulator with your client's OS version and see if it's crashing.
I am getting reports from beta testers that after installing my .apk file their device is rebooting. After reboot the application operates as normal. Reboot after installation is not part of the desired/expected behavior, and itself sounds like a security breach.
Can anyone speculate as to why Android might reboot after an .apk install?
UPDATE:
One of the devices was an LG Ally, the other was a Samsung Galaxy Note
Are your Beta users using a rooted device? Do they have some kind of security app like "Lookout" installed on their device?
I'd suggest that you make your app create a trace log on the sdcard, that you'd get your beta tester to email to you.
Of course, this debugging process would be easier if someone loaned you the same model of the device your beta user is using.
No matter what your app should never be able to crash the operating system. A lot of this can depend on the device and manufacturer. For example, I noticed that when using a certain app to stream music on 2.3.x on the Droid X, the device would sometimes restart. I could not fix this issue myself but instead had to wait until a fix was provided by Motorola (which it eventually was). I would see if you can find a common occurrence on certain devices or manufacturers then do some researching on their reported bugs page. Also, what type of application is this (game/media/utility?)