HockeyApp docs states that apps that are already in production and have pre-release options must be configured twice. One as Store and one as Beta.

Therefore, there should be an option to deploy the IPA to one config (using one App ID) and the dSYM to another (using a different App ID), where the IPA should go to the Beta config and the dSYM to the Store config.

Perhaps it would be interesting to have a new step to upload only the dSYM, considering that releases that are submitted to the AppStore don't need to be deployed to HockeyApp, only their dSYMs must be submitted in order for HockeyApp to be able to symbolicate their crashes and exceptions.

Hello,

It could be great if , for the upload, the attached note on hockeyApp can be the content of the changelog.md/txt file of the current repo

Cheers from France

TAG: enhancement

According to API documentation it is possible to upload an app without .ipa if .dSYM is given. This helps when using HockeyApp only for crash reporting.

This PR introduces a small change to allow for dsym_path to be passed without ipa_path

It has been more than a month that the HockeyApp deployment fails. By building a second time after the failure, the deployment works. Here is the fail point:

Response:
  status code: 504
  body: 
Performing request failed, status code: 504
exit status 1
|                                                                              |
+---+---------------------------------------------------------------+----------+
| x | hockeyapp-deploy (exit code: 1)                               | 165 sec  |
+---+---------------------------------------------------------------+----------+
| Issue tracker: https://github.com/bitrise-io/steps-hockeyapp-deploy/issues   |
| Source: https://github.com/bitrise-io/steps-hockeyapp-deploy                 |
+---+---------------------------------------------------------------+----------+

Hello everyone,

I'm getting the following error when deploying to HockeyApp:

If I take the artifacts (.ipa & .dSYM.zip) and upload it to HockeyApp manually via the website, it works. Can't find a way to log the full request.

Any advice and suggestions will be greatly appreciated. ❤️

Is there a way to change the outputed Enviroment Variables from

$HOCKEYAPP_DEPLOY_PUBLIC_URL

to

$HOCKEYAPP_IOS_DEPLOY_PUBLIC_URL

Also a similar change to the for the Android App? Otherwise you can't get both the link for the Android app and the iOS app in the build process.

+------------------------------------------------------------------------------+

| (8) hockeyapp-deploy | +------------------------------------------------------------------------------+ | id: hockeyapp-deploy | | version: 2.4.2 | | collection: https://github.com/bitrise-io/bitrise-steplib.git | | toolkit: go | | time: 2017-08-10T02:25:57-07:00 | +------------------------------------------------------------------------------+ | | INFO[02:25:57] * [OK] Step dependency (go) installed, available. Configs:

• IPAPath:
• DSYMPath:
• APIToken: a1e6bde50d88484f8a1758c5177d55fc
• AppID: 7933bdfcb19c467eb5d1ebd951f05de3
• Notes: Deploy with Bitrise HockeyApp Deploy Step.
• NotesType: 0
• Notify: 2
• Status: 2
• Mandatory: false
• Tags:
• CommitSHA:
• BuildServerURL: https://www.bitrise.io/build/48fa435a188203dc
• RepositoryURL: Issue with input: IPAPath parameter must be specifed when DSYMPath is missing | | +---+---------------------------------------------------------------+----------+ | x | hockeyapp-deploy (exit code: 1) | 4.75 sec |

https://www.screencast.com/t/zaycda3c

Why - IPAPath: and DSYMPath: are empty?

There's a way to support Markdown formatting in attachments, although it's buried in their documentation a bit.

See the "Message Formatting" section on the Slack API docs page.

{
    "attachments": [
        {
            "title": "Title",
            "pretext": "Pretext _supports_ mrkdwn",
            "text": "Testing *right now!*",
            "mrkdwn_in": ["text", "pretext"]
        }
    ]
}

The latest version changes how parameters are passed through the step and out to cURL. Previously, it was possible to include newlines in the "notes" field. This was useful for building things like changelogs using the "Markdown" Notes Type. In 2.2.0 these are no longer preserved and multi-line values are now passed through as a single-line string.

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

Detected Package Files

• .github/workflows/stale-issues-workflow.yml (github-actions)

Configuration

🔡 Renovate has detected a custom config for this PR. Feel free to ask for help if you have any doubts and would like it reviewed.

Important: Now that this branch is edited, Renovate can't rebase it from the base branch any more. If you make changes to the base branch that could impact this onboarding PR, please merge them manually.

What to Expect

It looks like your repository dependencies are already up-to-date and no Pull Requests will be necessary right away.

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section. If you need any further assistance then you can also request help here.

This PR has been generated by WhiteSource Renovate. View repository job log here.

Description

• Sensitive inputs marked in step.yml
• Readme updated with the "How to trigger a new release"
• Removed the old release workflows ( create-release & share-this-step) because we will not need them with the new release flow.
• Removed the release_config.yml and the changelog.md because we will not need them with the new release flow.
• Removed the old step.sh
• Dependency manager changed from godep to dep
• fix(workflow): git-clone step changed to script step

Click Up ticket / Github Issue / Discuss Thread

Click Up: https://app.clickup.com/757956/762238/t/40mvg

Type of change

Please select options that are relevant.

• [ ] Issue
• [X] Enhancement
• [ ] Maintenance
• [ ] Feture request