SketchUp Extension Conflicts After Version Upgrade: NoMethodError and Migration Issues
After upgrading SketchUp, extensions throw NoMethodError or stop loading entirely. I cover the clean installation process, Ruby API compatibility checks, and the extension isolation method that identifies the culprit.

SketchUp Extension Conflicts After Version Upgrade: NoMethodError and Migration Issues
A user on the SketchUp Community forum reported that after updating to SketchUp 2024, several extensions stopped working — Shape Loader, Artisan, ClothWorks, FlexTools Component Browser, and 3DArc Studio all gave "NoMethodError" messages in the new extension error window. Another user reported losing all 2024 extensions after installing 2025, despite the two versions supposedly being independent with separate install and AppData folders. A third user had extension problems across both 2024 and 2025.
These are the three most common extension problems after a SketchUp version upgrade, and each has a different root cause and fix.
Problem 1: NoMethodError After Upgrade
When extensions throw "NoMethodError" after a SketchUp upgrade, it means the extension is calling a Ruby API method that no longer exists or has been renamed in the new SketchUp version. SketchUp's Ruby API changes with each major release — methods are deprecated, renamed, or removed.
Understanding the Error
The "NoMethodError" message in SketchUp's extension error window looks like:
Error: NoMethodError
undefined method `some_method_name' for #<SomeClass:0x0000000>
This means the extension is trying to call some_method_name on an object of SomeClass, but that method doesn't exist in the current SketchUp Ruby API.
Fix 1: Check for Extension Updates
- Open Extensions → Extension Manager
- For each broken extension, note the developer name
- Visit the developer's website or the Extension Warehouse page
- Check if a newer version is available that supports your SketchUp version
- Download and install the updated version
Most active extension developers release compatibility updates within weeks of a new SketchUp version. If no update is available, the extension may be abandoned.
Fix 2: Contact the Extension Developer
If no update is available on the Extension Warehouse:
- Find the developer's contact information on the extension's Extension Warehouse page
- Send a message describing the NoMethodError, including:
- The exact error message
- Your SketchUp version
- Your operating system
- Many developers will provide a fix or a beta version
Fix 3: Find Alternative Extensions
If the developer is unresponsive or has abandoned the extension:
- Search the Extension Warehouse for extensions with similar functionality
- Check the SketchUp Community forum for recommendations
- Look for open-source alternatives on GitHub
Fix 4: Don't Force-Load Incompatible Extensions
Never modify extension code to bypass NoMethodError. The error means the extension is trying to do something the API no longer supports. Forcing it to load can corrupt your model or crash SketchUp. If an extension is incompatible, leave it disabled until an update is available.
Problem 2: Lost All Extensions After Installing New Version
A user reported: "I installed 2025 a couple of days ago to try out some of the new features. My understanding is that it's completely independent from 2024 and has separate install and appdata folders. I opened and closed both of them repeatedly without issue. Then I spent 2 days not using Sketchup at all and on the next launch, all extensions were gone."
Root Cause: Extension Migration Failure
When you install a new SketchUp version, it offers to migrate extensions from the previous version. This migration copies extension files from the old Plugins folder to the new one. The migration can fail silently if:
- The old Plugins folder has permission issues
- Extension files are locked by another process
- The migration script encounters an unexpected file format
- The user skips the migration dialog
Fix 1: Manually Copy Extensions
- Close both SketchUp versions
- Navigate to the old version's Plugins folder:
- Windows:
%AppData%\SketchUp\SketchUp 2024\Plugins\ - Mac:
~/Library/Application Support/SketchUp 2024/Plugins/
- Windows:
- Navigate to the new version's Plugins folder:
- Windows:
%AppData%\SketchUp\SketchUp 2025\Plugins\ - Mac:
~/Library/Application Support/SketchUp 2025/Plugins/
- Windows:
- Copy all files and folders from the old Plugins folder to the new one
- Restart SketchUp 2025
- Go to Extensions → Extension Manager and verify extensions are loaded
Fix 2: Reinstall Extensions Fresh
If manual copying doesn't work:
- Close SketchUp
- Delete the contents of the new version's Plugins folder
- Open SketchUp
- Go to Extensions → Extension Warehouse
- Search for each extension and install it fresh
- This ensures you get the latest version compatible with your SketchUp version
Fix 3: Check Extension Licensing
Some extensions require re-activation after migration:
- Open the extension's settings or about dialog
- Check if a license key is required
- Enter your license key (you may need to deactivate on the old version first)
- Some extensions use machine-specific licensing — contact the developer if re-activation fails
Problem 3: Extensions Causing Startup Crashes
When extensions cause SketchUp to crash at startup, you may not be able to access the Extension Manager to disable them.
Fix 1: Safe Mode (Shift+Launch)
- Hold down Shift while launching SketchUp
- SketchUp shows a dialog asking if you want to disable extensions
- Click Yes to skip extension loading
- SketchUp opens without any extensions
- Go to Extensions → Extension Manager
- Disable all extensions
- Restart SketchUp normally
- Re-enable extensions one at a time, restarting after each
- When SketchUp crashes after enabling a specific extension, that's the culprit
Fix 2: Rename the Plugins Folder
If Safe Mode doesn't work:
- Close SketchUp
- Navigate to:
%AppData%\SketchUp\SketchUp 2025\Plugins\ - Rename the folder to
Plugins_disabled - Create a new empty
Pluginsfolder - Start SketchUp — it should open without extensions
- Copy extensions from
Plugins_disabledtoPluginsone at a time - Restart SketchUp after each copy to identify the problematic extension
Fix 3: Check the Ruby Console
- Open SketchUp with extensions disabled (Safe Mode)
- Go to Window → Ruby Console
- Enable one extension in the Extension Manager
- Restart SketchUp with the Ruby Console open
- Watch the console for error messages during extension loading
- The error message will identify which extension is failing and why
Preventing Extension Conflicts in the Future
Before Upgrading SketchUp
- Document your extensions: Take a screenshot of the Extension Manager showing all installed extensions and their versions
- Check compatibility: Visit each extension's Extension Warehouse page and check compatibility with the new SketchUp version
- Wait 2-4 weeks: Don't upgrade on day one. Wait for extension developers to release compatibility updates
- Keep the old version installed: SketchUp allows multiple versions to coexist. Keep the old version until all extensions work in the new one
After Upgrading SketchUp
- Don't migrate extensions automatically: Skip the migration dialog and install extensions fresh
- Install one at a time: Install extensions one by one, testing SketchUp after each installation
- Test on a copy: Before using the new version on production files, test with a copy of your project
Managing Extension Dependencies
Some extensions depend on other extensions or shared libraries:
- Check the extension's documentation for dependencies
- Install dependencies first, then the dependent extension
- Common dependencies:
- SketchUp Extensions Platform: Required by many extensions
- TT_Lib2: Required by many ThomThom extensions
- LibFredo6: Required by all Fredo extensions
- If a dependent extension fails, check if its dependency is installed and up to date
Summary
| Problem | Root Cause | Fix | |---------|-----------|-----| | NoMethodError after upgrade | Ruby API method removed/renamed | Update extension, contact developer, or find alternative | | Lost extensions after new version | Migration failure | Manually copy Plugins folder or reinstall fresh | | Startup crashes from extensions | Incompatible extension loading at startup | Safe Mode (Shift+launch), rename Plugins folder, check Ruby Console | | Extension dependency failures | Missing or outdated shared library | Install dependencies first, check documentation |
The most important preventive measure is to wait 2-4 weeks after a new SketchUp release before upgrading. This gives extension developers time to release compatibility updates. When you do upgrade, install extensions fresh rather than migrating — you'll get the latest compatible versions and avoid migration-related issues.
Source Verification
More Sketchup Guides
troubleshooting
SketchUp 2025 Crashes on Startup: Graphics Engine Switch and Extension Isolation
9 min
troubleshooting
SketchUp 3D Warehouse Slow Downloads: WebCache Clear and Materials Palette Workaround
8 min
troubleshooting
SketchUp Inferencing Stops Working: Cursor Not Snapping to Corners and Guidelines
7 min
performance
SketchUp Large Model Performance: Edge Count, Tags, and 3D Warehouse Bloat
10 min
performance
SketchUp LayOut Slow Viewport Updates: Raster Mode, Edge Reduction, and Auto-Render
9 min
Related Troubleshooting Guides
Similar troubleshooting content for other CAD tools
3ds Max
•troubleshooting
3ds Max FBX and OBJ Import: Missing Materials, Broken UVs, and Texture Path Recovery
11 min
3ds Max
•troubleshooting
3ds Max Plugin DLL Errors: Missing Files, Load Failures, and plugin.ini Repair
9 min
3ds Max
•troubleshooting
3ds Max Random Crashes: Memory, Driver, and Crash Log Analysis Guide
10 min
Altium Designer
•troubleshooting
Fixing Altium Designer DRC Errors: Common Clearance and Routing Violations
9 min