I have an Android app with a corresponding Widget. It works perfectly in the past before 2017Nov. However, After my update to the Android studio, Gradle, and build tools. The app always build with an app that cause "Problem loading widget"
.
To make sure I am right I get back my code version before 2017Nov, and recompile. Problem still here. To solve this problem, my only way is to reboot the device. After reboot the device, the widget loads normally. My question:
What kind of special system calls the Android device will trigger when restart the device?
More information: Actually I have done one more test. While my widget is live and no problem is shown after reboot, I uninstall it, reinstall it. Then problem loading widget immediately appear. After that reboot, problem gone.
Related
I wanted to share a very annoying problem I have with Expo React-Native. It does not break the app or something but it is just annoying to work with.
I am using Expo and I am using the Android Studio Emulator. Expo is installed on a Virtuall Device and its working properly, however I have this problem for a longer time I think since ReactNative 0.61(or 0.60) when they implemented "Fast Refresh". There are time "Fast Refresh" does work right but sometimes when changing a small thing u get an Error thats something like:
Attempted to assign to readonly property.
When you reload the app so the error goes away expo shows a white screen with an endless blue spinner... It's just annoying to quit the node server, close the app, open devops in a browser and bring everything back up everytime.
Has anybody experienced the same behavior or knows a fix for this ?
I have tested my application using ionic-serve and everything run normally.
But, when i tried it using device, the application will first run the splash screen (which is not run when using ionic serve) and nothing happen, only white screen.
Can somebody please help me with this situation?
I have no idea about what happen.
The white screen issue often occurs on devices and not in the browser when you are injecting something into a module that kicks off your app. Try to figure out which one, and remove it (if it's not being used) or update it.
First thing to do is to check for errors in the log. To see them, type the address chrome://inspect/#devices in chrome, and click on your app. You'll need to make sure your device has usb debugging turned on.
I've created a sample application (just a textview, nothing else), and I noticed a bug.
After installing it from the SDCard, it displays the "Application installed" screen, with the done and open buttons.
If I click the open button, a strange thing occurs:
Whenever I put the application in background and reopen it from the application icon, it doesn't reopen it, it creates a new instance.
I can confirm that it is creating a new instance, because after putting it on background and reopening a few times, when I click the back button, it opens the previous instance, instead of returning to the home screen.
Now the strange thing is that it only happens after installing from the SDCard and clicking on the open button.
If I click the done button (or installing via ADB) and open the application via icon, it doesn't happen.
Also, if I click the open button (and the bug occurs), after the application is ended for the first time, the bug doesn't occurs anymore.
I've tested it in different devices and in different Android versions (GB, HC and ICS), and the bug is reproducing in them all.
Does someone know if this is an known issue from Android and if so, does someone have an official reference that I can refer?
Thanks in advance
Yep, it is a nasty, well-known Android bug that has been around since the very beginning. See the following:
Android issue 26658
Android issue 2373
Android app acts differently installed from adb vs sdcard
I keep getting the message 'Activity not started, its current task has been brought to the front' despite making changes to the code. I wasn't aware of changing any settings in Eclipse besides creating a new AVD and it was working fine earlier today. Now it's not reinstalling at all.
I'm not sure why the problem started when it did but I installed some updates from Eclipse and Android and it seems to be working fine now.
There are several thing that you can do to solve this problem:
You can close your AVD and then start it again.
You can manually uninstall your application using AVD interface (Home - Menu button - Manage apps - All tab - Your app - Force stop/Uninstall).
The solution was to start the task manager and end multiple AVD emulator processes that had somehow built up.
i also constantly have this problem, even when i change the code. what helps for me is simply to start my application in the debug mode; then it starts without that warning. later when i start the application in the non-debugging mode again it normally starts without that warning (at least for a while).
Like the title says, whenever I make any changes in the code I don't see the changes in the AVD. Is there a way to do this without closing the AVD and starting it again?
I'm using Eclipse.
Thanks!
I have noticed this behavior at times as well. In the ADB log it will state something like the activity is already started and has been brought to the front even though it was already on the screen. Not sure what the cause of this behavior is and it seems to happen randomly. I have dealt with this in the past by force stopping the app in the AVD or just uninstalling it. Sometimes pressing the home button on the AVD and then running the APP from eclipse seems to fix this.