Mod Publisher - Update Mod Crashes game

I tried several times to upload my mod, most of the time game crashes.

At one time I thought it was due to PROFANITY FILTER being overaggressive and reporting problems anytime I even try to mention my nickname in mod Woprok or Woprock ingame. As a side note can we do something with it ? It’s really annoying to not be able to use it… but I can deal with it as I don’t believe it will ever get addressed to not report everything that just touches bad words in random language I don’t even understand.

Anyway even after fixing problems with profanity filter stopping upload, problem remains. Game crashes whenever I try to update my mod ADVANCED GAME SETTINGS during the Finalizing update…

Good to mention that game crashes even when profanity filter is supposed to stop the upload. So I had to try at least 5 - 10 times to even get profanity filter report…

Part of the issue might be localization as I provided another localization for the mod, but It crashed even without it…

Last possible problem could be that someone uploaded copy of my mod built from repository files, but I cant do anything with that…

whole mod is at github, exact version that has the problem and is up to date…

Can this be looked into and solved ? It’s unacceptable for a game to crash on upload action.
At the moment I was able to upload it after like 10 tries… Thats half an hour of time wasted watching single bar progressing and crashing.

I looked at logs, but all I found was unhandled_date.txt files

-- Log file for all messages not properly caught --

22:00:11.573   WorldwideAutomatch2Service::OnHostComplete - we're not polling at the moment, ignoring
22:00:29.339   NetworkManagerInternal::FlushJobs - flushing remaining (1) dynamic jobs:
22:00:29.339   Dynamic job SetDataAsync still running
22:00:29.667   NetworkManagerInternal waited 328 ms for async jobs to complete successfully
22:00:29.667   NetworkManagerInternal::FlushJobs - flushing remaining (1) dynamic jobs:
22:00:29.667   Dynamic job LogoutAsync still running
22:00:34.670   AsyncJobDriver::~AsyncJobDriver() - dynamically allocated job SetDataAsync is still running
22:00:34.680   AsyncJobDriver::~AsyncJobDriver() - dynamically allocated job HttpRequestAsync is still running
22:00:34.989   Unloading step: [Additional crash information]
-- Log file for all messages not properly caught --

22:11:32.260   NetworkManagerInternal waited 0 ms for async jobs to complete successfully
22:11:32.260   NetworkManagerInternal::FlushJobs - flushing remaining (1) dynamic jobs:
22:11:32.260   Dynamic job LogoutAsync still running
22:11:37.265   AsyncJobDriver::~AsyncJobDriver() - dynamically allocated job SetDataAsync is still running
22:11:37.665   Unloading step: [Additional crash information]
-- Log file for all messages not properly caught --

22:12:23.175   WorldwideAutomatch2Service::OnHostComplete - we're not polling at the moment, ignoring
22:13:07.651   NetworkManager::DispatchEvents() - Warning - Time between calls was 3009 ms
22:14:18.987   SessionManager::Process() - Warning - Time between calls was 2969 ms, time waiting for lock was 0 ms

Best thing to do here would be to contact support—please make sure to include your warnings.log file after you experience a crash. Sorry to hear you are experiencing this, but any information you can provide will be super helpful. Thanks!