bitrise-steplib/steps-xcode-archive

App name get messed when using non-english characters

thebergamo opened this issue · 2 comments

thebergamo commented

Troubleshooting

  • I've searched discuss.bitrise.io for possible solutions.
  • Which version of the step is effected? 1.2.3
  • Is the issue reproducible with the latest version? YES / NO
  • Does the issue happen sporadically, or every time? SPORADIC / EVERY TIME
  • Is the issue reproducible locally by following our local debug guide? YES / NO / NOT APPLICABLE

Useful information

Issue description

My app has in it's name some non-english characters which during archive step this characters get messed up as you can see in the logs below.

When running it locally it works fine and I couldn't find anyway to configure it (or where it could be wrong set). My assumption is that this step sets some charset that doesn't support Brazilian accents in apps name and pass it somehow to xcode.

Bitrise info

Correct character would be: Tá Barato 
▸ Compiling main.m
▸ Compiling TÆ\ Barato_vers.c
▸ Compiling AppDelegate.m
▸ Linking TÆ\

Steps to reproduce

  1. Create a new ios app with non-english characters name for example: Tá Bom!
  2. Use this step in bitrise
bitrise-coresteps-bot commented

Hello there, I'm a bot. On behalf of the community I thank you for opening this issue.

To help our human contributors focus on the most relevant reports, I check up on old issues to see if they're still relevant.
This issue has had no activity for 90 days, so I marked it as stale.

The community would appreciate if you could check if the issue still persists. If it isn't, please close it.
If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me".

If no comment left within 21 days, this issue will be closed.

bitrise-coresteps-bot commented

I'll close this issue as it doesn't seem to be relevant anymore.
We believe an old issue probably has a bunch of context that's no longer relevant, therefore, if the problem still persists, please open a new issue.