Obsolete
Status Update
No update yet.
Comments
ce...@gmail.com
this is the result for context impl:
int res = ActivityManagerNative.getDefault().bindService(...);
return res != 0;
maybe you should make the method return flag int instead masking it with boolean - but perhaps it is to late now to change api :)
this way i need one more time to rely on reflections to achieve that what should be as simple as one statement in api - or do a transact myself :/
int res = ActivityManagerNative.getDefault().bindService(...);
return res != 0;
maybe you should make the method return flag int instead masking it with boolean - but perhaps it is to late now to change api :)
this way i need one more time to rely on reflections to achieve that what should be as simple as one statement in api - or do a transact myself :/
ar...@google.com
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Steps to reproduce
Please provide source code or apk of a sample application to reproduce the issue.
Also kindly mention the steps to be followed for reproducing the issue with the given sample application.
Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)
Expected output
Could you please explain the expected behavior.
Current output
Could you please explain the current behavior.
Steps to reproduce
Please provide source code or apk of a sample application to reproduce the issue.
Also kindly mention the steps to be followed for reproducing the issue with the given sample application.
Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)
Expected output
Could you please explain the expected behavior.
Current output
Could you please explain the current behavior.
ce...@gmail.com
all "needed info" is already in posted issue.
is...@google.com
ar...@google.com
vi...@google.com
Thank you for your feedback. We assure you we are doing our best to address the issues reported, however our product team has shifted work to higher priority bugs and may not be able to handle this bug. As for now, we will be closing the bug as won’t fix obsolete.
If you are still facing the issue recently, we request that you log a new bug along with the bug report herehttps://goo.gl/TbMiIO. ”
If you are still facing the issue recently, we request that you log a new bug along with the bug report here
Description
* @return If you have successfully bound to the service, {@code true} is returned;
* {@code false} is returned if the connection is not made so you will not
* receive the service object.
example case:
1. WE HAVE A SERVICE IN PACKAGE A
2. SERVICE IS NOT CREATED/STARTED / NO PID
3. WE CALL TO BINDSERVICE IN PACKAGE B BUT WITHOUT CREATING IT AS WE ONLY WANT TO CHECK IF IS RUNNING OR NOT (VIA SERVICE CONNECTION METHOD OR BINDSERVICE RESULT METHOD VARIABLE)
following code:
// create service intent
Intent bindIntent = new Intent();
bindIntent.setComponent(componentName);
// try bind don't auto create service
boolean bindResult = context.bindService(bindIntent, ServiceConnection, 0);
in this case result is **always true if service is found either started or not**, if we do not request to start/create the service the result should be false as we didn't bound to the service - we also don't get a call to connected/disconnected method in this case - but in this case system should either return false or true and then call disconnected on service connection method.
or the doc should say your call was successful but **nothing will happen** (service connection method will not be called) if service is not already started or did not explicit request to create it by using a flag AUTO_CREATE!