I am trying to setup flutter on my device, so far I have been able to download the flutter SDK and android studio and satisfy the conditions of flutter doctor to start learning android application development:-
flutter doctor
I ignored the absence of visual studio as I don't want my app to be compatible with windows(as I am trying to develop for Android) but I am not able to fix the missing java bundle, any help on how would I do that?
I just ignored it for a second and moved on to set up my emulator but on running, it shows a pop up which says "Attach a debugger or ESC to cancel"(the pop-up is something like this.) how would I fix it.
This doesn't run the app on the emulator so how would I fix that?
Also on trying to debug, it throws this error, I am totally confused on how to proceed further to at least run my app so that I could start developing and learning flutter?
I am following along this to run my application.
Edit:
I have the java bundle in place but don't know how would I configure Android Studio to get it.
java's prescence
Also that the emulator is now showing that the System UI is not responding and on closing it, it further shows this.
It's been a week since I am trying to work out the setup of flutter but some way or the other some issue happens, please help.
Thanks in advance.
you have to install java runtime environment and It'll work. get from here
it'll show like this if you have JDK installed properly.
I wonder if anyone has faced the same problem.
When we done some modification on the code, as the emulator is running; is there any way we could see the instant change without closing the emulator?
Sometimes when I made changes on the code then run the emulator, the amendment that I made doesn't seem to show on the emulator even after I clean the project.
Does anyone have any idea how to solve this?
Thanks.
Eclipse has an option under 'Run' in the menu bar to build, and run. This will re-package the application and send it to either your AVD, or attached android phone.
[2011-11-15 22:29:18 - MyAndroid] Failed to install MyAndroid.apk on device 'emulator-5554': device not found
[2011-11-15 22:29:18 - MyAndroid] com.android.ddmlib.InstallException: device not found
What troubleshooting steps have you done?
Has the app been installed on the emulator previously? If so, fully uninstall the app from the emulator first.
Try closing the emulator, and eclipse (if using eclipse). Then restart and try again.
If the issue keeps happening, you may need to delete the 'cache.img' in your AVD directory.
And if that doesn't help, delete the AVD, and recreate it.
I downloaded Android SDK and using Eclipse for development.
I am trying to run HelloAndroid program.
Everything goes fine till the installation of the application.
[2011-02-20 23:34:31 - HelloAndroid] Installing HelloAndroid.apk...
[2011-02-20 23:34:58 - HelloAndroid] Success!
[2011-02-20 23:34:58 - HelloAndroid] Starting activity com.example.helloandroid.HelloAndroid on device emulator-5554
[2011-02-20 23:35:01 - HelloAndroid] ActivityManager: Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.example.helloandroid/.HelloAndroid }
Above is, what is there in the console tab.
As soon as I take my pointer to the Menu button on the emulator or after say 2-3 min... I receive the below mentioned error from windows.
emulator.exe has encountered a problem and needs to close. We are sorry for the inconvenience.
Measures taken to solve this problem :
I turned off my firewall and tried running it, but it in vain.
I closed the emulator and re started it from the Window -> Android SDK and AVD Manager, but in vain. I also tried checking the
wipe user data
checkbox in the Manager window, but in vain.
PS: Only once till now the application did run properly and showed me the Hello Android Message but that too crashed. After that, the application has never even worked. It shows the home window with date and time, and crashes before showing the above mentioned reasons for the crash.
Also, I use Windows xp SP 2.0 and Eclipse 3.6.1. I choose min-sdkVersoin as 10.
Thaks in advance
Try Minimum API level=8 (that would be Android 2.2.)
Failing that. Note the Eclipse and JVM versions in the system requirements. I would stick with Eclipse "Classic" (3.5) if you're just trying to get your feet wet. Ensure that your JVM version is compatible.
I have found that Google don't really make things "linear" when it comes to installing stuff sometimes. Failing that, uninstall the JVM, and follow my deployment instructions I have written here. As this is exactly what I did and never had any probs. Hope this helps.. good luck!
Have you tried running a new AVD (Android Virtual Device) from the SDK manager (without loading any apps)? Does it crash too? If it does, then you might think reinstalling SDK again cause somethin aint right.
I moved my Android project to a laptop and now I get this when I hit Debug. Sounds like this is a bug? This shouldn't happen via Eclipse as far as I know.
Re-installation failed due to different application signatures.
The weirdest thing is this happened after I upgraded sdk/adt and Eclipse to support SDK 2.2 It was working fine earlier, and now it doesn't, so it might be a bug.
It happens because keystores on your laptop and original pc are different. it's called debug.keystrore
and located in %USER_HOME%/.android/ folder. TO be more specific it happens because eclipse tries to push apk with reinstall key. So you have two options
Share debug.keystore between various development pc's
Manually uninstall your apk from device ( using adb )
I also got the same problem and fixed it. you should do the following to fix it,
Uninstall the application from your mobile if you load it
already.
To uninstall goto settings->application->manage application.
Run the application again and choose the mobile
Hope this will help you
After you copy debug.keystore to your PC, you need to rebuild project on PC.
I had the same issue using the Droid emulator. I solved it by uninstalling the package from the application settings in the emulator as you would a normal device. On the next run, it reinstalled and the error went away.
I got the same problem and fixed it by just wiping the user data on the emulator. My guess is that the emulator keeps the project installed unless you wipe the data, so if your new project doesn't match some internal parameters it doesn't like it and won't reinstall it.
I also had the same problem and fixed it by uninstalling the app and reinstall it again.
ah i think i found your answer:
Why does the app signature change in Android after a classpath change?
its changed if you change the classpath
After searching and checking the phone, i came to know that i am currently developing 2nd version of this application which is already downloaded from android market in my phone, now as this app is signed and having different signatures this is throwing the above error.
Now, to resolve this issue, i had just uninstalled the app from mobile and run/install the application again.
I had the same issue with the emulator and i ran the command "adb uninstall TheNameOfPackage". Of course you must first go to the directory where the adb.exe has been installed, usually C:\Program Files\Android\android-sdk\platform-tools, and then run the above command.
For me after I copied all of my keystore files from my machine at home, I had to do a Project->clean. After that it worked perfectly.
When i tried to uninstall the application from my device after this issue occurs, i cannot able to find the app in my device. I don know where it gone. Then i uninstalled using adb,
adb -d uninstall <app package name>
This is the answer who are facing the issue similar to my problem.
I had the same issue.
To fix it I uninstalled the old .apk of the project from my device.
Go to device/emulator Settings -> Apps, find your app and uninstall it.
Or
In Android Studio open tab "Gradle" (on the right side), open:
appName
..appName
...Tasks
....install
.....uninstallAll
and click twice on this task to execute it.
Important note:
If you still get this error after uninstalling, try to Build->Clean Project.
If you still get this error, even if in your device Settings->Apps list you have no this app already, try to Build->Clean Project