This is a weird bug I have come across where my activity or say application does not start. As soon as I touch icon of my app and I press lock button , then when i unlocked it I can not see my application opened and moreover it is not in the active application status also. As per the flow of application runs it should get opened behind or atleast can be seen in Active Application status?
Is there any way to resolve it.
Maybe you can trace your code from adb or find tools in android sdk tools folder finder the tool to get the logs
Related
I have the flutter local notifications package installed and everything works just fine except for one thing:
When the screen is locked and a local notification appears, on iOS it doesn't show the real name of the App but only the name of the flutter project. And if I unlock the screen, the real name of the App appears.
I already changed the App name like you normally would do it, so going to the android folder/app/src/profile/AndroidManifest.xml and also on iOS Runner/Info.plist and change the name.
I also changed the title inside the NotificationController, but this only effects the name of the local notification when the screen is unlocked.
How can I change it so that not depending on wether the screen is locked or unlocked, only the real App name is shown?
Thank you very much!
Ok I guess I know whats going on. Somehow in debug mode sometimes the "real" name of the app doesn't show up but the project name. When releasing the app, this issue disappears.
So if anyone else has this problem, don't worry about it, just release the App, it will function correctly.
Well when I was facing the same problem I just searched that name in the Project level search using Ctrl+Shift+f. After searching it will show you all the places where the old name of your application still exist then you can change them one by one.
In my case I have found app name about 15-16 places some of them I have changed already and then changed the rest.
I hope this will work for you too.
Recently I noticed one thing in my app.
I created apk for my app say ABC.apk and copied to my device and installed it by clicking on it. After the installation got successfully completed, I got 2 options 'Done' and 'Open', the usual options we get after installation.
I clicked on 'Open' and run the app. I moved to some screen and I minimized the app and moved to someother app, when I click my ABC, it started from my first screen.
It was just fraction of seconds I moved back to it, hence it should not be killed though launched it like it is first time.
Few things I noticed I if I explicitly killed this first instance from background running apps and start the app again it is not giving me this problem, same if I click 'Done' instead of 'Open' it works fine.
Is there anyone who are facing same issue, or have some solution for it?
Thanks in advance.
Prajakta
The problem is the way that the app gets launched from the installer doesn't exactly match the way Android launches apps from the HOME screen. Because this, if you initially launch your app from the installer, when you then later launch the app again from the HOME screen, Android doesn't recognize that the app is already running and just creates a new instance of the root Activity and adds it to the existing task on top of whatever activities are already there.
This is why, if you kill the app and start it again from the HOME screen, you won't ever see this strange behaviour.
This is a nasty Android bug which has been around since the dawn of time and is still broken, even though countless issues have been opened about it and the behaviour is reproducible and well-documented.
See the following issues and questions:
https://issuetracker.google.com/issues/36941942
https://issuetracker.google.com/issues/36907463
https://issuetracker.google.com/issues/64108432
App restarts rather than resumes
Re-launch of Activity on Home button, but...only the first time
There is a workaround documented in my answer to
Re-launch of Activity on Home button, but...only the first time
Just some general comments that come to mind that you must consider that can cause problems.
If you are trying to deploy an apk, did you switch from debug to release before building it? Make sure you are doing a full release. Do a clean and rebuild while in release mode as well.
Did you sign the apk?
Make sure all the necessary (if any) permissions are set in the manifest that will be needed by your app, on the device.
Hope these help point you in a direction.
Mike
Is there a way I can disable close button of the android emulator or get a confirmation before closing.
After several runs I accidently closed the emulator.
Also it takes a lot of time to load the emulator again.
There is no built-in support anywhere for this. You have to search for 3rd-party solutions.
Here is one I found quickly.. http://lifehacker.com/5183947/noclose-disables-windows-close-button.
Go to the website, let it load, and then you have to search for NoClose. It is there, but it does not scroll automatically to the app to download.
You can also try to search for another similar solution.
I want to know the exact method which invokes/starts all the apps. I basically want to block a certain set of apps using xposed module. Its ok if the app icon is visible but the app should not be launched after clicking on it. To be precise nothing should happen when the user clicks on the app icon.
So I want to know where the source code which invokes the apps.
PS : I would also like to know if there is any way to hide the icon of the app as well.
Make your own launcher app and replace it with the ones running on mobile phones.
You can check the sources of Laucher and Laucher2 currently running on Android system.
During testing of mgwt application in emulator, if we suddenly stop and go to home page in emulator and start the application again, it will directly load the last page where we were wokring. Why it is not resetting it to the first page?
In GWT on module function, I am always loading the default place. I need to explicitly go and remove data and then start application to proceed.
How to overcome this problem programatically? Do we have any reference for it? I have not used gwt-phonegap, it is just mgwt with GWTp framework application.
I think your application isn't stopped. I think it is running in background. If you bring it back to front, it shows the same screen again.