You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am following the sample app to generate sources and triggers. When I force the reporting jobs to run, they always fail with SSLHandshakeException which I am guessing because the device system time is too far in the future.
Caused by: java.security.cert.CertPathValidatorException: Response is unreliable: its validity interval is out-of-date
I have set the sources to the minimum expiry possible (1 day) in the hopes that the reporting jobs would run earlier, however, the reporting jobs only attempt to run after setting the device time to at least 7 days in the future. Are there any parameters I should be trying in my sources and triggers? What is the recommended approach to have the reporting jobs run successfully?
Just came to say that setting the aggregatable_report_window to a smaller duration in the source header allowed me to generate a report without encountering the SSL issue above.
I'll leave this issue open and allow the authors to comment on whether this specific instruction belongs in the README for attribution reporting api.
I am following the sample app to generate sources and triggers. When I force the reporting jobs to run, they always fail with SSLHandshakeException which I am guessing because the device system time is too far in the future.
Caused by: java.security.cert.CertPathValidatorException: Response is unreliable: its validity interval is out-of-date
I have set the sources to the minimum expiry possible (1 day) in the hopes that the reporting jobs would run earlier, however, the reporting jobs only attempt to run after setting the device time to at least 7 days in the future. Are there any parameters I should be trying in my sources and triggers? What is the recommended approach to have the reporting jobs run successfully?
Thanks!
https://gist.github.com/allen-branch/fb922456668db83676ff251ddda5ef8f
The text was updated successfully, but these errors were encountered: