bitrise-steplib/steps-xcode-archive

Failed to process Step inputs: issue with input ExportOptionsPlistContent: plist: type mismatch: tried to decode plist type `string' into value of type `map[string]interface {}' (exit code: 1)

Shahrukh0396 opened this issue · 3 comments

Troubleshooting

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

Useful information

Issue description

Bitrise step xcode archive & Export ios has been failed when reading the export option plist file.

Bitrise info

 
Failed to process Step inputs:
  issue with input ExportOptionsPlistContent: plist: type mismatch: tried to decode plist type `string' into value of type `map[string]interface {}'
  

Steps to reproduce

  1. ...
  2. ...

Hi @Shahrukh0396

Thank you for contacting Bitrise.

As the description of the input variable ExportOptionsPlistContent suggests, you need to input the content of the plist to that variable, not the plist path.

Export options plist content
Specifies a plist file content that configures archive exporting.
If not specified, the Step will auto-generate it.

You can also leave it empty to let the step auto-generate it for you.

Hope this helps!

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.

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.