Closed davidae closed 1 year ago
Hey, We're experiencing the same regression issue (worked in the past with API v34 and Canary 7).
Logs we're seeing (for the sample measurement app, which has the right permissions in the manifest file) -
com.example.measurement.sampleapp D registerSource
com.google.android.adservices.api E Unauthorized caller. Caller is not allowed.
com.example.measurement.sampleapp W To enable debug api, include ACCESS_ADSERVICES_AD_ID permission and enable advertising ID under device settings
com.google.android.adservices.api E Package com.example.measurement.sampleapp is not allowed to call the API.
I'm using:
adservices/ppapi_app_allow_list="com.example.measurement.sampleapp"
adservices/ppapi_app_signature_allow_list="com.example.measurement.sampleapp"
adservices/global_kill_switch=false
adservices/adid_kill_switch=false
adservices/adservice_enabled=true
adservices/disable_sdk_sandbox=false
adservices/mdd_measurement_manifest_file_url=<ENROLLMENT URL>
adservices/measurement_kill_switch=false
Using a physical device (Pixel 7, Android 14, build number UPB4.230623.005)
Hi @davidae and @yuvalcar,
Are you using a Developer Preview or Beta version of the Privacy Sandbox? If you could provide the build number in Settings > About Phone > Build Number, that would be helpful!
Sometimes the device config pulls updates and settings can get reset. Even though you listed these values earlier, to eliminate possible variables I'd start by verifying that your app package name (or *) is in the allowlist with adb shell device_config get adservices ppapi_app_allow_list
and adb shell device_config get adservices ppapi_app_signature_allow_list
If the allowlists look correct, I would go through the enrollment process again, including downloading the enrollment file on your device.
If those two steps don't help, I would double check your enrollment information and make sure the URLs are correct and enrolled. One possible cause of this error is the app using a URL like "example.com/source" when the enrolled URL is "example.com/register_source"
To help with testing, you can disable config updates on your device by running adb shell device_config set_sync_disabled_for_tests persistent
. To re-enable them, there is adb shell device_config set_sync_disabled_for_tests none
Hi @erintwalsh, thank you for the tips. But, unfortunately, the problem remains the same.
Are you using a Developer Preview or Beta version of the Privacy Sandbox?
The build number on the emulated device is URA8.230510.004
.
To help with testing, you can disable config updates on your device by running adb shell device_config set_sync_disabled_for_tests persistent.
Thank you for sharing this command.
adb shell device_config get adservices ppapi_app_allow_list
and adb shell device_config get adservices ppapi_app_signature_allow_list
now remains with the *
value for the whole life-time of the emulated device.
I would double check your enrollment information and make sure the URLs are correct and enrolled.
Done this
If the allowlists look correct, I would go through the enrollment process again, including downloading the enrollment file on your device.
Done this. But a question here too, with the new enrollment form and process, I was informed this would no longer be required, is this correct?
Hi @erintwalsh, I've followed the guide using Hedgehog | 2023.1.1 Canary 15 and got the same results. Is there anything else we can try?
Hi @davidae and @typerat, is there a chance you're starting adb directly instead of using bash or other shells? If that's the case, try not escaping the quotes:
adb shell device_config put adservices ppapi_app_allow_list "\*"
adb shell device_config put adservices ppapi_app_signature_allow_list "\*"
"Caller is not allowed" indicates an issue with the allowlist, so if those values are correct we need to dig deeper into the error. Is it possible to reproduce and attach a full bugreport? (You can do so by running adb bugreport
).
If you have contacts at Google, if you ask them to put us in touch, I'd be happy to setup a video call to live debug.
Also, if you're using the com.example.measurement.sampleapp
package name, that is included in the allowlist by default
Thanks @erintwalsh for the live debugging session. As discussed, the issue has to do with our enrollment and not with the app.
This is the same issue as described in #56. It fails in my app, but the same error also appears in the Measurement Sample App (in this repo) - which are the error logs described below
Android Studio Version: Hedgehog | 2023.1.1 Canary 10
On fresh 'main' branch using the following commands
Setting up the device with the following adservices shell commands
I get the following error and log snippets when try to register a source attribution via "Register Click Event"
On fresh 'dev-preview-main' branch using the following commands
Setting up the device with the following adservices shell commands
I get the following error and log snippets when try to register a source attribution via "Register Click Event"