When I run MeasurementSampleAppdemo. How do I tell where the problem is?

[lezh666]

I downloaded and ran the MeasurementSampleApp demo in the dev-preview-main branch. I replaced DEFAULT_SERVER_URL with the address given by the server, and I clicked the Register Click Event button and the Register Trigger button. And use the command adb shell cmd jobscheduler run -f com.google.android.adservices.api 5 adb shell cmd jobscheduler run -f com.google.android.adservices.api 3 to generate the attribution report. But our server did not receive any message. How can I tell whether there is a problem on the client side or on the server side?

Android studio logcat 2023-12-14 14:28:42.877 3929-3929 adservices com.example.measurement.sampleapp D registerSource 2023-12-14 14:28:42.883 3929-3929 adservices com.example.measurement.sampleapp D bindService: android.adservices.MEASUREMENT_SERVICE 2023-12-14 14:28:43.002 26878-28492 ActivityManager system_server D sync unfroze 27803 com.google.android.adservices.api for 6 2023-12-14 14:28:43.028 3929-3929 adservices com.example.measurement.sampleapp D bindService() started... 2023-12-14 14:28:43.114 27803-27803 adservices com.google.android.adservices.api D AggregateReportingJobService already scheduled, skipping reschedule 2023-12-14 14:28:43.120 27803-27803 adservices com.google.android.adservices.api D AggregateFallbackReportingJobService already scheduled, skipping reschedule 2023-12-14 14:28:43.143 27803-27803 adservices com.google.android.adservices.api D AttributionJobService already scheduled, skipping reschedule 2023-12-14 14:28:43.148 27803-27803 adservices com.google.android.adservices.api D AttributionFallbackJobService already scheduled, skipping reschedule 2023-12-14 14:28:43.157 27803-27803 adservices com.google.android.adservices.api D EventReportingJobService already scheduled, skipping reschedule 2023-12-14 14:28:43.173 27803-27803 adservices com.google.android.adservices.api D EventFallbackReportingJobService already scheduled, skipping reschedule 2023-12-14 14:28:43.183 27803-27803 adservices com.google.android.adservices.api D DeleteExpiredJobService already scheduled, skipping reschedule 2023-12-14 14:28:43.185 27803-27803 adservices com.google.android.adservices.api E DeleteUninstalledJobService is disabled, skip scheduling 2023-12-14 14:28:43.193 27803-27803 adservices com.google.android.adservices.api D Maintenance Periodic Task has been scheduled with same parameters, skip rescheduling! 2023-12-14 14:28:43.199 27803-27803 adservices com.google.android.adservices.api D Maintenance Periodic Task has been scheduled with same parameters, skip rescheduling! 2023-12-14 14:28:43.207 27803-27803 adservices com.google.android.adservices.api D Maintenance Periodic Task has been scheduled with same parameters, skip rescheduling! 2023-12-14 14:28:43.217 27803-27803 adservices com.google.android.adservices.api D Maintenance Periodic Task has been scheduled with same parameters, skip rescheduling! 2023-12-14 14:28:43.226 27803-27803 adservices com.google.android.adservices.api D AsyncRegistrationQueueJobService already scheduled, skipping reschedule 2023-12-14 14:28:43.238 27803-27803 adservices com.google.android.adservices.api D AsyncRegistrationFallbackJobService already scheduled, skipping reschedule 2023-12-14 14:28:43.257 27803-27803 adservices com.google.android.adservices.api D DebugReportingFallbackJobService already scheduled, skipping reschedule 2023-12-14 14:28:43.275 27803-27803 adservices com.google.android.adservices.api D VerboseDebugReportingFallbackJobService already scheduled, skipping reschedule 2023-12-14 14:28:43.287 3929-3966 adservices com.example.measurement.sampleapp D onServiceConnected android.adservices.MEASUREMENT_SERVICE 2023-12-14 14:28:43.294 3929-3929 adservices com.example.measurement.sampleapp D bindService: android.adservices.ADID_SERVICE 2023-12-14 14:28:43.312 3929-3929 adservices com.example.measurement.sampleapp D bindService() started... 2023-12-14 14:28:43.319 3929-3966 adservices com.example.measurement.sampleapp D onServiceConnected android.adservices.ADID_SERVICE 2023-12-14 14:28:43.361 27803-32385 adservices com.google.android.adservices.api V Process 10183 has importance 100 comparing with threshold of 125. 2023-12-14 14:28:43.372 27803-32385 adservices com.google.android.adservices.api V AdIdWorker.getAdId for com.example.measurement.sampleapp, 10183 2023-12-14 14:28:43.402 27803-32385 adservices com.google.android.adservices.api D bindService: android.adservices.adid.AdIdProviderService 2023-12-14 14:28:43.574 27803-32385 adservices com.google.android.adservices.api D bindService() started... 2023-12-14 14:28:43.751 27803-3749 adservices com.google.android.adservices.api D onServiceConnected android.adservices.adid.AdIdProviderService 2023-12-14 14:28:43.755 3929-3929 adservices com.example.measurement.sampleapp W AdId call timed out 2023-12-14 14:28:43.755 3929-3929 adservices com.example.measurement.sampleapp D Registering source 2023-12-14 14:28:43.806 27803-32386 adservices com.google.android.adservices.api V Process 10183 has importance 100 comparing with threshold of 125. 2023-12-14 14:28:43.901 27803-3749 adservices com.google.android.adservices.api D unbinding... 2023-12-14 14:28:43.909 27803-32386 adservices com.google.android.adservices.api D MeasurementDao: insertAsyncRegistration: rowId=119 2023-12-14 14:28:43.921 3929-4695 adservices com.example.measurement.sampleapp D AdId permission enabled true 2023-12-14 14:29:41.830 3929-3929 adservices com.example.measurement.sampleapp D registerTrigger 2023-12-14 14:29:41.847 27803-28089 adservices com.google.android.adservices.api V Process 10183 has importance 100 comparing with threshold of 125. 2023-12-14 14:29:41.852 27803-28089 adservices com.google.android.adservices.api V AdIdWorker.getAdId for com.example.measurement.sampleapp, 10183 2023-12-14 14:29:41.859 27803-28089 adservices com.google.android.adservices.api D bindService: android.adservices.adid.AdIdProviderService 2023-12-14 14:29:42.096 27803-28089 adservices com.google.android.adservices.api D bindService() started... 2023-12-14 14:29:42.246 3929-3929 adservices com.example.measurement.sampleapp W AdId call timed out 2023-12-14 14:29:42.249 3929-3929 adservices com.example.measurement.sampleapp D Registering trigger 2023-12-14 14:29:42.324 27803-32383 adservices com.google.android.adservices.api V Process 10183 has importance 100 comparing with threshold of 125. 2023-12-14 14:29:42.341 27803-3749 adservices com.google.android.adservices.api D onServiceConnected android.adservices.adid.AdIdProviderService 2023-12-14 14:29:42.405 27803-32383 adservices com.google.android.adservices.api D MeasurementDao: insertAsyncRegistration: rowId=120 2023-12-14 14:29:42.509 27803-3749 adservices com.google.android.adservices.api D unbinding... 2023-12-14 14:29:42.558 3929-4695 adservices com.example.measurement.sampleapp D AdId permission enabled true 2023-12-14 14:30:40.056 26878-28111 JobScheduler system_server D executeRunCommand(): com.google.android.adservices.api/null/0 5 s=false f=true 2023-12-14 14:30:40.075 27803-27803 adservices com.google.android.adservices.api D AttributionJobService.onCreate 2023-12-14 14:30:40.143 27803-27803 adservices com.google.android.adservices.api D AttributionJobService.onStartJob 2023-12-14 14:30:40.176 27803-32385 adservices com.google.android.adservices.api D Scheduled AttributionJobService 2023-12-14 14:30:40.181 27803-32385 adservices com.google.android.adservices.api D DebugReportingJobService already scheduled, skipping reschedule 2023-12-14 14:30:57.602 26878-27201 JobScheduler system_server D executeRunCommand(): com.google.android.adservices.api/null/0 3 s=false f=true 2023-12-14 14:30:57.633 27803-27803 adservices com.google.android.adservices.api D EventReportingJobService.onStartJob:

[erintwalsh]

Hi @lezh666, apologies that this hasn't been answered yet. Are you still experiencing issues?

For general debugging - I would recommend running the sample app on the main branch. There are multiple reasons why the server wouldn't be receiving the report, so I would also recommend setting up debug reports, as those will provide useful information on whether sources and triggers were registered correctly, and if not, why.