Check if running via SSH (no access to the keychain)

[matteocorti]

Description

When running the resign script via SSH the distribution certificate cannot be access since the keychain is locked.

The script now issues an error so that the user is advised to run the script in local shell.

Related Issue

Motivation and Context

When running the script via SSH the error message is not readily visible and the issue is not easy to be noticed.

How Has This Been Tested?

Tested while running in a local shell and via SSH

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• Added an issue with details about all relevant changes in the iOS documentation repository.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.
• Added changelog files for the fixed issues in folder changelog/unreleased

[CLAassistant]

All committers have signed the CLA.

[hosy]

@matteocorti Thank you so much for your contribution! This will help us and other customers avoid getting stuck on resigning issues.

[matteocorti]

@matteocorti Thank you so much for your contribution! This will help us and other customers avoid getting stuck on resigning issues.

Actually, it appears that it should be possible to unlock the keychain via command line, but in my case I had some issues from time to time. As soon as I am sure, I will submit another patch.

[hosy]

@matteocorti Would be great if you could increase the version number when committing new changes.

[matteocorti]

@matteocorti Would be great if you could increase the version number when committing new changes.

Now I see: the script has an own version ...