The auto-update feature in the Stacker App fails to perform its intended function. When the automatic update option is enabled, the app should check for new versions upon launch and notify the user if an update is available. However, the system does not trigger any update check or alert, and manual updates are the only way to verify version changes.
Issue Description
When launching the Stacker App with auto-update enabled, the app does not perform a version check or display any notification about available updates. The expected behavior is that the app automatically queries the update server, compares the installed version with the latest release, and prompts the user to either download and install or skip the update. Currently, this process does not occur, and no feedback is provided to the user.
Environment
Property
Value
Application
SpikerSoft Stacker
Module
Auto-Update
Environment
Production
Platform
Desktop
Operating System
Windows 11
Version
v2026.10.08e
Device
Desktop
Preconditions
User has auto-update enabled in the app settings.
Steps to Reproduce
Open the Stacker App with auto-update enabled.
Observe that no update check or notification occurs.
Attempt a manual update — the app correctly prompts for update confirmation.
Compare behavior between automatic and manual update triggers.
Expected Result
The app should automatically check for updates on launch.
If a newer version exists, the user should receive a prompt to download and install or skip the update.
The system should log the update check in the console or update history.
Actual Result
No automatic update check occurs.
No visual or console feedback is provided.
Manual update works correctly, but auto-update does not trigger.
Evidence
Observed behavior during app launch with auto-update enabled.
Manual update prompt appears correctly, confirming update logic exists but is not triggered automatically.
Impact
Users may miss critical updates or bug fixes.
Reduces reliability of the auto-update feature.
Minor functional issue but significant for long-term maintenance.
Frequency
Always
Reproducibility
100%
Severity
Medium
Suggested Fix
Verify that the auto-update trigger is correctly initialized during app startup.
Ensure the update check function runs after user authentication or app load.
Add visual feedback (e.g., “Checking for updates…” message) to confirm the process.
Log update check results in the console for debugging and transparency.
## Summary
The **auto-update feature** in the **Stacker App** fails to perform its intended function. When the automatic update option is enabled, the app should check for new versions upon launch and notify the user if an update is available. However, the system does not trigger any update check or alert, and manual updates are the only way to verify version changes.
## Issue Description
When launching the Stacker App with **auto-update enabled**, the app does not perform a version check or display any notification about available updates. The expected behavior is that the app automatically queries the update server, compares the installed version with the latest release, and prompts the user to either **download and install** or **skip** the update. Currently, this process does not occur, and no feedback is provided to the user.
## Environment
| Property | Value |
|-----------|--------|
| Application | SpikerSoft Stacker |
| Module | Auto-Update |
| Environment | Production |
| Platform | Desktop |
| Operating System | Windows 11 |
| Version | v2026.10.08e |
| Device | Desktop |
## Preconditions
User has **auto-update** enabled in the app settings.
## Steps to Reproduce
1. Open the **Stacker App** with auto-update enabled.
2. Observe that no update check or notification occurs.
3. Attempt a manual update — the app correctly prompts for update confirmation.
4. Compare behavior between automatic and manual update triggers.
## Expected Result
- The app should automatically check for updates on launch.
- If a newer version exists, the user should receive a prompt to **download and install** or **skip** the update.
- The system should log the update check in the console or update history.
## Actual Result
- No automatic update check occurs.
- No visual or console feedback is provided.
- Manual update works correctly, but auto-update does not trigger.
## Evidence
- Observed behavior during app launch with auto-update enabled.
- Manual update prompt appears correctly, confirming update logic exists but is not triggered automatically.
## Impact
- Users may miss critical updates or bug fixes.
- Reduces reliability of the auto-update feature.
- Minor functional issue but significant for long-term maintenance.
## Frequency
Always
## Reproducibility
100%
## Severity
Medium
## Suggested Fix
- Verify that the **auto-update trigger** is correctly initialized during app startup.
- Ensure the update check function runs after user authentication or app load.
- Add **visual feedback** (e.g., “Checking for updates…” message) to confirm the process.
- Log update check results in the console for debugging and transparency.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
The auto-update feature in the Stacker App fails to perform its intended function. When the automatic update option is enabled, the app should check for new versions upon launch and notify the user if an update is available. However, the system does not trigger any update check or alert, and manual updates are the only way to verify version changes.
Issue Description
When launching the Stacker App with auto-update enabled, the app does not perform a version check or display any notification about available updates. The expected behavior is that the app automatically queries the update server, compares the installed version with the latest release, and prompts the user to either download and install or skip the update. Currently, this process does not occur, and no feedback is provided to the user.
Environment
Preconditions
User has auto-update enabled in the app settings.
Steps to Reproduce
Expected Result
Actual Result
Evidence
Impact
Frequency
Always
Reproducibility
100%
Severity
Medium
Suggested Fix