Error in Unreal engine MacOS shipping build

Hi,
I’m trying to package my project for MacOS and while it works in development packages. It displays “Error! Contact support or check logs.” on the dialoge window when packaged in shipping. the problem is i can’t check logs in a shipping build and it works in a development build.

I already had to do this fix : Mac mic fix

My setup :
Unreal engine 5.4
imac 2021 m1 chip

already successfully packaged on windows.

Is there any way to check what causes this error in a shipping build or is there something i have to do to make it work in shipping?

Hi @jules, thank you for reaching out,

Even when the app is in shipping mode, we still retain certain logs related to Convai. Could you please check your app directory for a folder named ConvaiLogs? should be under the Saved folder. Inside, you should find all the logs related to Convai, which will hopefully provide some clues about the issue.

I don’t have a folder named ConvaiLogs or Saved in my app directory.

I see, this might be because you’re using the latest plugin from the marketplace which do not yet have this type of logging enabled, we will be pushing the new updated plugin over the next 2 weeks, once updated you will be able to view these logs and it will help us identify the issue.

If you would like to install the latest plugin manually, you will need to convert your project to c++ and follow these steps

  • Uninstall the Convai plugin from the Epic Launcher.
  • Download the latest release from here.
  • Extract the plugin inside your project/plugins directory.
  • Run the project, which will cause the plugin to be built for your platform.

After packaging with this plugin release, you will be then able to see the ConvaiLogs folder.

I just build the latest release (3.6.6) from source and still no ConvaiLogs.

Is there any other solution that i can try. or is there a specific build i need to download & build to get the ConvaiLogs?

Could you please try with the development build?

As mentioned before, the project does work in the development build. However, sending a development build to our client would only be a last resort, and I’d really like to avoid that if possible. Since it runs fine in development but fails in shipping, I currently have no clear idea what causes the issue.

Just to clarify — when you say “try with the development build,” do you mean actually use the development build as a solution, or simply test with it to confirm behavior?

We won’t be able to resolve this issue in a short time. For now, you will need to use the development build.

Hello @jules,

Could you please check the logs? Please use version 3.6.7.