Launcher: Update fails after renaming .longshot_exefs and build folder #240

Open
opened 2026-11-21 20:54:08 +00:00 by BeanBot · 0 comments
Member

Reported on Discord

Launcher version

Launcher Nightly 148.

What happened

The reporter renamed .longshot_exefs to exefs so the update would start. The update then fails because it looks for a file under the previous nightly folder after the first step renames that folder to the new nightly name.

Expected

The update should use the existing game files without failing when the source build folder is renamed during the update.

Steps to reproduce

  1. Start an update from a build in a nightly folder.
  2. Rename .longshot_exefs to exefs for the update to start.
  3. The update's first step renames the old build folder to the new nightly folder name.
  4. The update fails while looking for the expected file in the old folder path.

Error

The reporter described the missing-file error as: no file at nigthly591/pack/something.smth is present.

Still unknown

Operating system confirmation, exact full path and file name, exact selected romfs/exefs paths, and launcher log. The reporter says no launcher log is needed; including one if available would help diagnose the failure.

LongshotLauncher #156 tracks the broader request to update without relinking the ROM. LongshotLauncher #207 fixed a related but distinct case where selected game-file paths inside a renamed build folder were stale; this report still occurs on Nightly 148 and involves the .longshot_exefs/exefs directory name as well as a missing path under the old folder name.

Reported on [Discord](https://discord.com/channels/1569849200047427645/1573796296459026613/1573796296459026613) ### Launcher version Launcher Nightly 148. ### What happened The reporter renamed `.longshot_exefs` to `exefs` so the update would start. The update then fails because it looks for a file under the previous nightly folder after the first step renames that folder to the new nightly name. ### Expected The update should use the existing game files without failing when the source build folder is renamed during the update. ### Steps to reproduce 1. Start an update from a build in a nightly folder. 2. Rename `.longshot_exefs` to `exefs` for the update to start. 3. The update's first step renames the old build folder to the new nightly folder name. 4. The update fails while looking for the expected file in the old folder path. ### Error The reporter described the missing-file error as: `no file at nigthly591/pack/something.smth is present`. ### Still unknown Operating system confirmation, exact full path and file name, exact selected `romfs`/`exefs` paths, and launcher log. The reporter says no launcher log is needed; including one if available would help diagnose the failure. ### Related [LongshotLauncher #156](https://git.magicbean.dev/MagicBeanDev/LongshotLauncher/issues/156) tracks the broader request to update without relinking the ROM. [LongshotLauncher #207](https://git.magicbean.dev/MagicBeanDev/LongshotLauncher/pulls/207) fixed a related but distinct case where selected game-file paths inside a renamed build folder were stale; this report still occurs on Nightly 148 and involves the `.longshot_exefs`/`exefs` directory name as well as a missing path under the old folder name.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/LongshotLauncher#240
No description provided.