This message was deleted.

Hi Jean-Michel All Build Scans sent to scans.gradle.com need to be activated. This is because there is no permission model there, at least for now, and we need a way to associate a Build Scan to a user for “ownership”. Now, if you tick the “Remember me” box when you activate a Build Scan, and use the same browser again when accessing an unactivated Build Scan later on, then “auto-activation” will kick in and auto-activate that new Build Scan for you. This works for a month before manual activation steps are required again. If you use another browser to activate a Build Scan, the activation process kicks in.

ah ok, the auto-activation is simply valid for a month. thanks

yes, it’s cookie-based with a 1 month expiration period

@François Guillot In practice though I had to through the

Active your Build Scan

processus 6 times in the last month including today, yersterday and two days ago. I am always using the same Firefox for macOS browser on the same iMac computer

=> solution was to clear all cookies because old ones were there (they should have been removed but the deletion logic somehow didn’t work)