Apostrophe in Project -> Description -> Project Name causes Packaging failure

Development Platform & Builds
, , ,
1

If you enter a string with an apostrophe ’ into the Project Name field e.g. “Wood in T’hole” then packaging for Windows will fail for a non-obvious reason. The project is a mixed code/BP one.

The string makes it into a PCH #define which won’t compile.

2

Hey IslandPlaya,

I’ve tested this in 4.14 and 4.15, but I’m not seeing a packaging failure. When I entered a name with an apostrophe, such as That’s Incredible, it packaged fine without an issue.

Would you mind providing the logs from your project’s Saved->Logs folder so I can take a closer look at your errors?

Thanks

3

My project packages correctly with this project name: Put Wood in Thole

With this project name it fails: Put Wood in T’hole

I’ve attached the log file for the failed attemptlink text. The error is on line 3119

Thanks

4

Could you test this again in a clean project? I’ve given it a try and it doesn’t appear to be causing a packaging failure on my end, even when I use the exact name you’ve provided.

5

I’ll do that and report on what I find. The problem may be down to the plugins I am using.
Thanks

6

Steps to reproduce:

Choose New Project → C++ → Basic Code

Change project name to "Put Wood in T’hole’

Package for Windows(64 bit)

Packaging fails in the same way I reported previously.

Cheers!

7

Thanks for the clarification. I wasn’t using a C++ project, so I didn’t see the same behavior. It does not appear to happen with a blueprint project.

Here’s a link to the public tracker so you can keep an eye on the issue:

Have a great day

8

Now fixed, marked for release in 4.16. That was quick.
This was my first bug report to Epic… It went smooth as silk.
Thanks Sean and team.

9

Thank you for fixing it. Given that my name is Nicholas O’Connor, I’d like that to be accurate in my copyright notices :V