Start with autopilot not working

[nvanderperren]

I've tested it with instagram and facebook, but whenever I start with autopilot, it's just not recording anything. It says it's done after capturing 0 posts. In Instagram autopilot is even done before the page is fully loaded.

I use archiveweb v0.11.2 and chrome Version 116.0.5845.140 on a macos Ventura (13.0).

[Lod3]

Same problem here on Windows
I noticed the autopilot function is not working in the archiveweb.page extension version v0.11.2.
Tested in Chrome official build: Version 116.0.5845.141
Archiveweb.page extension status: Idle, Continue Browsing.
With or without "start with autopilot" option enabled.
When I start archiving without "start with autopilot" option enabled the page scrolls down a little then back up and does not move.
With the "start with autopilot" option enabled it does not move.

[edsu]

I tested with v0.11.1 by installing the old version and can confirm that starting with autopilot fails with Instagram. So the breakage isn't a regression, and appears to be the result of some change on the Instagram side? I didn't test with Facebook.

I noticed that if you start without Autopilot turned on, and wait for the page to load completely (Idle, Continue Browsing displayed) and then click Start Autopilot the behavior seems to work ok? So maybe there is some kind of timing issue, or error that prevents the Autopilot from starting correctly?

[nvanderperren]

For Instagram that solves the problem (although there seems a problem with the behavior, cause only the first post of each row gets crawled), but it's not working on Facebook.

[katrienwe]

I also tried Facebook using v0.11.2 on Windows, but get also the "Idle, Continue Browsing". When stopping and starting again the auto pilot (in the scenario where it is directly on when starting AND when it is activated during the process) always has the same behavior. It continues for some moments and ends with "Idle, Continue Browsing".

[edsu]

It looks like the Instagram side of this got an issue over in webrecorder/browsertrix-behaviors#58 but not the FB side.

[nvanderperren]

I added the issue, but issues there seem to get little response.