I noticed that randomly my phone restarts. I am not sure if this is because of my app (which I recently developed) or because of a Android 4.3 bug with with the Nexus 4. I am terribly sorry if this is the wrong forum. Any advice on how I can exactly pinpoint the issue?
Use your phone for a while without your app? If the problem doesn't occur you can then work on investigating the app.
Related
I just finished my first Android app. I tested it in the emulator and on my personal device (Nexus 6p). Other folks are installing it and it's working for them. My dad, however, also gave it a try. He has a Samsung Galaxy S6 running 6.0.1, and the app crashes on startup for him.
My guess is it's something touchwiz related. The thing is, he's not the most technical person, as far as getting a logcat would go. So... what are my options to try and investigate this issue?
Crashlytics can help you to retrieve the stack trace and exceptions when your app crashes.
But if you want to test and fix before the deploy, another options is Xamarin Test Cloud, it's a paid solution, but have a free-trial
[EDIT]
Searching in the internet, I found something similar to Xamarin Test Cloud, I personally have not tested this solution, but you can check it out.
TestMunk, they have a free plan.
This is an aspect of the extreme fragmentation of the Android ecosystem. I've seen bugs that manifest only on a specific device from a specific carrier. For example, at one point, Verizon broke ACTION_HEADSET_PLUG on one of their tablets, so that no app would ever receive it. It had worked fine on an earlier firmware version. Naturally, they refused to acknowledge the problem. The same tablet model from T-Mobile never exhibited this issue.
This is why I don't trust the emulator. It's fine for early testing, but you still need to test on the actual hardware that you intend to support. There are online services that test your app on a wide variety of real devices to try to uncover the weird vendor-specific issues. I've never used these services, so I can't recommend one.
We have developed a react-native (v0.17.0) application for both iOS and Android. The iOS version is very responsive on physical devices. On Android devices I see a tremendous amount of variability. On Android version 5.1 the app is super responsive. On two separate phones with 5.1.1 (and both phones with much better specs) it is highly unresponsive. The navigation takes at least five seconds, TouchableHighlight buttons sometimes do not register at all. I have of course turned off dev mode but the issue still persists. My issue is that I can't see the degrade in performance on the emulator and this makes it hard to pin down the issue. Has anybody experienced and fixed a similar issue? What would be an advisable way to pinpoint the issue?
Disabling dev mode should help on android because it is super slow.
There are a little lack of details about what you are using or doing in your app. But i also had some performance issues in the app and could find the reasons for those by using the sysTrace wich is explained in the following link
https://facebook.github.io/react-native/docs/android-ui-performance.html
Maybe you can take advantage out of this.
I'm currently developing an app for android that uses the flash. My miserable problem is that I don't have a device featuring a flashlight... Is there any emulator in the world that shows the flash state?
Thank you guys in advance!
José.
There is no emulator that can allow you test the flashlight. You need a real device for it.
You need to add the permission also to your manifest file - "android.permission.FLASHLIGHT"
If you are working with laptop then You can use bluestack to check your application related to flashlight it will work
The android emulator does not work with "flashlight apps".
I was also disappointed to hear this when I started developing my flashlight app quite some time ago. I haven't found a solution either, except for having a development device (my phone) to test the app on.
In general, it helps to have a development device on hand because the emulator is not always 100% accurate.
Best of luck.
I have recently published my second app on the Android Market. I've gotten a few e-mails about the app crashing on open, and all users were using the Motorola Backflip. It seems to work fine on all other devices. The app shows the background image, but crashes right after that.
Is there something different I have to do when coding for that device?
The strange thing is that it is very similar to my first app, which seems to work just fine for them. The major difference is that my second app is a paid app, and uses Android Licence Verification. My implementation should catch any license errors though, and I've tested this on my device.
Users have uninstalled and reinstalled the app without success. I'm stumped.
The other thing they're reporting is that the icon doesn't even show properly, but rather is a gear in a box, which makes me think that something goes awry very early in the installation process.
The solution was to have a user install aLogcat on their phone to send me the log.
It had to do with onCreateDialog. I was returning several dialogs, but one of them actually called .show(), which it's not supposed to do, of course. The thing is that this didn't cause an error on any phones except for the Backflip. The emulators also didn't error, or even warn me about it.
I have a motorola backflip and i can say that is not a good product....it's crashing for a lot of things....don't worry, your app is not wrong, the phone is wrong...
It appears as though everyone using my application on an LG Ally is having to redownload the application every time they turn off their phone.
I've received the folling market comments relating to the issue:
"Is great when it works. But if i shut my phone off i have to reinstall it. Lg ally."
"Great quick ref. I do have to redownload it every time my cell updates. Lg Ally"
And the following report in an email:
"The one problem that I have with it is should I turn my pohone off or the battery dies completly I have to redownload and install again. I was wondering if there was a way to fix this. I am using an LG Ally with the latest android sofware what ever that may be. Thank you for the app and your time."
Based on a quick google, the LG Ally currently has Android 2.1.
My application requests the following permissions:
android.permission.INTERNET
android.permission.CALL_PHONE
and is using copy protection.
What could be causing this issue?
From what I've read the problem has to do with the Ally specifically and the android Market.
They're saying that if copy-protection is turned off it should work normally.
from the Verizon Community Forums
I'm an app developer and this update has effected many of my users (with the LG Ally). Uninstalling/reinstalling fixes the problem temporarily but then after a reboot the issue is back.
I provided the app to user's outside the market and the problem was fixed. The only difference is the version from the Market has "copy-protection" enabled. So my guess is Verizon messed up apps with copy-protection somehow.
Just a tip if you are experiencing issues with apps, ask the app developers if the issue is with copy-protection and if they will turn copy-protection off in the Market or provide the app to you some other way.
-Peter