Issue with lore "Lore project is not usable"

Summary

UEFN 43.10: Revision Control won’t connect for a team member. It says “Lore project is not usable… open the project as ‘DillyApp’” and offers no way to recover as your own account.

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Lore

Steps to Reproduce

  1. Collaborator A (account “DillyApp”) has the team project open locally with work that isn’t checked in. Their workspace is on their auto-created personal branch.
  2. The project folder, including its .lore workspace folder, is put on Collaborator B’s PC. B is a team member of the same project with their own Epic account.
  3. Collaborator B opens the project in UEFN 43.10 signed in with their own account.
  4. UEFN tries to connect Revision Control (Lore) while the project opens.

Expected Result

UEFN should recognise that the workspace belongs to another team member and give the signed-in user a working path. For example:

  • create a new personal branch / workspace for the current account,
  • or re-sync the project from main for this account,
  • or at least a button to switch the workspace safely without destroying the other member’s changes.

Revision Control should not be silently disabled for the whole project.

Observed Result

Revision Control fails and turns itself off. The output log shows:

Connection Error: The Lore repository is not usable right now.
The Lore project is not usable right now.
There are local changes from ‘DillyApp’ that have not been checked in.
To resolve this, please open the project as ‘DillyApp’ and either CHECK IN CHANGES or REVERT ALL.
The Lore repository is not usable right now.

After this:

  • “SourceControl: Revision control is disabled”. UEFN writes Provider=None to Saved/Config/WindowsEditor/SourceControlSettings.ini.
  • Reconnecting from the Revision Control Login window fails with the same error every time.
  • The editor offers no option except opening the project as the other account. The second team member can’t sign in as that account.
  • The lore command line still works for the same signed-in account (repository status and lock query succeed). So the account has access, and only the editor refuses the workspace.
  • While Revision Control is disabled, the editor lets you edit with no file locks or check-in. Teammates’ locks don’t protect anything, and work can be lost on

Platform(s)

Windows

Additional Notes

  • UEFN version 43.10 (43.10.60458657), Windows 11.
  • The project is a published live team project with several collaborators.
  • The workspace’s branch is a personal branch auto-created for the other collaborator. Its local and remote revisions match, so the “local changes” seem to be the other user’s personal-branch state rather than files edited on this PC.
  • The error message tells the user to sign in as someone else. That isn’t possible on a team, so the user is stuck with no supported fix inside the editor except downloading the whole project again.
  • Requests:
    • an in-editor option to start a fresh workspace / personal branch for the current account,
    • a clearer error that explains the workspace belongs to another account and how to get your own copy,
    • don’t permanently write Provider=None to the settings file after a failed connect.

@wouter Could you please check this asap

FORT-1197304 has been created and its status is ‘Unconfirmed’. This is now in a queue to be reproduced and confirmed.