runtime error: slice bounds out of range about steps-ios-auto-provision-appstoreconnect HOT 9 CLOSED

@MikaelMelkonyan You are right. The old step has a different source code. You can use that step as an alternative solution for now, but that step will be deprecated. In the future our engineers will investigate the difference between the old and the new step's source code, but until then you can't use emojis if you want to use the new step. Thanks for your understanding.

from steps-ios-auto-provision-appstoreconnect.

Hi @MikaelMelkonyan,

Could you please check that you don't have any special characters or emojis in your XCode project folder names? If the plist contains any special characters/emojis then the iOS Auto Provision step can fail. I hope these information could help.

from steps-ios-auto-provision-appstoreconnect.

Hi @MikaelMelkonyan,

Could you please check that you don't have any special characters or emojis in your XCode project folder names? If the plist contains any special characters/emojis then the iOS Auto Provision step can fail. I hope these information could help.

Hello Robert. Thanks for your reply.
I have 🚀 emoji in my 'Display name'. Is it required to remove emoji? For us it's very important to have emoji in 'Display name'. Marketing requirements 😃.

from steps-ios-auto-provision-appstoreconnect.

Hi @MikaelMelkonyan !

Sorry but you need to remove them if you want to be able to build :( Emojis are so funny and cool but it causes issues in the plist process.

from steps-ios-auto-provision-appstoreconnect.

Hi @MikaelMelkonyan !

Sorry but you need to remove them if you want to be able to build :( Emojis are so funny and cool but it causes issues in the plist process.

Got it. But old version of Auto-provision (iOS Auto Provision with Apple ID) still works fine with emojis. ((

from steps-ios-auto-provision-appstoreconnect.

@MikaelMelkonyan You are right. The old step has a different source code. You can use that step as an alternative solution for now, but that step will be deprecated. In the future our engineers will investigate the difference between the old and the new step's source code, but until then you can't use emojis if you want to use the new step. Thanks for your understanding.

Sure. I understand. Thanks a lot for your reply. 🤗

from steps-ios-auto-provision-appstoreconnect.

I'm seeing this somewhat suddenly as well, though I don't have any emoji in my file path or display name. However, we did add some emoji to an Xcode build phase script, which I imagine must have done it. After removing the emoji builds are back to normal.

Is there any chance at all this bug can be resolved? Obviously it's no longer urgent for us, but a resolution would be appreciated.

Thanks!

from steps-ios-auto-provision-appstoreconnect.

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.

from steps-ios-auto-provision-appstoreconnect.

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.

from steps-ios-auto-provision-appstoreconnect.