ADB.exe is obsolete and has serious performance problems
I am using Windows 10 and when I launch the Virtual Device Emulator in Android Studio I keep getting the message which reads:
"The ADB binary at C:UserssiviwAppDataLocalAndroidSdkplatform-toolsadb.exe is obsolete and has serious performance problems with the Android Emulator. Please update to a newer version to get significantly faster app / file transfer".
I am a new developer with little experience. What do I need to update to a newer version so that message is no longer shown?
android-studio virtual-device-manager edited Jul 30 '18 at 17:17
rene
33.8k1181110
asked Jul 9 '18 at 7:34
SiviweSiviwe
334127
add a comment |
I am using Windows 10 and when I launch the Virtual Device Emulator in Android Studio I keep getting the message which reads:
"The ADB binary at C:UserssiviwAppDataLocalAndroidSdkplatform-toolsadb.exe is obsolete and has serious performance problems with the Android Emulator. Please update to a newer version to get significantly faster app / file transfer".
I am a new developer with little experience. What do I need to update to a newer version so that message is no longer shown?
android-studio virtual-device-manager edited Jul 30 '18 at 17:17
rene
33.8k1181110
asked Jul 9 '18 at 7:34
SiviweSiviwe
334127
9
If you already have the latest version of ADB installed, and still getting the error, this is a known issue. Google hasn't yet provided any other ADB. Click on the "never show again" option and continue.
– Sunil Kumar
Jul 30 '18 at 9:24
add a comment |
I am using Windows 10 and when I launch the Virtual Device Emulator in Android Studio I keep getting the message which reads:
"The ADB binary at C:UserssiviwAppDataLocalAndroidSdkplatform-toolsadb.exe is obsolete and has serious performance problems with the Android Emulator. Please update to a newer version to get significantly faster app / file transfer".
I am a new developer with little experience. What do I need to update to a newer version so that message is no longer shown?
android-studio virtual-device-manager edited Jul 30 '18 at 17:17
rene
33.8k1181110
asked Jul 9 '18 at 7:34
SiviweSiviwe
334127
I am using Windows 10 and when I launch the Virtual Device Emulator in Android Studio I keep getting the message which reads:
"The ADB binary at C:UserssiviwAppDataLocalAndroidSdkplatform-toolsadb.exe is obsolete and has serious performance problems with the Android Emulator. Please update to a newer version to get significantly faster app / file transfer".
I am a new developer with little experience. What do I need to update to a newer version so that message is no longer shown?
android-studio virtual-device-manager android-studio virtual-device-manager edited Jul 30 '18 at 17:17
rene
33.8k1181110
asked Jul 9 '18 at 7:34
SiviweSiviwe
334127
edited Jul 30 '18 at 17:17
rene
33.8k1181110
asked Jul 9 '18 at 7:34
SiviweSiviwe
334127
edited Jul 30 '18 at 17:17
rene
33.8k1181110
edited Jul 30 '18 at 17:17
rene
33.8k1181110
edited Jul 30 '18 at 17:17
rene
33.8k1181110
33.8k1181110
asked Jul 9 '18 at 7:34
SiviweSiviwe
334127
asked Jul 9 '18 at 7:34
SiviweSiviwe
334127
asked Jul 9 '18 at 7:34
SiviweSiviwe
334127
334127
9
If you already have the latest version of ADB installed, and still getting the error, this is a known issue. Google hasn't yet provided any other ADB. Click on the "never show again" option and continue.
– Sunil Kumar
Jul 30 '18 at 9:24
add a comment |
9
If you already have the latest version of ADB installed, and still getting the error, this is a known issue. Google hasn't yet provided any other ADB. Click on the "never show again" option and continue.
– Sunil Kumar
Jul 30 '18 at 9:24
9
9
If you already have the latest version of ADB installed, and still getting the error, this is a known issue. Google hasn't yet provided any other ADB. Click on the "never show again" option and continue.
– Sunil Kumar
Jul 30 '18 at 9:24
If you already have the latest version of ADB installed, and still getting the error, this is a known issue. Google hasn't yet provided any other ADB. Click on the "never show again" option and continue.
– Sunil Kumar
Jul 30 '18 at 9:24
add a comment |
7 Answers
7
active
oldest
votes
I am new to android as well. dkalev's answer is correct but not very descriptive for a new user. I have outlined the steps below.
- Double Shift to open the search box
- Type SDK Manager
- In the results shown click "SDK Manager"
- In the window that opens click the second tab "SDK Tools".
You should see that there is an update available for SDK Build-Tools on the first line - Check "Show Package Details" in the lower right hand corner
- Scroll to the last item under "SDK Build-Tools" and check the box. (Mine was 28.0.1)
- Click "Apply"
- In the dialogue box that pops up, click "OK"
- When the installer finishes, click "Finish"
- Uncheck "Show Package Details" and look at "Android SDK Build-Tools" (first line). There should be no update available and it should say "Installed"
- Click "OK" to close the SDK Manager
That's all there is to it.
Happy coding
answered Jul 27 '18 at 2:21
KuyaKuya
2,54931026
2
Great answer, really loved the "double shift to open search" tip.
– Mr.Hunt
Oct 19 '18 at 13:39
It should be an accpeted answer, I got resolved the same issue.
– Hassan Jamil
Nov 6 '18 at 6:59
Should there be a "Step 6b: also click the last major version in each that is not yet installed" (so 27.0.3, 26.0.3, etc)?
– Dale
Feb 27 at 22:00
If this doesn't work, check task manager for more than one instance of adb.exe; other apps besides Android Studio might start instances of this program.
– Dale
Feb 27 at 22:09
add a comment |
I had the same problem and solved it by updating the Android SDK Build-Tools. Open the SDK manager in Android studio (double shift and type SDK manager). Then on the second tab (SDK Tools) update the Android SDK Build-Tools and the error message should go away.
answered Jul 10 '18 at 8:30
dkalevdkalev
1986
well in my case it was itself Emulator to updates.
– Code Lover
Feb 23 at 5:18
add a comment |
In my case what removed this message was (After updating everything) deleting the emulator and creating a new one.
Manually updating the adb didn't solved this for. Nor updating via the Android studio Gui.
In my case it seems that since the emulator was created with "old" components it keep showing the message. I had three emulators, just deleted them all and created a new one. For my surprise when it started the message was no more.
Cannot tell if performance is better or not. The message just didn't came up. Also I have everything updated to the latest (emulators and sdk).
answered Oct 18 '18 at 13:56
soynerditosoynerdito
40138
2
Just to add on this matter. After the message went out. I created an older sdk emulator (older than current). And it showed the message again with that particular emulator. But then somewhere in the future the message stop showing at all. If you are with this issue, is a witch hunt for me. And cannot say it will not show again in the future. In my case I will every now and then (after sdk updates) will try to delete and recreate emulators just to keep them with a current revision.
– soynerdito
Nov 3 '18 at 10:33
add a comment |
(You mentioned you are new to Android Studio) so I recommend pressing the Android Studio > Help > Check for updates... button that will update your environment.
answered Jul 10 '18 at 13:28
IstvanIstvan
20225
add a comment |
Had the same issue but in my case the fix was slightly different, as no updates were showing for the Android SDK Tools. I opened the Virtual Device Manager and realised my emulator was running API 27. Checked back in the SDK Manager and I didn't have API 27 SDK Tools installed at all. Installing v 27 resolved the issue for me.
answered Dec 11 '18 at 22:04
vinnyhvinnyh
11219
add a comment |
First you need to check which SDK your Emulator is using and as @kuya suggested you need to follow those steps and install the latest version of that SDK Build Tool. Suppose your Emulator uses SDK 27 then you need to install latest in that series. For me it was 27.0.3. After that the error was gone.
answered Dec 25 '18 at 18:16
Amit RayAmit Ray
3,08721330
add a comment |
17-01-2019
This works for me.
Just opened Android SDK Manager Then it showed 4 Updates Available. So I just Updated it and No more above warning.
edited Feb 15 at 9:59
Jossef Harush
16.4k46675
answered Jan 16 at 21:37
SampathSampath
32.7k19141242
add a comment |
protected by Community♦ Jan 17 at 9:15
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
7 Answers
7
active
oldest
votes
7 Answers
7
active
oldest
votes
active
oldest
votes
active
oldest
votes
I am new to android as well. dkalev's answer is correct but not very descriptive for a new user. I have outlined the steps below.
- Double Shift to open the search box
- Type SDK Manager
- In the results shown click "SDK Manager"
- In the window that opens click the second tab "SDK Tools".
You should see that there is an update available for SDK Build-Tools on the first line - Check "Show Package Details" in the lower right hand corner
- Scroll to the last item under "SDK Build-Tools" and check the box. (Mine was 28.0.1)
- Click "Apply"
- In the dialogue box that pops up, click "OK"
- When the installer finishes, click "Finish"
- Uncheck "Show Package Details" and look at "Android SDK Build-Tools" (first line). There should be no update available and it should say "Installed"
- Click "OK" to close the SDK Manager
That's all there is to it.
Happy coding
answered Jul 27 '18 at 2:21
KuyaKuya
2,54931026
2
Great answer, really loved the "double shift to open search" tip.
– Mr.Hunt
Oct 19 '18 at 13:39
It should be an accpeted answer, I got resolved the same issue.
– Hassan Jamil
Nov 6 '18 at 6:59
Should there be a "Step 6b: also click the last major version in each that is not yet installed" (so 27.0.3, 26.0.3, etc)?
– Dale
Feb 27 at 22:00
If this doesn't work, check task manager for more than one instance of adb.exe; other apps besides Android Studio might start instances of this program.
– Dale
Feb 27 at 22:09
add a comment |
I am new to android as well. dkalev's answer is correct but not very descriptive for a new user. I have outlined the steps below.
- Double Shift to open the search box
- Type SDK Manager
- In the results shown click "SDK Manager"
- In the window that opens click the second tab "SDK Tools".
You should see that there is an update available for SDK Build-Tools on the first line - Check "Show Package Details" in the lower right hand corner
- Scroll to the last item under "SDK Build-Tools" and check the box. (Mine was 28.0.1)
- Click "Apply"
- In the dialogue box that pops up, click "OK"
- When the installer finishes, click "Finish"
- Uncheck "Show Package Details" and look at "Android SDK Build-Tools" (first line). There should be no update available and it should say "Installed"
- Click "OK" to close the SDK Manager
That's all there is to it.
Happy coding
answered Jul 27 '18 at 2:21
KuyaKuya
2,54931026
2
Great answer, really loved the "double shift to open search" tip.
– Mr.Hunt
Oct 19 '18 at 13:39
It should be an accpeted answer, I got resolved the same issue.
– Hassan Jamil
Nov 6 '18 at 6:59
Should there be a "Step 6b: also click the last major version in each that is not yet installed" (so 27.0.3, 26.0.3, etc)?
– Dale
Feb 27 at 22:00
If this doesn't work, check task manager for more than one instance of adb.exe; other apps besides Android Studio might start instances of this program.
– Dale
Feb 27 at 22:09
add a comment |
I am new to android as well. dkalev's answer is correct but not very descriptive for a new user. I have outlined the steps below.
- Double Shift to open the search box
- Type SDK Manager
- In the results shown click "SDK Manager"
- In the window that opens click the second tab "SDK Tools".
You should see that there is an update available for SDK Build-Tools on the first line - Check "Show Package Details" in the lower right hand corner
- Scroll to the last item under "SDK Build-Tools" and check the box. (Mine was 28.0.1)
- Click "Apply"
- In the dialogue box that pops up, click "OK"
- When the installer finishes, click "Finish"
- Uncheck "Show Package Details" and look at "Android SDK Build-Tools" (first line). There should be no update available and it should say "Installed"
- Click "OK" to close the SDK Manager
That's all there is to it.
Happy coding
answered Jul 27 '18 at 2:21
KuyaKuya
2,54931026
I am new to android as well. dkalev's answer is correct but not very descriptive for a new user. I have outlined the steps below.
- Double Shift to open the search box
- Type SDK Manager
- In the results shown click "SDK Manager"
- In the window that opens click the second tab "SDK Tools".
You should see that there is an update available for SDK Build-Tools on the first line - Check "Show Package Details" in the lower right hand corner
- Scroll to the last item under "SDK Build-Tools" and check the box. (Mine was 28.0.1)
- Click "Apply"
- In the dialogue box that pops up, click "OK"
- When the installer finishes, click "Finish"
- Uncheck "Show Package Details" and look at "Android SDK Build-Tools" (first line). There should be no update available and it should say "Installed"
- Click "OK" to close the SDK Manager
That's all there is to it.
Happy coding
answered Jul 27 '18 at 2:21
KuyaKuya
2,54931026
answered Jul 27 '18 at 2:21
KuyaKuya
2,54931026
answered Jul 27 '18 at 2:21
KuyaKuya
2,54931026
answered Jul 27 '18 at 2:21
KuyaKuya
2,54931026
2,54931026
2
Great answer, really loved the "double shift to open search" tip.
– Mr.Hunt
Oct 19 '18 at 13:39
It should be an accpeted answer, I got resolved the same issue.
– Hassan Jamil
Nov 6 '18 at 6:59
Should there be a "Step 6b: also click the last major version in each that is not yet installed" (so 27.0.3, 26.0.3, etc)?
– Dale
Feb 27 at 22:00
If this doesn't work, check task manager for more than one instance of adb.exe; other apps besides Android Studio might start instances of this program.
– Dale
Feb 27 at 22:09
add a comment |
2
Great answer, really loved the "double shift to open search" tip.
– Mr.Hunt
Oct 19 '18 at 13:39
It should be an accpeted answer, I got resolved the same issue.
– Hassan Jamil
Nov 6 '18 at 6:59
Should there be a "Step 6b: also click the last major version in each that is not yet installed" (so 27.0.3, 26.0.3, etc)?
– Dale
Feb 27 at 22:00
If this doesn't work, check task manager for more than one instance of adb.exe; other apps besides Android Studio might start instances of this program.
– Dale
Feb 27 at 22:09
2
2
Great answer, really loved the "double shift to open search" tip.
– Mr.Hunt
Oct 19 '18 at 13:39
Great answer, really loved the "double shift to open search" tip.
– Mr.Hunt
Oct 19 '18 at 13:39
It should be an accpeted answer, I got resolved the same issue.
– Hassan Jamil
Nov 6 '18 at 6:59
It should be an accpeted answer, I got resolved the same issue.
– Hassan Jamil
Nov 6 '18 at 6:59
Should there be a "Step 6b: also click the last major version in each that is not yet installed" (so 27.0.3, 26.0.3, etc)?
– Dale
Feb 27 at 22:00
Should there be a "Step 6b: also click the last major version in each that is not yet installed" (so 27.0.3, 26.0.3, etc)?
– Dale
Feb 27 at 22:00
If this doesn't work, check task manager for more than one instance of adb.exe; other apps besides Android Studio might start instances of this program.
– Dale
Feb 27 at 22:09
If this doesn't work, check task manager for more than one instance of adb.exe; other apps besides Android Studio might start instances of this program.
– Dale
Feb 27 at 22:09
add a comment |
I had the same problem and solved it by updating the Android SDK Build-Tools. Open the SDK manager in Android studio (double shift and type SDK manager). Then on the second tab (SDK Tools) update the Android SDK Build-Tools and the error message should go away.
answered Jul 10 '18 at 8:30
dkalevdkalev
1986
well in my case it was itself Emulator to updates.
– Code Lover
Feb 23 at 5:18
add a comment |
I had the same problem and solved it by updating the Android SDK Build-Tools. Open the SDK manager in Android studio (double shift and type SDK manager). Then on the second tab (SDK Tools) update the Android SDK Build-Tools and the error message should go away.
answered Jul 10 '18 at 8:30
dkalevdkalev
1986
well in my case it was itself Emulator to updates.
– Code Lover
Feb 23 at 5:18
add a comment |
I had the same problem and solved it by updating the Android SDK Build-Tools. Open the SDK manager in Android studio (double shift and type SDK manager). Then on the second tab (SDK Tools) update the Android SDK Build-Tools and the error message should go away.
answered Jul 10 '18 at 8:30
dkalevdkalev
1986
I had the same problem and solved it by updating the Android SDK Build-Tools. Open the SDK manager in Android studio (double shift and type SDK manager). Then on the second tab (SDK Tools) update the Android SDK Build-Tools and the error message should go away.
answered Jul 10 '18 at 8:30
dkalevdkalev
1986
answered Jul 10 '18 at 8:30
dkalevdkalev
1986
answered Jul 10 '18 at 8:30
dkalevdkalev
1986
answered Jul 10 '18 at 8:30
dkalevdkalev
1986
1986
well in my case it was itself Emulator to updates.
– Code Lover
Feb 23 at 5:18
add a comment |
well in my case it was itself Emulator to updates.
– Code Lover
Feb 23 at 5:18
well in my case it was itself Emulator to updates.
– Code Lover
Feb 23 at 5:18
well in my case it was itself Emulator to updates.
– Code Lover
Feb 23 at 5:18
add a comment |
In my case what removed this message was (After updating everything) deleting the emulator and creating a new one.
Manually updating the adb didn't solved this for. Nor updating via the Android studio Gui.
In my case it seems that since the emulator was created with "old" components it keep showing the message. I had three emulators, just deleted them all and created a new one. For my surprise when it started the message was no more.
Cannot tell if performance is better or not. The message just didn't came up. Also I have everything updated to the latest (emulators and sdk).
answered Oct 18 '18 at 13:56
soynerditosoynerdito
40138
2
Just to add on this matter. After the message went out. I created an older sdk emulator (older than current). And it showed the message again with that particular emulator. But then somewhere in the future the message stop showing at all. If you are with this issue, is a witch hunt for me. And cannot say it will not show again in the future. In my case I will every now and then (after sdk updates) will try to delete and recreate emulators just to keep them with a current revision.
– soynerdito
Nov 3 '18 at 10:33
add a comment |
In my case what removed this message was (After updating everything) deleting the emulator and creating a new one.
Manually updating the adb didn't solved this for. Nor updating via the Android studio Gui.
In my case it seems that since the emulator was created with "old" components it keep showing the message. I had three emulators, just deleted them all and created a new one. For my surprise when it started the message was no more.
Cannot tell if performance is better or not. The message just didn't came up. Also I have everything updated to the latest (emulators and sdk).
answered Oct 18 '18 at 13:56
soynerditosoynerdito
40138
2
Just to add on this matter. After the message went out. I created an older sdk emulator (older than current). And it showed the message again with that particular emulator. But then somewhere in the future the message stop showing at all. If you are with this issue, is a witch hunt for me. And cannot say it will not show again in the future. In my case I will every now and then (after sdk updates) will try to delete and recreate emulators just to keep them with a current revision.
– soynerdito
Nov 3 '18 at 10:33
add a comment |
In my case what removed this message was (After updating everything) deleting the emulator and creating a new one.
Manually updating the adb didn't solved this for. Nor updating via the Android studio Gui.
In my case it seems that since the emulator was created with "old" components it keep showing the message. I had three emulators, just deleted them all and created a new one. For my surprise when it started the message was no more.
Cannot tell if performance is better or not. The message just didn't came up. Also I have everything updated to the latest (emulators and sdk).
answered Oct 18 '18 at 13:56
soynerditosoynerdito
40138
In my case what removed this message was (After updating everything) deleting the emulator and creating a new one.
Manually updating the adb didn't solved this for. Nor updating via the Android studio Gui.
In my case it seems that since the emulator was created with "old" components it keep showing the message. I had three emulators, just deleted them all and created a new one. For my surprise when it started the message was no more.
Cannot tell if performance is better or not. The message just didn't came up. Also I have everything updated to the latest (emulators and sdk).
answered Oct 18 '18 at 13:56
soynerditosoynerdito
40138
answered Oct 18 '18 at 13:56
soynerditosoynerdito
40138
answered Oct 18 '18 at 13:56
soynerditosoynerdito
40138
answered Oct 18 '18 at 13:56
soynerditosoynerdito
40138
40138
2
Just to add on this matter. After the message went out. I created an older sdk emulator (older than current). And it showed the message again with that particular emulator. But then somewhere in the future the message stop showing at all. If you are with this issue, is a witch hunt for me. And cannot say it will not show again in the future. In my case I will every now and then (after sdk updates) will try to delete and recreate emulators just to keep them with a current revision.
– soynerdito
Nov 3 '18 at 10:33
add a comment |
2
Just to add on this matter. After the message went out. I created an older sdk emulator (older than current). And it showed the message again with that particular emulator. But then somewhere in the future the message stop showing at all. If you are with this issue, is a witch hunt for me. And cannot say it will not show again in the future. In my case I will every now and then (after sdk updates) will try to delete and recreate emulators just to keep them with a current revision.
– soynerdito
Nov 3 '18 at 10:33
2
2
Just to add on this matter. After the message went out. I created an older sdk emulator (older than current). And it showed the message again with that particular emulator. But then somewhere in the future the message stop showing at all. If you are with this issue, is a witch hunt for me. And cannot say it will not show again in the future. In my case I will every now and then (after sdk updates) will try to delete and recreate emulators just to keep them with a current revision.
– soynerdito
Nov 3 '18 at 10:33
Just to add on this matter. After the message went out. I created an older sdk emulator (older than current). And it showed the message again with that particular emulator. But then somewhere in the future the message stop showing at all. If you are with this issue, is a witch hunt for me. And cannot say it will not show again in the future. In my case I will every now and then (after sdk updates) will try to delete and recreate emulators just to keep them with a current revision.
– soynerdito
Nov 3 '18 at 10:33
add a comment |
(You mentioned you are new to Android Studio) so I recommend pressing the Android Studio > Help > Check for updates... button that will update your environment.
answered Jul 10 '18 at 13:28
IstvanIstvan
20225
add a comment |
(You mentioned you are new to Android Studio) so I recommend pressing the Android Studio > Help > Check for updates... button that will update your environment.
answered Jul 10 '18 at 13:28
IstvanIstvan
20225
add a comment |
(You mentioned you are new to Android Studio) so I recommend pressing the Android Studio > Help > Check for updates... button that will update your environment.
answered Jul 10 '18 at 13:28
IstvanIstvan
20225
(You mentioned you are new to Android Studio) so I recommend pressing the Android Studio > Help > Check for updates... button that will update your environment.
answered Jul 10 '18 at 13:28
IstvanIstvan
20225
answered Jul 10 '18 at 13:28
IstvanIstvan
20225
answered Jul 10 '18 at 13:28
IstvanIstvan
20225
answered Jul 10 '18 at 13:28
IstvanIstvan
20225
20225
add a comment |
add a comment |
Had the same issue but in my case the fix was slightly different, as no updates were showing for the Android SDK Tools. I opened the Virtual Device Manager and realised my emulator was running API 27. Checked back in the SDK Manager and I didn't have API 27 SDK Tools installed at all. Installing v 27 resolved the issue for me.
answered Dec 11 '18 at 22:04
vinnyhvinnyh
11219
add a comment |
Had the same issue but in my case the fix was slightly different, as no updates were showing for the Android SDK Tools. I opened the Virtual Device Manager and realised my emulator was running API 27. Checked back in the SDK Manager and I didn't have API 27 SDK Tools installed at all. Installing v 27 resolved the issue for me.
answered Dec 11 '18 at 22:04
vinnyhvinnyh
11219
add a comment |
Had the same issue but in my case the fix was slightly different, as no updates were showing for the Android SDK Tools. I opened the Virtual Device Manager and realised my emulator was running API 27. Checked back in the SDK Manager and I didn't have API 27 SDK Tools installed at all. Installing v 27 resolved the issue for me.
answered Dec 11 '18 at 22:04
vinnyhvinnyh
11219
Had the same issue but in my case the fix was slightly different, as no updates were showing for the Android SDK Tools. I opened the Virtual Device Manager and realised my emulator was running API 27. Checked back in the SDK Manager and I didn't have API 27 SDK Tools installed at all. Installing v 27 resolved the issue for me.
answered Dec 11 '18 at 22:04
vinnyhvinnyh
11219
answered Dec 11 '18 at 22:04
vinnyhvinnyh
11219
answered Dec 11 '18 at 22:04
vinnyhvinnyh
11219
answered Dec 11 '18 at 22:04
vinnyhvinnyh
11219
11219
add a comment |
add a comment |
First you need to check which SDK your Emulator is using and as @kuya suggested you need to follow those steps and install the latest version of that SDK Build Tool. Suppose your Emulator uses SDK 27 then you need to install latest in that series. For me it was 27.0.3. After that the error was gone.
answered Dec 25 '18 at 18:16
Amit RayAmit Ray
3,08721330
add a comment |
First you need to check which SDK your Emulator is using and as @kuya suggested you need to follow those steps and install the latest version of that SDK Build Tool. Suppose your Emulator uses SDK 27 then you need to install latest in that series. For me it was 27.0.3. After that the error was gone.
answered Dec 25 '18 at 18:16
Amit RayAmit Ray
3,08721330
add a comment |
First you need to check which SDK your Emulator is using and as @kuya suggested you need to follow those steps and install the latest version of that SDK Build Tool. Suppose your Emulator uses SDK 27 then you need to install latest in that series. For me it was 27.0.3. After that the error was gone.
answered Dec 25 '18 at 18:16
Amit RayAmit Ray
3,08721330
First you need to check which SDK your Emulator is using and as @kuya suggested you need to follow those steps and install the latest version of that SDK Build Tool. Suppose your Emulator uses SDK 27 then you need to install latest in that series. For me it was 27.0.3. After that the error was gone.
answered Dec 25 '18 at 18:16
Amit RayAmit Ray
3,08721330
answered Dec 25 '18 at 18:16
Amit RayAmit Ray
3,08721330
answered Dec 25 '18 at 18:16
Amit RayAmit Ray
3,08721330
answered Dec 25 '18 at 18:16
Amit RayAmit Ray
3,08721330
3,08721330
add a comment |
add a comment |
17-01-2019
This works for me.
Just opened Android SDK Manager Then it showed 4 Updates Available. So I just Updated it and No more above warning.
edited Feb 15 at 9:59
Jossef Harush
16.4k46675
answered Jan 16 at 21:37
SampathSampath
32.7k19141242
add a comment |
17-01-2019
This works for me.
Just opened Android SDK Manager Then it showed 4 Updates Available. So I just Updated it and No more above warning.
edited Feb 15 at 9:59
Jossef Harush
16.4k46675
answered Jan 16 at 21:37
SampathSampath
32.7k19141242
add a comment |
17-01-2019
This works for me.
Just opened Android SDK Manager Then it showed 4 Updates Available. So I just Updated it and No more above warning.
edited Feb 15 at 9:59
Jossef Harush
16.4k46675
answered Jan 16 at 21:37
SampathSampath
32.7k19141242
17-01-2019
This works for me.
Just opened Android SDK Manager Then it showed 4 Updates Available. So I just Updated it and No more above warning.
edited Feb 15 at 9:59
Jossef Harush
16.4k46675
answered Jan 16 at 21:37
SampathSampath
32.7k19141242
edited Feb 15 at 9:59
Jossef Harush
16.4k46675
edited Feb 15 at 9:59
Jossef Harush
16.4k46675
edited Feb 15 at 9:59
Jossef Harush
16.4k46675
16.4k46675
answered Jan 16 at 21:37
SampathSampath
32.7k19141242
answered Jan 16 at 21:37
SampathSampath
32.7k19141242
answered Jan 16 at 21:37
SampathSampath
32.7k19141242
32.7k19141242
add a comment |
add a comment |
protected by Community♦ Jan 17 at 9:15
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
9
If you already have the latest version of ADB installed, and still getting the error, this is a known issue. Google hasn't yet provided any other ADB. Click on the "never show again" option and continue.
– Sunil Kumar
Jul 30 '18 at 9:24