Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: use manifest placeholder to get rid of playstore error (WPB-8645) 🍒 #3230

Merged

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Jul 24, 2024

EpicWPB-8645 [Android] Infrastructure code and developer experience

This PR was automatically cherry-picked based on the following PR:

Original PR description:



PR Submission Checklist for internal contributors

  • The PR Title

    • conforms to the style of semantic commits messages¹ supported in Wire's Github Workflow²
    • contains a reference JIRA issue number like SQPIT-764
    • answers the question: If merged, this PR will: ... ³
  • The PR Description

    • is free of optional paragraphs and you have filled the relevant parts to the best of your ability

What's new in this PR?

Issues

We have an "error/warning" from the play store console, suggesting to not use keys directly
Generated BuildConfig are plain text and accessible by the scanner of the playstore console.

Causes (Optional)

We are seeing that we can not release Beta/Blue apps in the playstore to internal testers

Solutions

Follow "best practices" and use manifest placeholder instead for this API key.

How to test / testing

The app should build, and if you build locally, you should see the substitution in the merged AndroidManifest from the build directory.


PR Post Submission Checklist for internal contributors (Optional)

  • Wire's Github Workflow has automatically linked the PR to a JIRA issue

PR Post Merge Checklist for internal contributors

  • If any soft of configuration variable was introduced by this PR, it has been added to the relevant documents and the CI jobs have been updated.

References
  1. https://sparkbox.com/foundry/semantic_commit_messages
  2. https://github.com/wireapp/.github#usage
  3. E.g. feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764.

@github-actions github-actions bot added cherry-pick PR is cherry-picking changes from another banch echoes: throughput/ci-maintenance size/XS labels Jul 24, 2024
@yamilmedina yamilmedina requested review from yamilmedina, a team, typfel, MohamadJaara, Garzas and ohassine and removed request for a team July 25, 2024 07:22
@yamilmedina yamilmedina enabled auto-merge July 25, 2024 07:22
Copy link

@yamilmedina yamilmedina disabled auto-merge July 25, 2024 08:12
@yamilmedina yamilmedina added this pull request to the merge queue Jul 25, 2024
Copy link
Contributor Author

Built wire-android-staging-compat-pr-3230.apk is available for download

Copy link
Contributor Author

Built wire-android-dev-debug-pr-3230.apk is available for download

Merged via the queue into develop with commit 5af0fdd Jul 25, 2024
11 of 12 checks passed
@yamilmedina yamilmedina deleted the chore/dont-use-buildconfig-forgcpapikey-cherry-pick branch July 25, 2024 08:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cherry-pick PR is cherry-picking changes from another banch size/XS
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants