# Trying to access a property causes blueprint runtime error

**URL:** <https://forums.unrealengine.com/t/trying-to-access-a-property-causes-blueprint-runtime-error/354842>\
**Category:** C++\
**Tags:** UE4-11, unreal-engine, bug-report, UE4, Blueprint, CPP, question\
**Created:** [April 20, 2016, 3:21pm UTC](https://forums.unrealengine.com/t/trying-to-access-a-property-causes-blueprint-runtime-error/354842 "2016-04-20T15:21:16Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![oristal](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@oristal](https://forums.unrealengine.com/u/oristal)\
**Post date:** [April 20, 2016, 3:21pm UTC](https://forums.unrealengine.com/t/trying-to-access-a-property-causes-blueprint-runtime-error/354842/1 "2016-04-20T15:21:16Z")

</div>

Sorry for double posting, I’ve already posted my issue [here][1] but managed to reproduce it in a project from scratch and think it’s really a bug and not something from my code. Here’s what I did:

- Create a third person BP project

- Create a c++ class, let’s call it Room, with a FString property like this:

- Create a blueprint that inherits from this class, place it in the scene

- In the third person BP, try to display the room name like this

 ![87665-bug_report.png](https://d3kjluh73b9h9o.cloudfront.net/original/4X/1/2/3/123138ab21c6948790fe3e276de3874d5be11b8a.png)

- Launch the game, press H, the room name is displayed

- Edit the code to add a comment just above the UPROPERTY

- Compile, launch, press H, the errors are displayed.

Am I the only one having this issue? I hope you guys can reproduce it and fix it. 🙂

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![Shadowriver](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Shadowriver](https://forums.unrealengine.com/u/Shadowriver)\
**Post date:** [April 20, 2016, 3:56pm UTC](https://forums.unrealengine.com/t/trying-to-access-a-property-causes-blueprint-runtime-error/354842/2 "2016-04-20T15:56:16Z")

</div>

This is not corruption, it’s hotreload not being perfect it messes up property data and as you notice already you need to restart editor so all modules are loaded properly. But it’s still a bug

---

<div class="post-metadata">

**Author:** ![oristal](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@oristal](https://forums.unrealengine.com/u/oristal)\
**Post date:** [April 20, 2016, 5:26pm UTC](https://forums.unrealengine.com/t/trying-to-access-a-property-causes-blueprint-runtime-error/354842/3 "2016-04-20T17:26:25Z")

</div>

Is there a way to force hotreload without restarting the editor? I can’t restart it every time I want to compile my code. What’s weird is that it never happened before we updated to 4.11.

Thanks for confirming the bug tho

---

<div class="post-metadata">

**Author:** ![Shadowriver](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Shadowriver](https://forums.unrealengine.com/u/Shadowriver)\
**Post date:** [April 20, 2016, 11:54pm UTC](https://forums.unrealengine.com/t/trying-to-access-a-property-causes-blueprint-runtime-error/354842/4 "2016-04-20T23:54:55Z")

</div>

hotreload when you compile with editor turned on end editor swaps old version of you module with new one, it is not perfect and sometimes act wierd. What you did here is updating reflection data and it seems it’s not doing it right, so restart when you edit header files if you update code in cpp hotreload should be ok. Simply if something behaves odd try restarting. And as said it’s still a bug and it probably know because you not first reporting this.

---

<div class="post-metadata">

**Author:** ![oristal](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@oristal](https://forums.unrealengine.com/u/oristal)\
**Post date:** [April 21, 2016, 11:35am UTC](https://forums.unrealengine.com/t/trying-to-access-a-property-causes-blueprint-runtime-error/354842/5 "2016-04-21T11:35:42Z")

</div>

I hope they release a fix soon, thanks for the info

---

<div class="post-metadata">

**Author:** ![anonymous\_user\_2b03d27c](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_2b03d27c](https://forums.unrealengine.com/u/anonymous_user_2b03d27c)\
**Post date:** [April 21, 2016, 1:29pm UTC](https://forums.unrealengine.com/t/trying-to-access-a-property-causes-blueprint-runtime-error/354842/6 "2016-04-21T13:29:51Z")

</div>

Hey oristal-

There is a difference in the behavior between the 4.10 and 4.11 engine version. I have entered a bug report about the error message you received (UE-29768) for further investigation. Rather than having to restart the editor, I found that compiling the blueprint with the reference (in your case the character) will update the blueprint and print the name as expected.

Cheers

---

<div class="post-metadata">

**Author:** ![oristal](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@oristal](https://forums.unrealengine.com/u/oristal)\
**Post date:** [April 22, 2016, 8:14am UTC](https://forums.unrealengine.com/t/trying-to-access-a-property-causes-blueprint-runtime-error/354842/7 "2016-04-22T08:14:47Z")

</div>

Thanks a lot for acknowledging this behavior! I’m fine with re-compiling the blueprint for the moment, it’s not as bad as I thought 🙂

---

<div class="post-metadata">

**Author:** ![RyanGPalmer](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@RyanGPalmer](https://forums.unrealengine.com/u/RyanGPalmer)\
**Post date:** [April 22, 2016, 8:34am UTC](https://forums.unrealengine.com/t/trying-to-access-a-property-causes-blueprint-runtime-error/354842/8 "2016-04-22T08:34:31Z")

</div>

Also experienced this issue in my project. Thank you for this temporary solution!

---

<div class="post-metadata">

**Author:** ![kubas1129](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@kubas1129](https://forums.unrealengine.com/u/kubas1129)\
**Post date:** [April 7, 2018, 8:50pm UTC](https://forums.unrealengine.com/t/trying-to-access-a-property-causes-blueprint-runtime-error/354842/9 "2018-04-07T20:50:17Z")

</div>

Actually I still have this problem, but if you want to fix this you can create getter/setter for value you get/set. It’s not the best solution but it fixes hot\_reload bug.

---

<div class="post-metadata">

**Author:** ![Shmann](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Shmann](https://forums.unrealengine.com/u/Shmann)\
**Post date:** [July 6, 2018, 8:36pm UTC](https://forums.unrealengine.com/t/trying-to-access-a-property-causes-blueprint-runtime-error/354842/10 "2018-07-06T20:36:23Z")

</div>

Can you send me a screenshot with the solution?

---

<div class="post-metadata">

**Author:** ![Herr\_Edgy](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/herr_edgy/32/924115_2.png) [@Herr\_Edgy](https://forums.unrealengine.com/u/Herr_Edgy)\
**Post date:** [June 4, 2019, 12:42pm UTC](https://forums.unrealengine.com/t/trying-to-access-a-property-causes-blueprint-runtime-error/354842/11 "2019-06-04T12:42:36Z")

</div>

Bump. This error persists in 4.22 still and the logged error is still marked unresolved.

In my case, I import new data assets via C++ compilation and consolidate objects to clean up, then fix up references. Due to the compiling via hot reload, blueprint classes that make use of the new, consolidated data assets don’t work unless recompiling manually (no compile error beforehand though) or restarting the editor due to “missing properties”.

---

<div class="post-metadata">

**Author:** ![kubas1129](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@kubas1129](https://forums.unrealengine.com/u/kubas1129)\
**Post date:** [June 4, 2019, 3:24pm UTC](https://forums.unrealengine.com/t/trying-to-access-a-property-causes-blueprint-runtime-error/354842/12 "2019-06-04T15:24:11Z")

</div>

It’s very simple, if you have for example code like this:

```
//declararation of variable
UPROPERTY(EditAnywhere, BlueprintReadWrite,Category = "MyCategory")
int someVar;

//get 
UFUNCTION(BlueprintCallable)
int getSomeVar() const { return someVar; } 

//set 
UFUNCTION(BlueprintCallable)
void setSomeVar(int var) { someVar = var; }

```

It should work after compile.

---

<div class="post-metadata">

**Author:** ![SOuNDSNC](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@SOuNDSNC](https://forums.unrealengine.com/u/SOuNDSNC)\
**Post date:** [June 22, 2019, 2:44am UTC](https://forums.unrealengine.com/t/trying-to-access-a-property-causes-blueprint-runtime-error/354842/13 "2019-06-22T02:44:27Z")

</div>

I’m getting this error and the properties are defined in blueprint. Not sure what to make of it, other than maybe that the blueprint is in the process of being destroyed?  
UE 4.21

---

<div class="post-metadata">

**Author:** ![J\_McBride](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@J\_McBride](https://forums.unrealengine.com/u/J_McBride)\
**Post date:** [June 24, 2019, 6:37pm UTC](https://forums.unrealengine.com/t/trying-to-access-a-property-causes-blueprint-runtime-error/354842/14 "2019-06-24T18:37:23Z")

</div>

Confirming that we are also dealing with this issue. Yes, it is resolved by restarting the editor, but this is definitely hindering our development process as we have to to restart the editor once this bug appears.

---

<div class="post-metadata">

**Author:** ![Herr\_Edgy](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/herr_edgy/32/924115_2.png) [@Herr\_Edgy](https://forums.unrealengine.com/u/Herr_Edgy)\
**Post date:** [June 26, 2019, 10:07am UTC](https://forums.unrealengine.com/t/trying-to-access-a-property-causes-blueprint-runtime-error/354842/15 "2019-06-26T10:07:58Z")

</div>

Yes, I hope Epic will look into this. Since the bug has quite a few votes and is still unresolved, maybe we should just submit more individual bug reports about this to make a statement on how problematic it is in the long run. The plugin I’m working on for a company right now forces the user to restart the engine upon reimporting data. That’s not because the data doesn’t get reimported, that works nicely, but the blueprints accessing said data just stop working if we don’t force the user to do that.

Users want easily accessible solutions, not some tech mumbo jumbo explaining they have to recompile their affected blueprints. A forced restart is easier, but at the same time shouldn’t be necessary in the first place.

---

<div class="post-metadata">

**Author:** ![Alfheimrer](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Alfheimrer](https://forums.unrealengine.com/u/Alfheimrer)\
**Post date:** [July 2, 2019, 11:59am UTC](https://forums.unrealengine.com/t/trying-to-access-a-property-causes-blueprint-runtime-error/354842/16 "2019-07-02T11:59:34Z")

</div>

Fix this annoying bug, it’s driving me crazy.  
I have to manually recompile every ■■■■■■■ BP.

---

<div class="post-metadata">

**Author:** ![smt](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@smt](https://forums.unrealengine.com/u/smt)\
**Post date:** [July 12, 2019, 12:59am UTC](https://forums.unrealengine.com/t/trying-to-access-a-property-causes-blueprint-runtime-error/354842/17 "2019-07-12T00:59:38Z")

</div>

we’re getting this on 4.22.3 too, for me compiling the related blueprints seems to fix this until another hot reload

---

<div class="post-metadata">

**Author:** ![Barrett1207](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Barrett1207](https://forums.unrealengine.com/u/Barrett1207)\
**Post date:** [July 23, 2019, 2:43pm UTC](https://forums.unrealengine.com/t/trying-to-access-a-property-causes-blueprint-runtime-error/354842/18 "2019-07-23T14:43:03Z")

</div>

I am still getting this bug as well in version 4.22

---

<div class="post-metadata">

**Author:** ![Navhkrin](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Navhkrin](https://forums.unrealengine.com/u/Navhkrin)\
**Post date:** [August 19, 2019, 2:17pm UTC](https://forums.unrealengine.com/t/trying-to-access-a-property-causes-blueprint-runtime-error/354842/19 "2019-08-19T14:17:57Z")

</div>

Getting this on 4.22.3 aswell

---

<div class="post-metadata">

**Author:** ![Navhkrin](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Navhkrin](https://forums.unrealengine.com/u/Navhkrin)\
**Post date:** [September 28, 2019, 10:11am UTC](https://forums.unrealengine.com/t/trying-to-access-a-property-causes-blueprint-runtime-error/354842/20 "2019-09-28T10:11:07Z")

</div>

4.23 , Issue still persists

[Next page](https://forums.unrealengine.com/t/trying-to-access-a-property-causes-blueprint-runtime-error/354842.md?page=2)
