Trying to Install Embark Addon v1.7.0 to Blender 2.90.1

[firebert85]

Describe the bug
A clear and concise description of what the bug is.

After installing the addon, when I try to click and Enable v1.7.0 of the addon, I receive the following error:

Traceback (most recent call last):
File "C:\Program Files\Blender Foundation\Blender 2.90\2.90\scripts\modules\addon_utils.py", line 382, in enable
mod.register()
File "C:\Users\evans\AppData\Roaming\Blender Foundation\Blender\2.90\scripts\addons\blender-tools-main_init_.py", line 37, in register
register_recursive(REGISTER_CLASSES)
File "C:\Users\evans\AppData\Roaming\Blender Foundation\Blender\2.90\scripts\addons\blender-tools-main\utils_init_.py", line 60, in register_recursive
register_recursive(obj.REGISTER_CLASSES)
File "C:\Users\evans\AppData\Roaming\Blender Foundation\Blender\2.90\scripts\addons\blender-tools-main\utils_init_.py", line 56, in register_recursive
bpy.utils.register_class(obj)
ValueError: register_class(...): already registered as a subclass 'EmbarkAddonPreferences'

To Reproduce
Steps to reproduce the behavior:

1. Go to Addons
2. Click Install, and select from disk the latest 1.7.0 zip file of the Embark Addon
3. Click Enable checkbox for addon
4. See error

Expected behavior
Addon to install with no error message.

Screenshots

Device:

• Windows 10
• Blender Version 2.90.1

Additional context
n/a

[moppius]

@firebert85 Hmm, did you already have a version of the plugin installed before trying to install this one?

It looks like it's trying to register the same thing twice. can you check your %APPDATA%\Blender Foundation\Blender\2.90\scripts\addons folder (paste that path into Windows Explorer) and make sure you don't already have an old version of the plugin installed there?

If there is already a embark_blender_tools folder in your addons folder, you'll need to delete that before installing the new one.

I just tried installing the 1.7.0 version of the plugin on Blender 2.90.1 and it worked fine on my end, so I suspect you may have a duplicate of the plugin or an old version already installed.

Please let me know what you find!

[firebert85]

@moppius
Trying this again on the new 2.91 release, and still get the attached error message every time I try to click the Activate check box
This happens no matter how many times I remove the addon from within Blender and make sure the scripts/addons folder in 2.91 folder is deleted.

[firebert85]

This is a new one--I just got this error message after another complete clean remove/delete from the //scripts/addons folder, and attempted to click Activate

Every subsequent click of the Activate checkbox returns the previous error message.

[firebert85]

For whatever reason--I just went to install this and so far it works.

[moppius]

Weirdly, I did manage to reproduce this once the other day - I think there is a race condition in registering modules and the update operator, I have a potential fix for it that I'm testing locally.

Thanks for following up!

[moppius]

Closing this for now, will see if anyone else hits it after the speculative fix in release 1.7.1.