Hello,
I have an application which has some of it's activities restricted via
my own permission. The permission is published in the manifest of the
application A and a second application B should request this
permission and then be able to call an activity from app A. Both
applications belong to me and are signed with the same certificate
(they share the same keystore and alias/password from it).
The manifest of app A looks like this:
<manifest>
<permission
android:name="com.sebastian.example.EXAMPLE_PERMISSION"
android:label="@string/permisson_label"
android:description="@string/permisson_description"
android:protectionLevel="signature">
</permission>
<application>
<activity android:name=".ui.Example"
android:permission="com.sebastian.example.EXAMPLE_PERMISSION">
</activity>
</application>
<uses-permission
android:name="com.sebastian.example.EXAMPLE_PERMISSION"></uses-
permission>
</manifest>
App A is installed *before* app B and I can call the activity from the
inside of app A. The manifest of app B looks like this:
<manifest>
<application>
<activity android:name=".ui.Example2">
</activity>
</application>
<uses-permission
android:name="com.sebastian.example.EXAMPLE_PERMISSION"></uses-
permission>
</manifest>
Application A gets granted the permission but app B gets never granted
the permission! Logcat tells me about this during the installation and
the app crashes with an security exception when trying to start the
activity from app A.
What the heck am I doing wrong? Could it be something with the
application signing? Please help me, I'm totally out of ideas.
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
