Updated the project to run with Android Studio Otter. #386
Conversation
| EditText etApiKey = findViewById(R.id.et_api_key); | ||
| EditText etCustomOptions = findViewById(R.id.et_custom_options); | ||
|
|
||
| etApiKey.setText("rzp_live_ILgsfZCZoFIKMb"); |
There was a problem hiding this comment.
@vivekshindhe need clarity on whether we share our merchant key publicly or not.
![semgrep-code-razorpay[bot]](https://avatars.githubusercontent.com/u/7713209?s=60&v=4){kind=small}
| val etApiKey = findViewById<EditText>(R.id.et_api_key) | ||
| val etCustomOptions = findViewById<EditText>(R.id.et_custom_options) | ||
|
|
||
| etApiKey.setText("rzp_live_ILgsfZCZoFIKMb") |
There was a problem hiding this comment.
Hardcoded sensitive data leaked
Semgrep has detected a leak of sensitive data in this code. This secret data could be used by internal or external malicious actors. We highly recommend you change, reset, or rotate the sensitive data.
A secret is hard-coded in the application. Secrets stored in source code, such as credentials, identifiers, and other types of sensitive data, can be leaked and used by internal or external malicious actors. It is recommended to rotate the secret and retrieve them from a secure secret vault or Hardware Security Module (HSM), alternatively environment variables can be used if allowed by your company policy.
🔴 Fix or ignore this finding to merge your pull request.
Ignore this finding from string
| EditText etApiKey = findViewById(R.id.et_api_key); | ||
| EditText etCustomOptions = findViewById(R.id.et_custom_options); | ||
|
|
||
| etApiKey.setText("rzp_live_ILgsfZCZoFIKMb"); |
There was a problem hiding this comment.
Hardcoded sensitive data leaked
Semgrep has detected a leak of sensitive data in this code. This secret data could be used by internal or external malicious actors. We highly recommend you change, reset, or rotate the sensitive data.
A secret is hard-coded in the application. Secrets stored in source code, such as credentials, identifiers, and other types of sensitive data, can be leaked and used by internal or external malicious actors. It is recommended to rotate the secret and retrieve them from a secure secret vault or Hardware Security Module (HSM), alternatively environment variables can be used if allowed by your company policy.
🔴 Fix or ignore this finding to merge your pull request.
Ignore this finding from string
No description provided.