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

Create placeholder files for google-services.json and String Resources secrets #26

Open
1 task done
Basler182 opened this issue Jun 7, 2024 · 2 comments
Open
1 task done
Labels
ENGAGE HF ENGAGE-HF-specific issues enhancement New feature or request

Comments

@Basler182
Copy link
Contributor

Problem

Currently, the project lacks placeholder files for google-services.json and String Resources secrets. This can cause confusion and errors during the setup process, as developers may not know where or how to include these essential configuration files.

Solution

Create placeholder files for google-services.json and the necessary String Resources secrets. These placeholders should be clearly marked with instructions on how to replace them with actual configuration values.

Additional context

Including placeholder files will streamline the setup process for new developers, ensuring that they know exactly where to place their configuration values and reducing the likelihood of setup errors.

Code of Conduct

  • I agree to follow this project's Code of Conduct and Contributing Guidelines
@Basler182 Basler182 added the enhancement New feature or request label Jun 7, 2024
@eldcn
Copy link
Contributor

eldcn commented Jun 8, 2024

Instead of placeholders, we can consider introducing source sets for debug builds.

@PSchmiedmayer
Copy link
Member

We have added a placeholder file for the google services json for Firebase in #30 that ensures that the builds are running locally and build successful. The file is replaced when building an app bundle for the Play Store. Does not address string resources secrets.

@PSchmiedmayer PSchmiedmayer added the ENGAGE HF ENGAGE-HF-specific issues label Jun 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ENGAGE HF ENGAGE-HF-specific issues enhancement New feature or request
Projects
Status: Next Steps
Development

No branches or pull requests

3 participants