Why would BlueprintImplementableEvent not work on Mobile?

Development Platform & Builds Mobile
, , ,
1

I’ve implemented a BlueprintImplementableEvent on my custom actor.

UFUNCTION(BlueprintImplementableEvent, Category = AOE)
void OnInitialize(); //virtual doesn't work either

I call it like this

this->OnInitialize(); //doesn't work with "this" either

It works perfectly every time in the editor & mobile preview. But when I run it on my device it doesn’t get called?

I put a debug message before I call it like this

      GEngine->AddOnScreenDebugMessage(-1, 5.f, FColor::Yellow, TEXT("Initialize"));
       this->OnInitialize();

And it displays in the editor and on the device.

I also added a “Print String” node to the blueprint event and disconnected the rest for testing.
This message appears in the editor as expected but does not appear on the device.

6321-blueprintevent.png

I have no idea why the event wont get called on mobile?

Edit: I should also add that I’ve implemented other BlueprintImplementableEvents in another class and they work just fine. And I know the actor in question here is working as I can see it in-game and it’s effects (it’s an area of effect which has a static mesh and damages enemies OnTick)

2

Really desperate here. Tried moving it to another class for the sake of it. But it’s just not getting called on the device (and still works perfectly in the editor). I am literally out of ideas, is it broken?

3

Hi DannRees,

I sincerely apologize for not responding sooner. What version of the Engine are you using, and are you using one that you built from source code, or installed by the Launcher?

Are you able to make this happen using one of the project templates? If so, could you please let me know exactly how you set everything up so that I can reproduce the issue here?

In your other post on this issue, you mentioned you were trying to make this work on a Galaxy S4. Have you tried reproducing the issue on a different Android device?

4

Hi DannRees,

We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will offer further assistance.

Thank you.