-
Notifications
You must be signed in to change notification settings - Fork 52
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
Attribution - Getting "Failed to find resolveInfo for adServices service." #46
Comments
Hi @levyitay, thanks for reporting the issue! Would you mind letting us know if you are experiencing this on a Developer Preview or Beta release? |
Hi @erintwalsh I followed the developer preview release both on real device and emulator |
@levyitay thanks for the quick response! Just to check, are you using Developer Preview 7? (You can check this in the SDK Manager, in the |
Thanks, @levyitay! Would you mind following a few more steps to help us debug the issue?
Thank you!! |
@erintwalsh
On device (pixel 5 with Build TRA4.221021.001.A1):
register trigger:
|
@erintwalsh Did we figure this one out? |
Sorry for the delay, jumping in to this issue a bit late so please excuse me if my question is out of date. We believe the issue comes from your device having not received a config rollout yet. It appears it's harder to get working on an emulator, so using your physical device, can you try to start the missing service via adb:
And let me know what the output is? Should see something like
But if it fails, will have an additional |
yeah I got:
FYI I'm on |
Hi, I'm getting the same error Any updates regarding the issue? @erintwalsh Is it expected to work on a physical device? |
Hi, I am testing the developer preview and is facing the same problem on both emulator and physical device.
Wondering if there is some guidance on how to proceed. Thanks! |
Hey, I have same issue running on Pixel 5
On registerTrigger()
While running |
Hi everyone! We greatly appreciate the logs and insights posted here as we worked on the issue. An update has started to roll out, so you should be seeing this issue resolved shortly on both physical devices and emulators (exact time will vary depending on device and network connectivity). Thank you for bearing with us! |
Hi @erintwalsh ! Thanks for the update. Im still experiencing the same issue on an emulator
Logs for 3)
|
@erintwalsh @cshmerling |
@erintwalsh @cshmerling |
Hi @RonShub, @levyitay, and @pazlavi, Just wanted to check - have you declared the |
Hi @erintwalsh ! |
@erintwalsh yes I can confirm it's declared |
Hi all, If you are still experiencing the issue, can you please provide the version code on your device? You can find this by going to Settings > About phone > Build number. Can you also confirm that you have updated to the latest version of Developer Preview 7, or Beta 2? Instructions to update to the latest Developer Preview 7 on an emulator:
Instructions to update to the latest Beta 2 on an emulator:
|
Hi @RonShub, @levyitay, and @pazlavi, if you're still experiencing this issue, would you mind following these steps and then try calling the API again? Reset your allow list by running the commands
Note: you will need to use the 'put' command for each app package name you are testing with. |
@erintwalsh when I first tried it I got the following error:
Then I ran our script that supposed to setup my device for Privacy Sandbox (I removed manifest url just for posting this)
And got this:
I waited few minutes and saw that ad services service started an update from the enrollment url so I decided to try again and got this:
|
We are seeing the exact same error... Curious if anyone has successfully called the attribution reporting API, and if so, what did you do/change to make this happen? |
Hey, |
@erintwalsh Any update on that stack trace and issue from my last comment? |
Hi everyone, Thanks for your continued feedback, stack traces, and patience! We have made a few updates that will hopefully be helpful. Would you mind making sure you have the latest commits from this GitHub project, testing on a fresh emulator or clean install on a device, and making sure all the steps on this page are followed? |
Hi Team,
I'm trying to test the attribution process but keep getting the following error when I try to register source or trigger:
I also doubled checked device config is accurate:
The service seems to be up since its responding to forcing it's jobs like:
adb shell cmd jobscheduler run -f com.google.android.adservices.api 14
which works
What could be the issue?
The text was updated successfully, but these errors were encountered: