The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Short answer: java.lang.NoClassDefFoundError: org.openqa.selenium.android.AndroidDriver usually means your test is compiled for Selenium’s retired AndroidDriver, or the JAR that once contained that class is absent from Eclipse’s runtime classpath. It is not automatically an Android manifest problem. Confirm the missing class, inspect the actual Eclipse build path, then either reproduce an intentionally pinned legacy stack or move the test to Appium’s supported Android drivers.
What this exception is telling you
NoClassDefFoundError is thrown when the JVM tries to load a class that code references but cannot define at runtime. In this case the missing binary name is org.openqa.selenium.android.AndroidDriver. The class may have been present when an old example was written, available only to the compiler, or removed from the dependency set after an upgrade.
That distinction matters: an Android project can have a perfectly valid AndroidManifest.xml and still fail before the first test starts. The class loader is looking for a Java class in the test process, not an Android component in the application package.
There is another common Selenium error, “unable to locate driver executable.” That concerns a browser-driver executable or its path; it is a different failure from a missing Java class. Fix the class-loading problem first.
#1 Best Overall
- POWER YOUR STUDY, FUEL YOUR PLAY – Discover smarter learning with the Lenovo Idea Tab. Stay campus-ready with all-day battery life, AI-powered apps to enhance your work, and sharp graphics for tv marathons with friends.
- SMOOTH, POWERFUL, IMMERSIVE – The MediaTek Dimensity 6300 processor is more powerful than ever, with the AI-enhanced multitasking you need to stay ahead.
- CIRCLE IT, SEARCH IT – Use your Lenovo Tab Pen or fingertip to circle items for instant search results or to translate other languages without switching apps. Circle to Search with Google ensures answers are only a circle away.
- SHARP VIEW, CLEAR SOUND – Experience sharp visuals and immersive sound for study sessions and streaming breaks. With 72% NTSC and quad Dolby Atmos-tuned speakers you can enjoy your study breaks with vivid videos and crystal-clear sound.
- LEVEL UP YOUR STUDY – Write, organize, sketch, and calculate with four learning apps built to match your flow. Lenovo AI Note, Squid, Nebo, and MyScript Calculator help you stay clear, focused, and ready for every study session.
Why AndroidDriver projects commonly break
Selenium’s own AndroidDriver was retired
Selenium removed its own Android and iPhone driver code from the repository in December 2013 and recommended alternative projects. Code importing org.openqa.selenium.android.AndroidDriver therefore targets a historical API. A current Selenium dependency is not expected to provide that class.
The old JAR-copy advice is not a confirmed fix
A historical mailing-list reply suggested downloading relevant JARs and placing them in a test project’s libs folder. The original reporter said the same error continued, and the thread does not identify the project’s complete dependency graph. Treat that suggestion as an unverified legacy experiment, not as a reliable solution.
Compile-time and runtime paths differ
Eclipse can compile against one container while launching a JUnit configuration with another. A JAR shown under “Referenced Libraries” may be missing from the launch configuration, or a duplicate Selenium version may win class-path ordering. Check both the project build path and the exact test launch.
Diagnostic sequence in Eclipse
- Capture the complete exception. Expand the first
Caused bysection and record the exact missing binary name. For this case it should beorg.openqa.selenium.android.AndroidDriver, including capitalization. - Find every reference. In Eclipse use Search → File and search for
org.openqa.selenium.android.AndroidDriverandnew AndroidDriver. Check test sources, copied examples and generated code. - Inspect the project path. Right-click the project → Properties → Java Build Path → Libraries. Expand Maven Dependencies, Gradle containers and manually added JARs. Do not assume a JAR provides the class; inspect its contents or dependency documentation.
- Inspect the launch path. Open Run → Run Configurations…, select the JUnit or Java application configuration, and review the Classpath tab. Ensure the same dependency container used by the project is present and remove stale, duplicate Selenium JARs.
- Clean and rebuild. Use Project → Clean…, select the project, then rebuild. If Eclipse still shows old containers, refresh the Maven or Gradle project and recreate the launch configuration.
- Check the dependency declaration. Record Java, Selenium, Appium Java Client and test-runner versions from
pom.xml,build.gradleor the downloaded JAR names. A screenshot of the Libraries tab alone is not enough to diagnose transitive conflicts.
Choose a repair route
| Route | When it fits | What to expect |
|---|---|---|
| Pin the historical stack | You must keep an old test suite unchanged and can reproduce its original environment. | Requires the exact compatible Selenium-era artifacts and a controlled Java runtime. It preserves obsolete APIs and carries ongoing security and maintenance risk. |
| Migrate to Appium UiAutomator2 | Android native, hybrid or web automation is required. | Appium documents UiAutomator2 for all three Android modes. Test code and capabilities need updating. |
| Migrate to Appium Espresso | The target is an Android application where Espresso integration is the better fit. | Appium documents Espresso for Android applications; setup and test APIs differ from Selenium AndroidDriver. |
For a maintained project, migration is normally the safer decision because the missing class belongs to a retired Selenium driver. Select the Appium driver from the target type, not from the package name in the old exception.
Rank #2
- COMPACT SIZE, COMPACT FUN – The Lenovo Tab One is compact, efficient, and provides non-stop entertainment everywhere you go. It’s lightweight and has a long-lasting battery life so the fun never stops.
- SIMPLICITY IN HAND - Add a touch of style with a modern design that’s tailor-made to fit in your hand. It weighs less than a pound and has an 8.7” display that’s easy to tuck in a purse or backpack.
- NON-STOPPABLE FUN – Freedom never felt so sweet with all-day battery life and up to 12.5 hours of unplugged YouTube streaming. It’s designed to charge 15W faster than previous models so you can spend less time tethered to a power cable.
- PORTABLE MEDIA CENTER - Enjoy vibrant visuals, immersive sound, and endless entertainment anywhere you go. The HD display has 480 nits of brightness for realistic graphics and dual Dolby Atmos speakers that provide impressive sound depth.
- ELEVATED EFFICIENCY - Experience the MediaTek Helio G85 processor and 60Hz refresh rate that ensure fluid browsing, responsive gaming, and lag-free streaming.
Migrating from AndroidDriver to Appium
Verify the Java and Selenium baseline first
Appium Java Client 9 requires Java 11 or later. Its migration guide also states that Selenium versions below 4.14.1 will not work with Java Client 9 or newer. In Eclipse, check Window → Preferences → Java → Installed JREs, then check the project’s Java Compiler compliance level. Make the build tool, Eclipse JRE and test launch use the same supported JDK.
Use a build tool instead of copying random JARs
Declare one Appium Java Client version and let Maven or Gradle resolve its Selenium dependencies. Then refresh the Eclipse project and inspect the resolved dependency tree for multiple Selenium versions. Do not mix a manually copied Selenium JAR with the build tool’s transitive Selenium artifacts unless you have a documented reason.
Update the session model
Replace the import and constructor that reference AndroidDriver from Selenium with the Appium Java Client’s Android driver classes. Configure the Appium server endpoint, automation name and device/application capabilities required by your selected driver. Keep capabilities limited to those supported by the installed Appium driver and your device or emulator.
A migration is not completed by renaming an import: review waits, context switching, mobile gestures, server startup and teardown. Run one smoke test against a known emulator or device before converting the full suite.
Rank #3
- 【Dual-Function 2-in-1 Tablet】URAO Android 16 Tablet is a game-changer with 2-in-1 professional work mode. The tablet is compatible with a Bluetooth keyboard, mouse, stylus, headset, and a convenient foldable case. The setup and connection process is straight forward, enabling you to effortlessly transform your tablet into either a laptop or a computer mode. Friendly Tips: Mouse does not come with batteries.
- 【Android 16 & Octa-Core Processor】URAO Android tablet features the latest operating system Android 16 and an 1.8 GHz octa-core processor ensure of excellent performance, seamless multitasking, getting rid of annoying ads, emphasizing privacy and security by designing enhanced app permissions, providing you complete management control.
- 【36GB (6+30GB) RAM 128GB ROM 】Our 11 inch tablet comes with 36GB (6+30GB) RAM 128GB ROM and maximun 1TB TF card ( not included )expandable ensures you of a fast APP launch and smooth gaming experience. URAO tablet also come with pre-installed Google Play Store, you can easily download any needed Apps such as Facebook, Twitter, Youtube, etc.
- 【7800mAh Battery with Fast Charge】The built-in large capacity and low consumption CPU enable our URAO 11 inch tablet to stand by for up to 3 days and allows you to enjoy up to 8 hours of mixed reading, watching TV shows, playing games, surfing the web. URAO tablet adopts fast-charging technology ,easily charge via the USB Type-C port and rest assured the battery will last. It is a good companion for you to play and study!
- 【Wi-Fi 6+Bluetooth5.4】URAO 11 inch android tablet adopts the lastest sixth generation WiFi technology and the upgraded bluetooth 5.4. Dual band integrated chips make the 5g WiFi and 2.4g WiFi more stable and the lastest bluetooth 5.4 connection supports all your favorite accessories, highly increased the speed of data transfer, improved network capacity and reduced network delays.
A minimal Eclipse verification checklist
- The stack trace names the class you actually searched for.
- No source file still imports Selenium’s retired AndroidDriver unless legacy pinning is deliberate.
- The JUnit launch configuration includes the dependency container at runtime.
- There is one coherent Selenium version rather than competing manually added JARs.
- The selected Appium driver matches native, hybrid, web or application testing needs.
- Java 11+ and Selenium 4.14.1+ are used when the project adopts Appium Java Client 9.
- The test runs against a reachable emulator/device and Appium server after the class-loading error is gone.
Common symptoms and precise fixes
“The JAR is in libs, but the error remains”
Confirm that Eclipse marks the folder as a library location and that the launch configuration includes it. Then verify the JAR truly contains the requested package. If it does not, adding more copies of the same JAR cannot create the class; migrate or obtain the exact historical artifact only when legacy compatibility is intentional.
The error appears only from Run As JUnit
Compare the JUnit configuration’s Classpath tab with the project’s Java Build Path. Delete and recreate the configuration if it references an old project output or a removed user library.
Changing Selenium versions produces a new linkage error
That usually indicates mixed Selenium modules or an Appium Java Client compatibility mismatch. Remove manually copied modules, refresh the build tool, and use the compatibility requirements for the chosen Appium client. Do not solve one missing class by downgrading unrelated libraries blindly.
The next error says a driver executable cannot be found
You have moved past Java class loading. Follow Selenium’s driver-management guidance for the executable-path problem, or complete the Appium server and device setup. It is not evidence that AndroidDriver has returned.
Rank #4
- 【Android 16 OS & High-Performance CPU】 Evermyth GMS-certified tablet runs on the Android 16 operating system, allowing direct downloads of popular apps from the Play Store. Powered by a robust 5-core processor that hits speeds up to 1.8GHz, the android tablet is engineered to boost multitasking performance. Whether you’re working, watching videos, or gaming, this 5-core tablet pc operates seamlessly, delivering a fast, professional-grade experience.
- 【24GB RAM + 64GB ROM + 1TB Expandable Storage】 Our 10 inch electronics tablets comes with 24GB RAM (3GB physical + 21GB virtual), 64GB ROM, and supports up to 1TB of expandable storage via a TF card (not included). This ensures quick app launches and smooth gameplay.
- 【10 inch HD IPS In-Cell Display】 This tablet PC boasts a 1280×800 high-resolution IPS screen that delivers vibrant, true-to-life colors. Enjoy sharper, brighter visuals for a more immersive viewing experience. The 5MP front and 8MP rear camera can handle video calls and photo recording with ease. LCD touchscreen uses low-blue-light tech to cut down on eye strain from screen flicker and harsh blue light. Slim and lightweight, this 10-inch tablet amps up immersion for all your favorite activities.
- 【6000mAh Rechargeable Battery】 Electronics tablets Packed with a 6000mAh battery and a low-power-consuming CPU, Evermyth 10 inch tablet offers up to 3 days of standby time and up to 8 hours of mixed usage—perfect for reading, streaming, or web browsing. Charging is a breeze via the USB-C port, making the tablet an ideal companion for both entertainment and work!
- 【Wi-Fi 6 & Bluetooth 5.4】 Evermyth Android 16 tablet features the latest Wi-Fi 6 and upgraded Bluetooth 5.4. It supports dual-band (5GHz/2.4GHz) Wi-Fi connectivity for stable, high-speed transfers. Bluetooth 5.4 ensures seamless compatibility with all your favorite accessories.
It fails after upgrading to Java 11
Check source and target levels, Eclipse’s selected JRE, and the build tool’s runtime separately. Java 11 satisfies the stated minimum for Appium Java Client 9, but an old test runner or plugin may impose its own constraint.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Reliability, performance and cost considerations
Keeping a retired driver can minimize immediate code changes but makes dependency retrieval, security updates and reproducibility harder. A supported Appium driver adds migration work yet gives you a documented target and a clearer upgrade path. Run a small smoke suite first, pin versions in source control, and record the device, Android version, Appium server and Java runtime used by CI.
Class-path diagnosis itself costs no device time: perform it before launching an emulator. Once the class loads, separate infrastructure failures from test failures by logging the Appium server URL, session capabilities and device identifier without exposing credentials.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Or skip the browser setup
If your Android or web test work also needs repeatable website screenshots, ScreenshotNeo provides a single HTTP capture endpoint instead of requiring you to maintain a browser harness. It accepts consent banners before capture and removes more than 60 known consent platforms, newsletter popups and chat widgets; each step can be disabled. Bot checks, blank pages, timeouts, failed loads and cache hits are not billed, and response headers identify the page verdict and billing status.
For a direct capture, see the ScreenshotNeo API documentation:
Best Value
- Do what you love, uninterrupted — 25% faster performance than the previous generation and is ideal for seamless streaming, reading, and gaming.
- High-def entertainment — A 10.1" 1080p Full HD display brings brilliant color to all your shows and games. Binge watch longer with 13-hour battery, 3 or 4 GB RAM, 32 or 64 GB of storage, and up to 1 TB expandable storage with micro-SD card (sold separately).
- Thin, light, durable — Tap into entertainment from anywhere with a lightweight, durable design and strengthened glass made from aluminosilicate glass. As measured in a tumble test, Fire HD 10 is 2.7 times as durable as the Samsung Galaxy Tab A8 (2022).
- Stay up to speed — Use the 5 MP front-facing camera to Zoom with family and friends, or create content for social apps like Instagram and TikTok.
- Ready when inspiration strikes — With 4,096 levels of pressure sensitivity, the Made for Amazon Stylus Pen (sold separately) offers a natural writing experience that responds to your handwriting. Use it to write, sketch in apps like OneNote, and more.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
The same request in Python:
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)
And in Node.js:
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
ScreenshotNeo also has an MCP server with take_screenshot, get_page_info and capture_pdf tools for Claude, Cursor and other MCP clients. Features include full-page lazy-image loading, CSS-selector element capture, device presets, retina scale, PDF controls, custom CSS and JavaScript, clicks, waits, request blocking, headers, cookies, user agents, authorization, timezone, geolocation, transparent backgrounds, resizing, chosen-TTL caching, signed links, asynchronous webhooks, bulk capture of up to 100 URLs per call, a usage API and an OpenAPI specification.
The Free plan includes 1,000 shots each month with no card; paid plans start at $5 for 3,000 shots. Create a free ScreenshotNeo account to try it.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →When to ask for more evidence
The historical report does not reveal the project’s Eclipse version, Java runtime, dependency declarations or launch configuration. If the checklist does not isolate the failure, collect the full stack trace, dependency tree, Eclipse Build Path and Run Configuration classpath, plus the exact JAR or build-tool declarations. Those details are required for a project-specific diagnosis; the old thread alone cannot establish its root cause.
Frequently Asked Questions
Can I fix this by adding the Android SDK to Eclipse?
Usually no. The missing name is a Java Selenium class, so adding an Android SDK path does not supply it. Inspect Selenium/Appium dependencies and the test launch classpath instead.
Which Appium driver should replace the old class for an Android website?
Appium documents UiAutomator2 for Android native, hybrid and web modes. Choose Espresso when the target is an Android application and that integration fits your test.
Does Appium Java Client 9 work with Java 8?
No. Its migration guide lists Java 11 as the minimum and says Selenium versions below 4.14.1 are unsupported with Java Client 9 or newer.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

