Hey AvikB-
Thank you for submitting a bug report. I have reproduced this issue and logged a report for it here Unreal Engine Issues and Bug Tracker (UE-46610) . You can track the report’s status as the issue is reviewed by our development staff. Please be aware that this issue may not be prioritized or fixed soon.
Cheers
Hi , thanks. I will keep an eye on the bug.
Cheers. 
When i package my game and open it it crashes, throws this error. The game works fine in standalone and viewport and no errors in the output window. I have included the logs and crash files.
https://i.imgur.com/F8Kke4o.png
Log and crash files: https://1drv.ms/u/s!AshlE4zYrQfJxgdNiciU7nNZZHH7
UPDATE: After some testing i found it this is due to use of GEngine in the constructor.
https://i.imgur.com/0MWuYsv.png
Unfortunately i need to use it in constructor as i am creating widget using ConstructorHelper which freezes the Editor loading at 72%, unless there is better way ofc.
Here is the forum thread for more detail:
Hi . What exactly do you mean by project setup?
Hi . I’m not experiencing the error in the OP. I’m experiencing the error Fjellgnu posted. I tried to reproduce it in a blank project, but my main has so much going on I doubt I could narrow it down without more understanding of what this error means.
The only useful information I have is that this is definitely a 4.17 issue. I took an old build from my svn that I know for a fact compiles and runs successfully on 4.16, packaged it in 4.17, and I receive the same error upon launching my game.
I am getting something very similar with engine version 4.17.
Hey Fjellgnu-
Can you provide additional information about your setup? Are you using GEngine and constructor helpers in a class constructor? If not, can you provide the setup you’re using that causes this error for you?
I am getting the exact same error Fjellgnu mentioned in 4.17 as well. My project is entirely blueprints based and I have not modified any C++ files.
Hey-
Retesting the reproduction steps listed in the bug report, I was successfully able to open the packaged .exe file. If you are getting this message, can you provide the project setup you’re using in case there is another circumstance that causes this error.
Hi, you can find the steps here. It is how i got the bug to appear.
I haven’t tested the bug with 4.17 YET. i will probably do some test just to make sure.
Hey-
As AvikB mentioned, the reproduction steps originally used when reporting this issue can be found at the link provided. When testing these steps locally in 4.17 I did not receive the error message anymore.
By project setup, I mean what steps do you take from open the editor and create a new first person project to project crashes and window appears (first person project is just an example, please be sure to include what type of project you’re using).
If you have a project that can easily reproduce the behavior, could you provide a copy of that project for me to test locally? You can either attach a zip of the project here or send me a PM on the forums with a download link if you have any privacy concerns.
Can you link your forum profile please? I’ll give this a bit more of a look to see if I can figure out what’s going on, If I can’t narrow it down I’ll send it off to you later tonight/tomorrow.
This link looks broken, 
I’m running into the same issue now when I try and package my game too.
D/UE4: [2017.08.27-13.51.34:040][ 0]Assertion failed: Assertion failed: RecursionNotAllowed.Increment() == 1 [File:D:\Build++UE4+Release-4.17+Compile\Sync\Engine\Source\Runtime\CoreUObject\Private\Serialization\AsyncLoading.cpp] [Line: 4235]
try this link:
https://forums.unrealengine.com/privatemessage/new/14493
you need to be logged in.
yes you can send private message to . What link were you talking about?
Hey Avik,
This just takes me to the compose private message screen.
Look at the recipients list that it makes. Also fyi the current workaround to this bug is to disable nativization. So if you really need to package to test something you can do it that way for now.
Apologies, I skimmed over the conversation and thought was providing a link to a fix for the issue, I didn’t realise you were just asking for his profile.