Packaging error while using setter method in blueprint

Hello! Every day I package my multiplayer game and test it with others but for some reason, today it returned me an error while packaging:

UATHelper: Packaging (Windows (64-bit)): Program.Main: AutomationTool exiting with ExitCode=25 (Error_UnknownCookFailure)
UATHelper: Packaging (Windows (64-bit)): BUILD FAILED PackagingResults:Error: Error Unknown Cook Failure

The reason for this error was a bit above in the log:

UATHelper: Packaging (Windows (64-bit)): Cook: LogInit:Display: LogBlueprint:Error: [Compiler WeaponBaseClass_BP] Error Can't connect pins  New Current Weapon  and  Self : PLACEHOLDER-CLASS  Weapon Base Class BP C 1 Reference is not compatible with Self Reference. from Source: /Game/blueprints/Weapons/WeaponBaseClass_BP.WeaponBaseClass_BP
UATHelper: Packaging (Windows (64-bit)): Cook: LogInit:Display: LogBlueprint:Error: [Compiler WeaponBaseClass_BP] Error Can't connect pins  Self  and  New Current Weapon : Self Reference is not compatible with PLACEHOLDER-CLASS  Weapon Base Class BP C 1 Reference. from Source: /Game/blueprints/Weapons/WeaponBaseClass_BP.WeaponBaseClass_BP

The thing is: I have two blueprint classes. First one is a character class, which has a “CurrentWeapon” variable, which holds the reference to the instance of a child class of my WeaponBaseClass. In my character class, there is a setter method that sets the “CurrentWeapon” variable with argument name “NewCurrentWeapon”. I use this setter in my weapon class. So when I connect the self-reference node to setter argument I get the error above (it wasn’t there until today), but when I manually set this variable from inside my weapon class it works just fine. Note that it also compiles fine while I am in the editor.

Ok so I managed to find a workaround: In that setter method, I now take the argument as an Actor class reference, instead of my custom WeaponBaseClass_BP, then inside setter, I use cast. The functionality was restored.
BUT THE BUG IS STILL PERSISTS!!! Please, Staff, address this bug.