Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
Summary of ChangesHello @carolina584, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! Este pull request actualiza el archivo de configuración de Firebase ( Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
Ignored Files
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
Este pull request actualiza el archivo de configuración de Firebase GoogleService-Info.plist. Sin embargo, la actualización incluye credenciales sensibles como una API_KEY. Esto representa una vulnerabilidad de seguridad crítica. He dejado un comentario detallado en el archivo con recomendaciones para mitigar este riesgo. Es crucial que los archivos que contienen secretos no se incluyan en el control de versiones.
| <key>API_KEY</key> | ||
| <string>AIzaSyAzlj4APqi5S58nFtE52Da0fYBOHA2MhaY</string> | ||
| <key>BUNDLE_ID</key> | ||
| <string>com.google.firebase.quickstart.AnalyticsExample</string> | ||
| <key>CLIENT_ID</key> | ||
| <string>123456789000-hjugbg6ud799v4c49dim8ce2usclthar.apps.googleusercontent.com</string> | ||
| <key>DATABASE_URL</key> | ||
| <string>https://mockproject-1234.firebaseio.com</string> | ||
| <string>AIzaSyDW7nSUCURYKM-fqKSrGN4eS0UZkA1GtpE</string> | ||
| <key>GCM_SENDER_ID</key> | ||
| <string>123456789000</string> | ||
| <key>GOOGLE_APP_ID</key> | ||
| <string>1:123456789000:ios:f1bf012572b04063</string> | ||
| <string>672558884827</string> | ||
| <key>PLIST_VERSION</key> | ||
| <string>1</string> | ||
| <key>BUNDLE_ID</key> | ||
| <string>com.caro.testdemo</string> | ||
| <key>PROJECT_ID</key> | ||
| <string>testmobileios-df09c</string> | ||
| <key>STORAGE_BUCKET</key> | ||
| <string>testmobileios-df09c.firebasestorage.app</string> | ||
| <key>IS_ADS_ENABLED</key> | ||
| <true/> | ||
| <false></false> | ||
| <key>IS_ANALYTICS_ENABLED</key> | ||
| <true/> | ||
| <false></false> | ||
| <key>IS_APPINVITE_ENABLED</key> | ||
| <true/> | ||
| <true></true> | ||
| <key>IS_GCM_ENABLED</key> | ||
| <true/> | ||
| <true></true> | ||
| <key>IS_SIGNIN_ENABLED</key> | ||
| <true/> | ||
| <key>PLIST_VERSION</key> | ||
| <string>1</string> | ||
| <key>PROJECT_ID</key> | ||
| <string>mockproject-1234</string> | ||
| <key>REVERSED_CLIENT_ID</key> | ||
| <string>com.googleusercontent.apps.123456789000-hjugbg6ud799v4c49dim8ce2usclthar</string> | ||
| <key>STORAGE_BUCKET</key> | ||
| <string>mockproject-1234.appspot.com</string> | ||
| <true></true> | ||
| <key>GOOGLE_APP_ID</key> | ||
| <string>1:672558884827:ios:9dabd5502a0477c3f169fe</string> |
There was a problem hiding this comment.
Se está cometiendo el archivo GoogleService-Info.plist con credenciales y configuración de un proyecto real de Firebase. Esto representa un riesgo de seguridad crítico, especialmente la API_KEY. Las claves de API y otros datos sensibles no deben ser almacenados en el control de versiones, especialmente si el repositorio es público.
Recomendación:
- Elimine este archivo del historial de Git para evitar la exposición de las credenciales.
- Añada
GoogleService-Info.plistal archivo.gitignorepara prevenir futuras confirmaciones. - Revoque la
API_KEYexpuesta en la consola de Google Cloud/Firebase y genere una nueva. - Cada desarrollador debe usar su propia copia local de
GoogleService-Info.plistpara desarrollo, siguiendo las instrucciones delREADME.md.
Updated paths and job names in the iOS workflow.
Updated workflow to check for Podfile instead of installing dependencies.
Updated step name and echo statements for clarity.
Updated workflow name and modified steps to list directories and find Podfiles.
Updated workflow name and modified steps to create Podfile from scratch instead of downloading it.
Updated project name and adjusted paths for xcodeproj and target.
No description provided.