A 17 hour old approval resumed a background task that played a video into his real account history
A background task asked from an iPhone to open a YouTube video was blocked on a site approval, and the prompt waited about 17 hours. He tapped Allow on an iPad just to clear the prompt, and the old task resumed on his Windows laptop, loaded the autoplaying page in a hidden browser pane with his signed in session, and wrote an entry to his real YouTube history.
This one went wrong. Read what happened so you don’t hit the same problem.
How it works
- A background task started from Dispatch on an iPhone asks to open a YouTube video in the built in browser pane
- Navigation is blocked and the task parks on an approval prompt
- About 17 hours later he opens Dispatch on an iPad, finds the prompt waiting, and taps Allow to clear it so he can type an unrelated question
- The day old task resumes on his Windows laptop
- The page loads for the first time in a browser pane with no visible window, autoplays with sound, and writes an entry to his real YouTube account history
Why it’s worth knowing
Three devices each saw only part of one action: the request on a phone, the approval on a tablet, and the result on a laptop, a day later.
Where it’s from
Summarized from a public post on github.com. See the original ↗