We solved the issue by getting the application context and calling
startService/bindService on that context rather than the activity's
context (which is within an activity group - which is why it didn't
work for some reason).
On Nov 13, 3:46 pm, Raktim Das [EMAIL PROTECTED] wrote:
Hi,
I am
Thanks a lot for analyzing the problem.
First, my comment on your second point -
This I had already been doing - as in the client application's
manifest, the service application's manifest too has this entry under
the manifest tag:
uses-permission
Be sure you install the .apk providing the permission before the one
using it. You can see what permissions your app has been granted by
digging through the output of adb shell dumpsys package.
Also PLEASE DO NOT use the name android.permission. The namespaces
android.* and com.android.* are
The Intent you are making to bind to the service is trying to find a
component in your own .apk, not the other.
The last permission error you mention is because you need to
explicitly request to use even your own permissions.
On Nov 10, 9:31 pm, Raktim Das [EMAIL PROTECTED] wrote:
Hi,
I am
Thanks a ton. It worked!
On Nov 11, 3:42 pm, hackbod [EMAIL PROTECTED] wrote:
Be sure you install the .apk providing the permission before the one
using it. You can see what permissions your app has been granted by
digging through the output of adb shell dumpsys package.
Also PLEASE DO NOT
5 matches
Mail list logo
