When i click on link created in development mode in eclipse, in chrome browser it shows message to install gwt plugin though I have installed the plugin.
I tried uninstalling chrome browser and reinstalling the plugin.
Any help?
Thanks in advance
The plugin uses the NPAPI, which is no longer supported by chrome.
You have to options:
get an older version of chrome which supports NPAPI or switch to Super Dev Mode.
I would advice you to use Super Dev Mode, because this is the future.
Take a look here: GWT Super Deve Mode
I've installed the GWT plugin in my Eclipse Luna. When I create a simple Web Application Project only for testing and using jre8, when running it and click on the link it shows this on browser, and if I change to jre7 it show this.
I've also found out here that "GWT Development Mode will no longer be available for Chrome sometime in 2014, so we improved alternate ways of debugging. There are improvements to Super Dev Mode, asserts, console logging, and error messages."
Can anyone tell me how to solve this errors if it is possible or what other ways of working with GWT are? Thank you
There are two different solutions you could take :
Downgrade to an older browser like Firefox 24.8.1esr which still supports the GWT Developer Plugin.
Use the Super Devmode, which can be easily accessed in the GWT 2.7 version in Eclipse. More information about the Super Dev Mode can be found here.
DevMode works fine on the latest esr version of Firefox 24, but I use Eclipse 3.7 with jre7_25. Here you can find a solution how to install GWT plugin in Chrome manually (regarding your 1st image).
On the 2nd image I see 404 error which means that the file is not there. Make sure the war path in your Run Configuration is correct (see Arguments tab). In my case I use -war to specify a location to war directory.
P.S. This information may be useful about DevMode.
I am trying to install the GWT Developer plugin for Chrome (Version 34.0.1847.131 m) and I get the following error "This application is not supported on this computer. Installation has been disabled. The following problems are detected:" and "NPAPI plugin is required by this app". Is there a way around this?
I have installed Microsoft Visual C++ 2008 SP1 Redistributable Package as suggested by one answer.
I am also trying to run in Explorer (version 11) and it requires me to download the GWT Developer plugin for Firefox. Which then requires content to be opened in a new window. I then elect to open "gwt-dev-plugin.xpi". When it finishes downloading it requests me to save it (if I open it it just download again). Is there a way around this?
I am running on Windows 8.1.
I am also trying to run in Explorer (version 11) and it requires me to download the GWT Developer plugin for Firefox.
To avoid that, open IE11 dev tools and under the "Emulation" menu change the "Document mode" from "Edge" to "10". The page should refresh and from there you should be able to install the GWT plugin for IE.
Once it's installed you can fall back to the "Edge" document mode.
Worked for me.
But as #apanizo said, I'd use the Super Dev Mode if possible. The dev mode is already not supported anymore in the latest firefox and it is going to be the same for the upcoming Chrome 35. No clue about IE though.
Enable the GWT Developer Plugin in Chrome.
Check for other plugin that is installed on Chrome.
Click on plugins for other systems to get more GWT Developer plugins.
Here is the URL for GWT missing-plugin.
Click on required GWT plugin and simply click on save button as shown below for IE9.
This might be useful for you:
Create shortcut Chrome to desktop.
Right click to shortcut and choose properties.
Click to Compatibility tab
Inside Compatibility mode check "Run this compatibility mode for:" and choose Window 7.
Apply and Ok.
Source: https://code.google.com/p/google-web-toolkit/issues/detail?id=7778
If you want to think Agile, here's what I adopted as a solution:
superDevMode is not practical, it takes forever to compile each time on my i7 with 8Gb of memory.
The solution I adopted is that I'm using FF for developement and I validate everything is fine only after GWT compiling on chrome (once in a while for the pauses).
Seriously I didn't see the point of having dev mode working on all browsers. In addition it runs curiously faster on FF than on Chrome (under windows). For Ubuntu (actually) I had to downgrade my FF to the version 24 to have it work (but since it's only a dev machine it doesn't bother me)
p.s: superDevMode might compile faster if optimized, hoestly I didn't try it: increasing the localWorkers could reduce compile time and make superDevMode a good solution, but I can't tell you; I didn't try that: http://mojo.codehaus.org/gwt-maven-plugin/compile-mojo.html#localWorkers
This problem sounds similar to a few others, except in my case the OK button is not grey-ed out. But for those who would rather not click the links...
Trying to create or edit an AVD from within Eclipse, after entering my settings, the "OK" button seems to be "clickable", but when I click it absolutely nothing happens.
I've made sure I have the appropriate system images installed, and that the target platform matches the API being used. Clearly a CPU has been chosen, skin set, etc... all the things that would make the OK button greyed out, which it's not.
I can create/edit AVDs if I run the AVD manager from outside eclipse, so this isn't the end of the world, but I feel there's a solution to this particular problem and I want to help solve it.
I've tried running eclipse as an administrator (that's what stopped the AVD manager from crashing outside of eclipse). I've tried just waiting around, or clicking multiple times. Looking at the Task Manager, no new processes begin when I click OK, nor does eclipse's CPU or RAM usage increase at all. The "Edit Android Virtual Device" window doesn't even go away.
Any clues?
(Running Indigo with the ADT plugin, btw, not the bundled version, which failed to work in a different way. Java 1.6.0 45. Windows 8, unfortunately. Plenty of RAM etc)
THIS IS A POSSIBLE WORKAROUND FOR BUGS IN ADT 22.6.0 ONLY, THESE BUGS SUBSEQUENTLY FIXED IN FOLLOWING BUILDS
Download and install new ADT v22.6.1 from here (zip) or use SDK manager to update
Seems like some bug from Google side, this problem found after "ADT 22.6" update. Widely reported on "Android Open Source Project - Issue Tracker" and nobody properly answered it yet.
However I was partially successful to create an AVD by opening "AVD manager.exe" from "Android SDK" for creating new AVD try to open directly AVD Manager.exe in SDK folder.
May be we have to wait for any conformation from Android community
Worked for me, sort of.. .
(Windows 8.1 Pro 64 Bit, Java JDK 1.7 Update 25, Eclipse Standard Kepler Service Release 1, Android Development Toolkit 22.6.0.v201403010043-1049357)
Update 1
Further research revealed that launching AVD Manager from SDK Manager (Tools --> Manage AVDs...) also works without any problems.
Update 2
More bad news is AVD creation not working from command line tool too.
Update 3
Assuming some parameter passed during launching AVD manager from Eclipse causes these problems
Update 4
Updated Java to JDK 1.7 Update 51 and Eclipse Standard SDK to Kepler Service Release 2 their latest and no resolution to the problems. Also tested under Debian and same results obtained.
Update 5
At https://code.google.com/p/android/issues/detail?id=66661 android project members conforms the problems and promises to fix by upcoming versions of ADT (22.6.1 - 22.6.3). At the mean time I would suggest to roll-back ADT to a lower version version 22.3.0
To uninstall current ADT go to
Help --> About Eclipse --> Installation Details --> Android Development Tools --> Uninstall
I may suggest uninstalling whole packages from Android (DDMS, Hierarchy Viewer, NDT, Traceview, OpenGL ES..etc..) to avoid any possible compatibility issues and install a fresh new ADT from above link through archive installation method.
Hope this will solve this problem temporarily. And wait for new release of ADT here.
Update 6
New ADT, version 22.6.1 is out now which will solve these problems
To elaborate on the statement "I can create/edit AVDs if I run the AVD manager from outside eclipse" in the OP:
Run the following on the command line
<android-sdk-location>/tools/android avd (on Linux in this case)
This launches the same AVD window you see when you click the AVD Manager icon in the eclipse toolbar. But this instance of the AVD manager does not have the bug, and you can create and run emulators as you did before the bug was introduced.
1 minute solution
I used a quick workaround where I cloned a device that already existed. The Clone button worked and I was able to successfully edit the clone.
Steps:
Select a Device by Google
Click the "Clone..." button
A window will pop up, click "Clone device"
Select the newly cloned Device, it should say "... by User"
Click the "Edit" button on the side
There you have it, you now have your own custom virtual device
Update and Solution: AsYashwanth Krishnan said, The bug in question is now fixed in later versions. I tried ADT 222.6.1 and ADT 22.6.2 , and they did not suffer from the bug of not not being able to create or edit Android Virtual Devices. The direct solution is to update you ADT to latest version, The workaround written below is left only for historical purposes.
Historical Workaround As #Yashwanth Krishnan said, this is a bug in ADT plugin 22.6; so best workaround is to rollback. for those asking how to rollback, here is a step-by-step guide:
First: Uninstall ADT plugin and all related plugins for android:
help->about
Installation details
Select android plugins and press uninstall button
Restart
Second: Download ADT 22.3.0 Archive from https://dl.google.com/android/ADT-22.3.0.zip
and install it
add repository from archive on local disk
Select android plugins
INFO:
I WAS able to create an AVD successfully after clicking OK several times and modifying some of my settings as a test.
I tried yashwanth krishnan solution and tried to open the AVD Manageer.exe directly without success. The manager will not open directly for me on Windows 8 x64. It tries to open, then shuts down immediately...
I met this issue too . The issue occurs in the latest version 22.6 which was released in March . Meanwhile I did the testing in 22.3 , the issue was not found .
So that I suggest that rollback the ADT to 22.3 and wait the new fix for 22.6
I banged my head on this for several hours until I found out that the default location was C:\username path\SDKs or something, where Android was installed on my system to D:\sdks\android_sdk_windows. So, changing the Eclipse Android directory to D:\sdks\android_sdk_windows fixed it.
I also heard that it may help things if you install the Android SDK to a path without spaces.
Hope this helps someone keep some hair.
Today I ran into the same problem after installing Maven. I messed around with different Path settings to get it to work and I ran into issues. I was also trying to install the google server for GCM. Somewhere in what I was doing I corrupted the Android Virtual Device Manager. I searched S.O. for an answer, then I decided to follow the first rule of TechSupport. I reinstalled the tool kit!
I went into the SDK manager and I uninstalled the tools (by clicking the Tool checkbox). It took several minutes to delete them all. Then I reinstalled the Tools which took about ten minutes. I rebooted Eclipse and the AVD and worked just like it did yesterday!
This time it only took a total of twenty minutes to fix.
Per the release notes, this problem has been resolved in revision 22.6.1, which is now available for download.
Updated your Android SDK Tools to 22.6.1 in Eclipse by selecting Window > Android SDK Manager and follow the prompts to install the update.
After that update finishes, select Help > Check for Updates and follow the prompts to update the appropriate Eclipse components.
After completing these updates, I tested the AVD functionality and it appears to be working properly.
i just copied the avds from a different system as descriped here:
Android - How to copy the emulator to a friend for testing
I faced the similar issue. I am using 23.0.2 version of android SDK.
"OK" button was disabled, but then I went to the path where android SDK was installed. In my case:
C:\Program Files\Android\android-sdk\
and executed AVD-Manager.exe by right clicking and selecting Run as an Administrator, and it worked like a charm.
Sometimes the AVD cannot be created because of this following error while starting:
x86 emulation currently requires hardware acceleration!
I was also facing this same issue. If u are facing the same, then it can be resolved by opening SDK Manager -> Under Extra -> Installed "Intel x86 Emulator Accelerator (HAXM Installer). Then when creating the AVD, select the proper CPU. This should work. :-)
For those posting that we need to set the sdcard size: I tried that and many other settings, and none of that helps. I get the NoClassDefFound Exception mentioned by mogilka, in the Error view. No configuration settings are going to fix that. It seems a bad update was pushed
Give some value for your sd card. May be something like 100 or 200
I'm trying to load an applet using JNLP. Things work fine on every browser I've tested, except for Safari (tried on Safari 5.0.3 on OSX Snow Leopard).
This seems a Safari related bug, because even the JNLP applet used for testing in the plugin2 page on Oracle doesn't seem to be working, as Safari tries to load "Ignored.class" instead of looking at JNLP file.
Does anyone know a workaround for this issue?
Ok, so after a lot of tinkering, it seems that the reason for this behavior lies in the plugins installed on Safari (and Firefox 3.6, it seems).
Instead of working with the latest Java Plugin 2 NPAPI, it's using some older plugin. So the real fix is to remove that older plugin from Safari: Go to /Library/Internet Plug-ins and remove JavaPluginCocoa.bundle (also, remove it if you have it on ~/Library/Internet Plug-Ins).
This are the same directions described in this Apple Knowledge Base article, although for different reasons.
When you do this, Safari will use the new Java Plugin 2, and will work exactly as other browsers using the newer plugin (namely, Chrome or Firefox 4, unsure about Opera. For Firefox 3.6 you'll have to do a similar thing, but following the steps in this bug report)