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

Update AndroidManifest.xml #1739

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update AndroidManifest.xml #1739

wants to merge 1 commit into from

Conversation

aria1991
Copy link

@aria1991 aria1991 commented Jan 11, 2023

1- I've added <uses-permission android:name="android.permission.INTERNET" /> and other permission that should be in the app, also added activity to launch the app and activity to handle the passport.

2- It's better to generate a new API key for the Google Maps feature instead of using the one provided in the script. This will ensure the security of the application and prevent unauthorized access to the Google Maps feature.

3- The uses-permission and uses-feature elements should be carefully reviewed and only the necessary permissions should be requested. It is important to be transparent with the users about the permissions that the application needs and the reasons why they are necessary.

4- It's better to use android:protectionLevel="signature" for permission that are not critical to the app operation and do not contain sensitive information and if possible, implement runtime permissions which allow users to grant permissions at the time the feature is used rather than at the time of installation.

1- I've added <uses-permission android:name="android.permission.INTERNET" /> and other permission that should be in the app, also added activity to launch the app and activity to handle the passport.

2- It's better to generate a new API key for the Google Maps feature instead of using the one provided in the script. This will ensure the security of the application and prevent unauthorized access to the Google Maps feature.

3- The uses-permission and uses-feature elements should be carefully reviewed and only the necessary permissions should be requested. It is important to be transparent with the users about the permissions that the application needs and the reasons why they are necessary.

4- It's better to use android:protectionLevel="signature" for permission that are not critical to the app operation and do not contain sensitive information and if possible, implement runtime permissions which allow users to grant permissions at the time the feature is used rather than at the time of installation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant