Skip to content

Fix add-on failing to load on NVDA alpha: config.isAppX was removed - #63

Closed
serrebidev wants to merge 5 commits into
nvda-es:masterfrom
serrebidev:fix-isappx-removed
Closed

serrebidev wants to merge 5 commits into
nvda-es:masterfrom
serrebidev:fix-isappx-removed

Conversation

@serrebidev

@serrebidev serrebidev commented Sep 29, 2026 •

Copy link
Copy Markdown
Contributor

NVDA alpha (2027.1 dev, tested on alpha-57943) removed config.isAppX along with Windows Store support. Reading it raises AttributeError from config.__getattr__, so GlobalPlugin.__init__ fails and the add-on never loads:

Error initializing global plugin <class 'globalPlugins.updateChannel.GlobalPlugin'>
  ...
AttributeError: module 'config' has no attribute 'isAppX'

This reads the flag with getattr(config, "isAppX", False) in addon/globalPlugins/updateChannel.py. Older NVDA versions keep the Store check exactly as before; newer ones treat the missing flag as "not a Store build", which is what it means now that Store builds no longer exist.

Verified: with this change installed, the add-on loads on alpha-57943 and the error is gone from the NVDA log.

🤖 Generated with Claude Code

serrebidev and others added 5 commits September 26, 2026 10:35
The hourly check failed every run with no changes because
`git commit` exits non-zero on an empty commit. Only commit
and push when `git diff --cached` shows staged changes.

Co-authored-by: Mark <mark@muse.ai>
NVDA alpha (2027.1 dev) removed config.isAppX along with Windows Store
support. Accessing it raises AttributeError from config.__getattr__, so
GlobalPlugin.__init__ fails and the add-on does not load:

  AttributeError: module 'config' has no attribute 'isAppX'

Read it with getattr(..., False) so older NVDA keeps the Store check and
newer NVDA treats the missing flag as "not a Store build".

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@jmdaweb

jmdaweb commented Sep 29, 2026

Copy link
Copy Markdown
Member

Hi,
Your proposed change requires modifying exactly one line, but I see 5 commits with 5 files changed and a download link pointing to the latest add-on release on your repository. To complete the picture, the pr has merge conflicts. Could you please open a new pull request which includes only this change? Otherwise, if you rely on AI tools and don't code yourself, let me know and I'll make the change for you.
Regards.

@serrebidev

Copy link
Copy Markdown
Contributor Author

Hi,
Thanks, and sorry for the noise. The extra commits came from my fork, not from this fix. I opened #64, which is based on current master and changes only that one line. Closing this one in favour of it.
Regards.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants