I am running ManifestExplorer (Download Link) tool in my Android Device. It returns the list of permission required by installed applications. One of the application installed requires
"android.permission.RECEIVE_SECURITY_SMS"
I have tried google but cannot find significance of this permission.
Can anyone help me with the same.
Related
I created my app, generated a signed apk and tried to install it. I got an error App not installed. I rebooted the device, resigned apk, tried again. But nothing worked. On the emulator everything is ok. How can I fix the problem? I try to install apk to android 10. The minimum SDK is 21. Permissions:
<uses-permission android:name="android.permission.INTERNET" />
I don't know what else may influence and cause this error. Please, help me
Scenario one
The application where you want to install your app from whether it was Google Drive or File Manager doesn't have the permission to Install apps from unknown sources
So go to the >> App info and set this permission enabled.
Scenario Two
Installing an app from Google Drive issue happened with a client of mine, and we were uploading the app to MediaFire instead.
I think in that case the application would be downloaded and installed from the browser Chrome and by turn it should have the same permission Install apps from unknow sources enabled.
Don't forget If an old version of the app was installed on your device make sure to un-install it manually
recently I get Installed blocked : The app permissions error error when updating my application(in app updating).
I know my app signatures are same because I can install new app manually.
can some know why this happen?
Do you think I need to grant android.permission.INSTALL_PACKAGES while I granted android.permission.REQUEST_INSTALL_PACKAGES? if yes can explain deference of both?
Note: my application updated correctly in many devices!! but in some devices(android Version: 5.1.1) have problem!!!
The INSTALL_PACKAGES permission allows an application to install packages. It is not for use by third-party applications.
Developers of apps that require the ability to download and install other apps via the Package Installer may need to make some changes. If an app uses a targetSdkLevel of 26 or above and prompts the user to install other apps, the manifest file needs to include the REQUEST_INSTALL_PACKAGES permission.
Read more here: https://android-developers.googleblog.com/2017/08/making-it-safer-to-get-apps-on-android-o.html?m=1
I want to add this permission to my Android manifest:
<uses-permission android:name="android.permission.MODIFY_PHONE_STATE" />
But after I paste this permission in my manifest, it tests red underline and says:
permission is only granted to system apps
What can I do?
MODIFY_PHONE_STATE permission is granted to system apps only.
For your information, there are 2 types of Android apps: system & user
User apps are just all your normal app installations through the Google Play Store, Amazon Appstore or sideloading. These go into the /data partition of your Android phone, which is the part of the internal memory made available for user data and apps.
System apps are basically the apps that come pre-installed with your ROM. In a standard Android user environment, the user doesn’t have write access to the /system partition and thus, installing or uninstalling system apps directly isn’t possible.
In order to install an app as a system app on your Android device,
your device must either be rooted or have a custom recovery installed (or both).
That being said, that error is actually wrong because you have a valid code and compilation should work. It would be better if it gave a warning instead. In Eclipse you can easily fix it. Just go to:
Window -> Preferences -> Android -> Lint Error Checking.
Find ProtectedPermission from the list and set the severity to something other than error(info for example). This way your project will still compile.
MODIFY_PHONE_STATE is a system-only permission. System Apps are either pre-installed into a system folder or compiled by a manufacturer using their security certificate.
Hence, if you are trying to do this you are trying to use API which are no longer supported. With Android versions 2.3+ you can monitor incoming calls, but blocking is not allowed (i think from the link you posted thats what you're trying to do).
Android issues if you need to follow: Issue 15022 and Issue 14789
This error appears in SDK 19 onwards, when you change the manifest.
Do Project Clean and Build.
It should clear this error.
just clean your project it will be fine like this :
project > Clean...
There are four types of Permission
Regular
Dangerous
Signed
Signed or System
The first two can be used by Simple Apps Other two can only be used by the app which is build in framework
Because this is the system level permission device developer not grant this so application development tools also warn against this so you have to
Simply Clean project & Rebuild this is it
Find ProtectedPermission from the list in
Window -> Preferences -> Android -> Lint Error Checking.
and set the severity to something other than error(info for example). This way your project will still compile.
I'm developing an app that uses the Google Maps api to give you a list of a given business type at runtime based on your current location.
I developed this on Eclipse using my LG Ally running Android 2.2.2 as a test device.
The QA team is not local to me so I emailed them the same apk file I installed on my phone.
Here's where it gets strange.
One tester, was able to install the app and run it with no problems. That person is using a phone running Android 2.2.2 - just like I am, although I am unsure if their phone is an LG Ally.
The other person is using a phone running 2.3.3 and they are unable to run the app. They've installed an app that emails me the logcat output and the only message that looks even vaguely related is:
06-21 14:22:57.147 W/PackageInstaller( 8784): Parse error when parsing manifest. Discontinuing installation
I've read on Stackoverflow that the manifest must contain info about the sdk. My Android Manifest contains:
<uses-sdk android:minSdkVersion="7" android:targetSdkVersion="15"/>
I've also read on Stackoverflow that some people have problems installing apps emailed to them and suggested something like DropBox.
I've done both (included the above sdk line in my Manifest and delivered the app via DropBox) and they are still unable to run the app.
Which got me wondering about the Google Maps dependency. I'm not delivering the maps.jar file in my apk. Is there a way I can check that the maps.jar is available on the device where my app is running? Is there a way I can deliver the maps.jar file? What do I do if maps.jar is already present?
Is there a way I can check that the maps.jar is available on the device where my app is running?
If you have <uses-library> with the android:required="false" attribute, then your app can run even if the device lacks the Google Maps add-on for Android. You would use Class.forName() to see if MapActivity exists before trying to actually use a MapActivity, as in this sample project.
However, if your <uses-library> lacks an android:required attribute, or has it set to true, then the app simply cannot be installed on the device.
Is there a way I can deliver the maps.jar file?
Only in the form of buying the user another device -- one that has the Google Maps add-on -- and shipping it to them. Either the device has it (as do most devices that legitimately have the Play Store) or it doesn't (e.g., Kindle Fire). You cannot change that fact.
In one of my application my customer reported the problem with installation. He/She is unable to install my application in his/her Android mobile it's having problem to install application in SD card how to fix this problem?
Thanks,
Is your customer's device running Android 2.2 or above? If not, then you cannot install to SD.
Have you specified android:installLocation in your manifest? If you do not, then by default, you can only install the app to internal memory regardless of Android version.
See Android dev - manifest for general info, and Android dev - installLocation for more detailed information on the installLocation tag including how to maintain backwards compatibility.