I have set up Flutter in my Ubuntu Machine, but cannot accept the Android Licenses, thus am not able to use the tool.
Flutter appears to be working fine in root, but when I try to run flutter doctor it tells me that Android Licenses have not been accepted, even though I did accept them. If I try to type again flutter doctor --android-licenses it works as though I never accepted the licenses. If I accept all of them once more, it just gets back to as though I never accepted them.
I could use flutter in root, but that's not really secure and I would rather have it usable as a normal user.
EDIT:
The solution appears to lie in the repositories.cfg file. It appeared to be missing and adding a blank file with that name solved the issue.
Go to your $ANDROID_HOME/tools/bin and open the command line
Run the following command ./sdkmanager --licenses
Accept All licenses listed there.
Related
i couldn't run my flutter application on a real device neither on the emulator even thought the flutter sdk is installed and it's path is set does anybody knows what can be the cause of it ?
here's how it is shown in android studio
when checked the project structure it says how can i also fix this ?
here's the command that i made because they said that i should verifiy that my phone can be seen by the flutter sdk and that i should make sure that there is no error left by the 'flutter doctor' command
but nothing did actually help
I would make sure to get rid of that Android licenses and VS Code error.
Then on android studio, from the menu bar: "Tools > Device Manager > Create new device". Create a new virtual emulator from there and delete any old ones.
Also, I would recommend to ask for help after your "flutter doctor -v" comes out clean with "No issues found!".
I am trying to create an app using Room persistence library in Android Studio. The problem is that is not working when I try to run, it gives me this message:
Error:Execution failed for task ':app:compileDebugJavaWithJavac'.
> java.lang.UnsatisfiedLinkError: org.sqlite.core.NativeDB._open_utf8([BI)V
I am following everything from this https://www.youtube.com/watch?v=KAHAQunQkDE tutorial, and it worked with the guy on the video. Maybe is something that I should install, but I dont know what. (I double checked every step on the video and everything is ok, except that mine dont run)
My error in this case was due to /tmp being mounted with the noexec flag. If you're on linux, you can check if this is the case with a grep /tmp /proc/mounts to see the mount options. The sqlite JDBC repo has an issue about this problem.
In my case, I fixed it by remounting /tmp without the noexec option. If you don't want to (or can't), it seems to be suggested to set GRADLE_OPTS=-Djava.io.tmpdir=/some/other/path. The issue linked above also mentions settingorg.sqlite.tmpdir`. Unfortunately, neither of those seemed to work for my by setting gradle opts in Android Studio.
my emulator is not runnnig and gives the error in image below
error image
and test at run window
C:\Users\Wahlah\AppData\Local\Android\sdk\tools\emulator.exe
-netdelay gprs -netspeed full -avd Nexus_4_API_21
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
terminate called after throwing an instance of 'std::logic_error'
what(): basic_string::_S_construct null not valid
and second error exist is this image
ERROR 2
I got the same problem with the same logged warnings and errors (and the alert as well).
Although from the first logged line (C:\...emulator.exe) it looked like the tools did find the emulator - my problem was resolved only after I followed this answer, and changed the ANDROID_SDK_ROOT environment variable (which pointed to a folder above the sdk instead to the sdk's folder itself).
So I changed it from
C:\Users\<username>\AppData\Local\Android
to
C:\Users\<username>\AppData\Local\Android\sdk
and... voila! The emulator is running properly.
I should note that I'm working on Windows and from the question it looks like AIR TRAVELS was as well.
I had the same problem and fixed it by selecting Cold Boot from the Tools > Android > AVD Manager > Edit > Show Advanced > Boot option from Quick Boot to Cold Boot.
Hope this helps.
You can fix this error, need configure the device again. Download all the necessary libraries through the SDK manager.
I've just published an app of mine to the Google Play Store and it seems that it keeps force closing and crashing on the users.
I am not asking for a solution as to why, but i am curious.
On eclipse i have the Emulator and the target API of my app was Android-19 (it's 17 now because i'm changing that to see if it'll help). And while in eclipse and while running the emulator, with several devices (tablets, nexus one and such) , and the app works perfectly fine.
My friend has sent me a screenshot and the message that comes up once they try to open the app is "Unfortunately, Data Tool has stopped."
Any brainstorming ideas?
-Colt
THIS ISSUE IS NOW FIXED!
Here's a way to locally test your app's release APK outside of Eclipse. It's written for Linux, but should be pretty close for other development hosts.
adb uninstall my.package.name; adb install -r my.package.apk && adb shell monkey -p my.package.name -s 0 1
This assumes the simplest case where you only have a single device connected. If you want a more versatile version that allows for easy switching between devices and/or versions, let me know and I'll add it.
Try building it without proguard first and test. If that works then its proguard configuration file issue.
First of all just let me say that I have looked through the solutions on stackoverflow and have not found one that has worked. These include:
linking folders (but that was absurd for my case)
Creating the environment (system) variables for the computer and eclipse.
Still when I run Android Virtual Device Manager on eclipse and when I start the AVD I get:
Starting emulator for AVD 'AVD_for_4_65in_720p_Galaxy_Nexus'
PANIC: Could not open: ¨8W
I have tried other devices still it doesn't work. I have two hard drives but the AVDM says the correct path up top which is D:\Users\User.android\avd
Anyone got a solution?
Thanks a lot.
P.S.: It says the AVDs are "A valid Android Virtual Device."
You have to add a new user environment variable (Windows 7):
Start Menu > Control Panel > System > Advanced System Settings (on the left) > Environment Variables
Add a new user variable (at the top) that points your home user directory:
Variable name: ANDROID_SDK_HOME
Variable value: C:\Users>User Name<
Also, move the .android folder in your Users directory to the same directory your SDK is in
maybe something went wrong with your configurations .
close eclipse and adt , and then delete the ".android" folders from both the drive you have installed it into , and from your user folder.
also , try to uninstall the sdk tools from the sdk manager , and then re-install them . in addition , try to use a little older android version for the emulator .
another solution is to set the environment parameter of your system:
ANDROID_SDK_HOME = C:\users\my.username
if nothing helps , try to completely uninstall anything related to android , and install on a different drive (or the default one).
anyway , this issue was already reported and handled by some users here .
Try to run eclipse "As Administrator".
Of course after adding the path and user home.
It works every time for me. When i simple "run" eclipse it gives me
PANIC: Could not open: ¨8W //or something similar, almost different each time
When i "run as administrator" it works perfect every time.