scratchfoundation / scratchfoundation/scratch-desktop
Windows: 32-bit installer doesn't clean up existing 64-bit application
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 426
- Forks
- 268
- Avg merge
- 16h 6m
- Merged PRs (30d)
- 25
Description
Expected Behavior
Installing a new copy of Scratch Desktop should remove any pre-existing copy in the same context (per-user or per-machine).
Actual Behavior
Installing a 32-bit build of Scratch Desktop (version 3.11 or higher) does not clean up an existing 64-bit build (versions from 3.7.0 to 3.10.4). Most noticeably, shortcuts may point to the older version even after installing the newer version.
Steps to Reproduce
For these steps, make sure to install "per machine" / "for all users"
- Install Scratch Desktop version 3.10.4 or lower (but not older than 3.7.0)
- Install the latest Scratch Desktop
- Check for
C:\Program Files\Scratch Desktop\Scratch Desktop.exeandC:\Program Files (x86)\Scratch Desktop\Scratch Desktop.exe.- Expected behavior: only one of those files should exist
- Actual behavior: both files exist
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Windows installer configuration responsible for per-machine installations and reproduce the 32-bit-over-64-bit upgrade sequence from the issue. Done means installing the newer build leaves only one Scratch Desktop executable under Program Files or Program Files (x86), with shortcuts no longer pointing to the older version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100