Think about extremly simple flutter application that contains one Container widget on the screen and GestureDetector on it.
main goes to myApp, main and myApp widgets are in the same dart file.
myApp goes to HomePage which is a different dart file.
HomePage has one Container and GestureDetector widgets.
GestureDetector's onTap function is : print('pressed');
"pressed" appears for the first time when container tapped. The problem is when I tapped for several times on this container. "pressed" appears after a delay. Sometimes I see it after compilers' message.
uid=10153(com.example.vocabulary_master_8) 1.ui identical 4 lines
Here is my flutter doctor -v finding.
[!] Android Studio (version 4.1.0)
• Android Studio at C:\Program Files\Android\Android Studio
X Flutter plugin not installed; this adds Flutter specific functionality.
X Dart plugin not installed; this adds Dart specific functionality.
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
After I upgrade Android Studio to 4.1.2 and Nexus 6 API 30, I started to get this error and delay.
Could you please somebody help?
Best regards.
Try printing with an integer variable that gets incremented every time you press the icon. Prints the way you want.
GestureDetector(
child: Icon(Icons.person,color: Colors.black54,),
onTap: (){
i = i+1;
print("clicked person:$i");},
behavior: HitTestBehavior.translucent
),
Firstly you should install the Dart plugin as dectected by flutter doctor.
Coming to your issue, there can be many reasons for the delay :
I guess you are running it in debug mode on an emulator, the performance in debug mode will be slow and laggy compared to release mode. To test the app in release mode, use a real device instead of an emulator and instead of flutter run, use flutter run --release.
print statement might sometimes get delayed. Instead of trying to print something try updating your UI on tap. And as seen in the above scenario, as you are tapping several times, you are forcing the debugger to print the same statement multiple times, hence in case of flutter, it check if the print statements are same or not, if they are same, it will combine all of them and print an output like this :
uid=10153(com.example.vocabulary_master_8) 1.ui identical 4 lines
after a certian delay.
So in short you code is working fine, the delay is caused because flutter takes some time to recognize and combine the similar print statements.
Yes, I also had GestureDetector is little slower in my emmulator.. I am not sure why... If you need just a Tap function then try with InkWell or Listener for better performance...
I was using Visual Studio and it's Debug mechanism is really useful to me. With many header and C files in 1 project, just a simple F10 it could take me a tour around from the beginning of the main() function so that I could see the sequence of the code being executed.
Now I'm jumping into Android Studio and start with a project using NDK, JNI (this project for example: https://github.com/googlesamples/android-ndk/tree/master/gles3jni), it makes me confused because there're many .java files and others C++ (native code) files and I don't know which code from which file is executed first and how it goes on.
My Question is: I'm looking for a way to debug in Android Studio line by line from the beginning to see its workflow likes how Visual Studio did but all I got from searching is how to start from a breakpoint when debugging.
I have tried putting the break point in the onCreate() method of the launcher activity and use F8 to Step Over and F7 to Step Into but it doesn't work as i expect. It keeps taking me to the super class Activity.java and GLSurafaceView.java instead of taking me to the C++ code. Is there any way to do so in Android Studio and how to do it?
I have tried with others project but the problem still remain the same. Hope someone could help.
This won't happen. Your app (the Java boilerplate code) is set to respond to many system events that happen when the user works with the app and the device on which the app is installed. If your c++ code is a piece of monolythic straightforward algorithm, you can set s breakpoint in the beginning and really follow step by step. But with Android Studio, even this process is not as easy as with Vusial Studio. To begin with, it's always remote debugging, dependent on delicate communication protocols.
This said, you can try to set up Microsoft Visual Studio as your IDE for debugging native Android code. It is surprisingly robust, and also may be more familiar to you.
Since you've asked about Android Studio, I will answer about that - I am not familiar with Visual Studio for Android and perhaps it is better for what you are asking.
In Android studio such debugging is very hard - although some people said they managed to get it to work, I wasn't able to. Especially in a complex environment. So, what I'm doing is extensive logging, with as many details as possible, and visual debugging - put some text view on the screen and update it with the info you need. This could be quite powerful in some cases. Or, alternatively, make some changes in your ui or your scene as a result of certain conditions you define - so you could see the visual effect. Again, much less useful than debugging, but can still be quite powerful.
I'm using Android Studio 1.5.1 on Kubuntu 15.10 and lately, Android Studio freezes completely whenever I right click into the project explorer. The only thing I can do then is to kill the process.
More oddly, whenever I hover the Help menu with the mouse, the complete OS freezes completely and I have to restart the computer. I am not 100% sure if these two issues are related, but they started at the same time.
Sometimes (about 10% of the time) it works well. I have no idea what influences this pattern, though. This used to happen earlier as well, but much less frequent.
The usage of different color schemes or deactivating plugins seem to have no influence on this behavior. I also did not install any fishy third party software or anything else that could (to my knowledge) have influenced this. Any ideas?
The issue seems to be resolved in the latest stable release (2.0).
I've recently run into this as well. Pointing jstack at the hung process suggests that it's this problem.
Switching to the Darcula or GTK+ theme resolved it for me. Weirdly, I can switch back to the Intellij theme afterwards and the problem stays fixed - I just have to switch to GTK+ or Darcula at some point after startup but before triggering a right-click menu.
Edit, 1 day later: In a deeply unimpressive plot twist, this solution no longer works for me. I've changed nothing since yesterday, but now attempting to switch themes triggers the lockup ಠ_ಠ
Edit, 1 day, 5 minutes later: After a restart the situation improved slightly - changing the theme now works again, and avoids the freeze-on-rightclick failure. I'm finding it difficult to take this as much of a victory.
Edit: As karpfen notes below, this issue has been resolved in the latest release. Huzzah!
I installed android studio.. it was working fine. Now all the sudden, none of the auto complete features are working.. I can type anything anywhere no variable checking, no help with functions or checking anything. I can still compile the project and I get errors when that happens.
Can anyone please help me out with this issue.
#1 From Build menu (of your Android Studio), click Rebuild Project option.
#2 Then once rebuild completes, go to File > Invalidate Caches / Restart... and Click on Invalidate an Restart button.
This really works for me.
Source: https://code.google.com/p/android/issues/detail?id=61844#c4
#1 Rebuild is required, because Android-Studio does simply rely solely on Gradle's build-result (without static-analysis support, at least at time of writing, 2022).
#2 Clearing cache is required, because the previous build-result (before above rebuild) may be indexed, which makes Android Studio ignore latest Gradle build-result
(this is a very good speed optimization, but a very bad Developer-experience as well).
There can sometimes be other reasons too, which is why there are many other answers posted here.
You can also check if Power Save Mode on File menu is disabled.
Close Android Studio
Go to C:\Users\UserName\.android and rename the folder:
build-cache to build-cache_old
Go to C:\Users\UserName\.AndroidStudio3.x\system
OR (for Android studio 4 and Higher) go to C:\Users\UserName\AppData\Local\Google\AndroidStudio4.x
and rename these folders:
caches to caches_old
compiler to compiler_old
compile-server to compile-server_old
conversion to conversion_old
external_build_system to external_build_system_old
frameworks to frameworks_old
gradle to gradle_old
resource_folder_cache to resource_folder_cache_old
Open Android Studio and open your project again.
Originally use:
compileSdkVersion 32
targetSdkVersion 32
And an update to 33 appeared, I updated it and the suggestions in the XML no longer appeared, I went back to 32 and now the suggestions appeared.
Close Android Studio
Go to c_users_path_on_windows/.AndroidStudio3.5/system/
Delete the cache folder
Start Android Studio
This works for me.
Most of the times i have seen that the problem is that Power Save Mode is enabled, to disable go to Current inspection profile (lower right corner in Android Studio).
I have not run into this problem personally, but try checking the following settings (File -> Settings or Alt+F7):
Project Settings [name]
Inspections - ensure that Android and Android Lint is checked, or alternately just set it back to default using the dropdown box at the top.
IDE Settings
Editor -> Code Completion - ensure the Autopopup code completion is checked (and check the rest of the settings based on your preference.
Uncheck "Power Save Mode" in "File" tab
If nothing works (like happened with me ) go to your user profile in windows at %userprofile% . You will find folders there (hidden) named with the version of the android studio you are using and prefixed with a dot.
like .AndroidStudio3.1. Just delete that .
Solution: Try disabling "File -> Power Save Mode" in Android Studio (Beta) 0.8.14 - Mac OS X
On windows, the option can be at some other place.
I had the same problem then I recalled that while exploring the new android studio, I switched on the "File -> Power Save Mode" to see what it does?
I disabled the power save mode and all those intelligent features were back.
It turned out that in Power Save Mode, Android Studio switches off the modules responsible for features like Smart Code Completion and Code Analysis.
I had a similar problem where none of the other solutions worked.
Closing Android Studio and then deleting the .idea and build folders resolved the issue.
Disable Power Save Mode and Invalidate Cache and Restart.
For Artic Fox 2020|3.1 Version: Auto Complete Suggestion Problem.
Please Follow the Following Steps:
Close Android Studio
Locate caches folder in C:\Users{username}\AppData\Local\Google\AndroidStudio2020.3
and Delete it.
Open Android Studio Again.
Check your Android studio version and Target that version folder at below location
C:\Users{username}\AppData\Local\Google
Note : AppData folder is Hidden in Windows
This Solution also works if android studio mess up with xml files and java code. Don't! modify your code otherwise IDE won't able to change it to default. If you see such messy code just follow above steps and your code will be fine again.
It's Working
Disable Power Save Mode
Untick Power Save Mode Option ::
File -> Power Save Mode
There is a power saver mode in android studio if accidentally you click on that it will disable code analysis which will reduce the battery consumption and performance will also increase but it will not detect any errors and do auto complete operations.
To disable power saver mode
- Go to File Menu of Studio
- Uncheck The Power Saver Mode
In your IDE code analysis will be shown using an eye symbol at the right corner of your android studio.
If Green means it is enabled and there is no error in your code.
If Red Means It is enabled but there are few errors in your code.
If It is white or blur then code analysis is disabled
Just remove all the folders named AndroidStudioPreview
On Windows:
Go to your User Folder - on Windows 7/8 this would be:
[SYSDRIVE]:\Users[your username] (ex. C:\Users\JohnDoe)
In this folder there should be a folder called .AndroidStudioPreview
On Mac OS X
Remove these files:
~/Library/Application Support/AndroidStudioPreview
~/Library/Caches/AndroidStudioPreview
~/Library/Logs/AndroidStudioPreview
~/Library/Preferences/AndroidStudioPreview
There can be several things which cause this.
Make sure you've write the correct version in targetSdkVersion and compileSdkVersion.
Make sure targetSdkVersion and compileSdkVersion are same.
Other solutions can be:
Invalidate caches & restart Android Studio from File → Invalidate Caches / Restarts...
Clean your project from Build → Clean Project
Rebuild project from Build → Rebuild Project
Make project from Build → Make Project [this process may take some time]
Be sure to check for IDE errors by clicking the button at the bottom right of android studio.
In my case, there was a bad plugin, and the IDE Fatal Errors window prompted me to uninstall the plugin. (I wish I'd known about this feature before spending half a day invalidating caches, deleting folders, and reinstalling android studio with no luck.)
It worked for me.
From menu select:
File -> Power Save Mode
and make sure it's disabled
Go TO Left Side Top File Option
Then Click To Power Save Mode
Disable Power Save Mode That Fix This Issue
In my case, when I switch keyboard language to English, the auto complete works again.
if the autocomplete isn't working for you in Android Studio, just press File and uncheck the Power save mode, it should work fine after that.
if power save mode is already unchecked then first check then uncheck them.
If you have a library project included, make sure the library has the dependencies in build.gradle listed using the api configuration, not the implementation configuration.
Also make sure that the project that includes the library has all the dependencies listed (using the implementation configuration is fine here).
'The file size (2561270 bytes) exceeds configured limit (2560000 bytes). Code insight features are not available.'
Had this issue for days with none of these proposed solutions working before eventually getting this message in yellow under the tabs after adding a line of code. Removing the line of code eliminated the message but not the issue. There appears to be a code size window where you lose insight features but don't get this message, at least for me. Once you go over a certain point the message finally pops up. The suggested solution in a different thread for this issue was to edit 'Help/Edit Custom Properties' to increase the configured limit, but just opening this brought up a dialogue asking if I wanted to create an 'idea.properties' folder so I decided not to risk that approach over eventually cutting the file size.
If sometimes this problem can occur if you misspelled a file extension or make a file without adding an extension.
Check you have added the file extension correctly.
I think that answer may help you.
I'm using mac and suddenly the code completion (^space) not working. There are no errors. Turned out the android studio's shortcut was conflicted with system's shortcut. I don't know why it suddenly happen because it was fine before, maybe there was an update on my Mac.
See below setting for the conflicting shortcut
In my case, C:\Users\UserName\AppData\Local\Google\AndroidStudio2020.3\ just delete caches folder and restart android studio. after deleting this caches folder my problem was solved :)
I encounter with this problem while adding a kotlin library into my project on mac. Changing macbook language to english solved this problem. I also had some weird problems with auto-generated databinding codes, those are also solved.
Try Invalidate caches/Restart from File in Menu Bar from android studio.
Close Android Studio
Go to
C:\Users\YOUR_USERNAME\.android
and rename the following folder to:
build-cache to build-cache_old
then Go to (Android studio lower then version 4)
C:\Users\UserName.AndroidStudio3.x\system
OR (Android studio 4 and Higher) Go to
C:\Users\UserName\AppData\Local\Google\AndroidStudio4.x
or
C:\Users\UserName\AppData\Local\Google\AndroidStudio2021.2
depending on your version and rename these folders:
caches to caches_old
compiler to compiler_old
compile-server to compile-server_old
conversion to conversion_old
external_build_system to external_build_system_old
frameworks to frameworks_old
gradle to gradle_old (if exists)
resource_folder_cache to resource_folder_cache_old (if exists)
Open Android Studio again and the autosuggsion will be fixed.
and You can also check if Power Save Mode is disabled or not from the File menu.