Faced this problem, and after spending hours of time on this, got the solution.
The issue is, whenever I installed the app, the TWLauncher of the Samsung device, enters a crash loop, where it always crashes.
No idea why, but when I replaced the icon with an other one, it fixed the issue. So use a different image and try, and it will work! Just thought I would share this with all of you.
Related
Conflict comes only some time when sign up. When he comes to my office then it works fine on trying. But after going to home he faces same problem. Please let me know the reason behind it.
I have an icon within my app that links to my fan page. It was working fine before but since around 2 weeks ago, whenever someone clicks on the icon, they get to an error page saying: “Trouble Loading Timeline”. It also says “Tap to retry” but nothing happens when they do.
Although I’m using the same source code for both (because of Unity3D engine), this happens only for Android, not iOS. I didn’t have this issue after my last update but it started happening suddenly a few weeks after. I didn’t make any changes in my source code in the last few weeks.
Would anyone know what the issue is and how to fix it?
Thanks
I would really like to understand this in a hope that I can fix this problem which I have spent countless hours on...
I understand the circumstances surrounding the behaviour of the problem, but have no idea where to fix it, though I guess it will be in manifest some where...
If I install my APK and then select 'DONE' after the install is complete, my app resume functionality works fine! But if I select 'OPEN' then the app resume functionality will never resume to the last used screen, it just keeps returning to whatever the launcher screen is..
and there is more..
when I select OPEN, but then access task manager and END the app process, then launch it from the ICON in the home screen... the resume works perfectly again..
It's driving me crazy.. I have seen some people comment about this exact problem but have never seen an answer to go with it! I was hoping if I can understand what OPEN does differently to DONE then selecting the icon on the home screen to open the app, then I / we might be able to finally figure it out!
Thank you!
Found the answer .. or what there is of it.
Seems like I am among many others who lost countless, countless hours trying to fix this one when it is reported as an android OS bug which is extremely hard to fix. Here are two links to androids official bug issues regarding this particular bug.
You can go through the replies and test various fixes, but unfortunately the bug is still not fixed from androids side (apparently).
Just hope this helps save SOME PEOPLE a lot of time if they can read this early on!!
(Basically the android OS gets confused in some instances when installing the app and causes this behaviour).
http://code.google.com/p/android/issues/detail?id=2373 (original issue)
http://code.google.com/p/android/issues/detail?id=26658 (follow up of the exact same issue as was still not fixed since 2373...)
Please add code to onCreate
if (isTaskRoot()) {
final Intent intent = getIntent();
final String intentAction = intent.getAction();
if (!intent.hasCategory(Intent.CATEGORY_LAUNCHER) &&
intentAction != null && intentAction.equals(Intent.ACTION_MAIN)) {
finish();
System.exit(0);
}
}
I frequently get complaints from customers that they can't click the Allow button on the SSO screen of my app, that's based on the Facebook SDK. They say that it simply does not respond to clicks.
I have never been able to reproduce this problem. But it occasionally does have various errors when you do press the button, but trying a couple of times always ends up working.
Has anyone else encountered this issue? If I can't find a solution, I'm just going to have to permanently disable SSO.
Looks like a similar problem that I had. It was solved by not calling the Facebook app by default when going to authorize. To do so, simply add Facebook.FORCE_DIALOG_AUTH to the authorize parameters. A similar post with this answer can be found here.
I hope it helps =]
I feel a little bit silly asking this, but I haven't been able to find any answers on my own. My Force Close dialog has a "Report" button. I think it's a great idea, and I wish everyone had it. At first, I thought it must be something I turned on without realizing it, but not only can't I find any setting that I might have touched, I also can't find any reference to this button existing on the Internet. I have a Droid, and I know 4 other people with Droids, and they say they don't have the option to report Force Closes. Am I special? Am I just missing something? The "report" button has been there for at least a few weeks now.
When I use the Report button, I get a screen with a "feedback" field and a checkbox for "Include system data". Below that , it says "Information from feedback reports will be shown to the developer of the application." Under that are Preview and Send buttons.
As a developer, I've never received one of these reports.
I'd try to send a report to myself, but it seemingly only shows the button for apps installed from the market, and I don't know of a way to crash my production app.
I suppose I could publish a simple crashing app just to try it out, but I thought I'd ask you folks first.
Edit:
You can view screenshots here: http://bentobin.com/crashReportImages/
This is a new feature of Android :)