Unable to Publish Island Update - Verse Error, Failed In-Island Transactions

Summary

We have never made in-island transactions on our map yet that is what the error is suggesting we’re failing. We are able to compile verse, successfully run a memory test, but can’t publish our build because the verse check is failing on what we assume is the in-island transaction check.

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Publishing

Steps to Reproduce

  1. Make a new private build of our map
  2. Creator Portal shows the In-Island Transactions check fails, even though we have no in-island transactions.

Expected Result

We expect no error

Observed Result

It fails, and prevents us from being able to publish

Platform(s)

PC

Island Code

7627-8175-3618

Upload an image


hi @OKomili

This has been a problem look at my post

[Solved] UEFN Feature Example In-Island Transactions , fake experimental Scene Graph error

This is from the Feature Example

and the documentation on

In Island Transactions in Fortnite | Fortnite Documentation | Epic Developer Community

Posts about documentation problems

In Island Transactions Documentation Not Consistent? - General / Feedback & Requests - Epic Developer Community Forums

In-Island Transaction documentation Verse Handling Payment different from Example - General / Issues and Bug Reporting - Epic Developer Community Forums

Hi Jimbo,

Thanks for the suggestion, I looked at our headers and nowhere do we reference the Marketplace library either so unfortunately that’s not the problem.

Someone at Epic pinged me on Discord when I asked her for help and she pointed me to something about a cook error. It seems our build was actually failing at the cook stage, even though all warnings on the Fortnite Creator Portal was what you see in my post above. This seems like it was a bug with the Creator Portal itself, presenting the wrong error.

There’s also a mismatch in behaviour between the private build cook validation test and the cook that occurs when making a local build to test. I verified this because I reverted my local build to our most recent public build that we successfully published on Friday February 27th, and that one still fails took cook when making a new private build. The issue had to do with us defining an abstract class and it claiming it would cause a runtime error. We removed the abstract specifier and we were finally able to make a build that succeeded. My assumption is something changed with the latest hotfix from earlier in the week that changes behaviour, but it’s only reflected on private build cooks, not local.

Hopefully that makes sense.

1 Like

I just clicked the link you posted and realized you were suggesting it’s more than the Marketplace lib reference error. Interesting. I will investigate and see if those changes help.

1 Like