Did you see a warning first, @Fatso?
Have you hard-refreshed your browser? Or closed and re-opened it on mobile?