Steps to reproduce:
- Install NVDA-2023.2;
- Install an add-on whose API version should be less than 2024.1.0, that is, compatible with 2023.2.
- Install the NVDA-alpha version (API version is 2024.1.0).
- Check the add-on status in the add-on store: Add-on installed in stap2 is disabled.
- Uninstall the NVDA Alpha version through the NVDA uninstaller in the control panel.
- Restart your computer and install NVDA-2023.2
- Check the add-on status in the add-on store.
Actual behavior:
Perform step 7: You will find that the status of the add-on is the same as step 4, that is, it is still disabled.
Expected behavior:
Add-on should be enabled.
When I tested using NVDA-2022.1 and NVDA2023.1, it performed as expected. So this could also be considered a regression.
Alternatives I Considered:
- When uninstalling NVDA, it ask to delete the user configuration.
- Ask user to delete legacy user configuration or reset add-on status when installing NVDA.
NVDA logs, crash dumps and other attachments:
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
NVDA-Alpha Version
Windows version:
Windows 10 22H2 (AMD64) build 19045.3393
Name and version of other software in use when reproducing the issue:
None
Other information about your system:
None
Other questions
Does the issue still occur after restarting your computer?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
When I tested using NVDA-2022.1 and NVDA2023.1, it performed as expected. So this could also be considered a regression.
If NVDA add-ons are disabled, is your problem still occurring?
n/a
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
n/a
Steps to reproduce:
Actual behavior:
Perform step 7: You will find that the status of the add-on is the same as step 4, that is, it is still disabled.
Expected behavior:
Add-on should be enabled.
When I tested using NVDA-2022.1 and NVDA2023.1, it performed as expected. So this could also be considered a regression.
Alternatives I Considered:
NVDA logs, crash dumps and other attachments:
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
NVDA-Alpha Version
Windows version:
Windows 10 22H2 (AMD64) build 19045.3393
Name and version of other software in use when reproducing the issue:
None
Other information about your system:
None
Other questions
Does the issue still occur after restarting your computer?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
When I tested using NVDA-2022.1 and NVDA2023.1, it performed as expected. So this could also be considered a regression.
If NVDA add-ons are disabled, is your problem still occurring?
n/a
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
n/a