App version: 1.13.0, downloads don't work

[HughisaName]

Checklist

• I'm reporting a bug unrelated to a specific site.
• I've verified that I'm running the latest version of yt-dlp.
• I've verified that I'm running the latest stable version of Seal or any later preview versions.
• I've read the Contributing guidelines and Code Of Conduct.
• I've checked that the site i'm trying to download from is in the Supported Sites list from yt-dlp
• I understand that the issue will be (ignored/closed) if I intentionally remove or skip any mandatory field.

Describe the bug

Trying to use quick download however it errors out, cannot fetch information

To Reproduce

From insta or FB
Tap share
Tap seal quick download

Error reports

App version: 1.13.0 (11302)
Device information: Android 14 (API 34)
Supported ABIs: [arm64-v8a]
Yt-dlp version: 2024.10.01.232843

URL: https://www.instagram.com/reel/DA1se3APJqY/?igsh=c2hrOGxsYm1ibHBu
WARNING: [Instagram] DA1se3APJqY: General metadata extraction failed (some metadata might be missing).
WARNING: [Instagram] unable to extract shared data; please report this issue on https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using yt-dlp -U
WARNING: [Instagram] Main webpage is locked behind the login page. Retrying with embed webpage (some metadata might be missing).
WARNING: [Instagram] unable to extract additional data; please report this issue on https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using yt-dlp -U
ERROR: [Instagram] DA1se3APJqY: Requested content is not available, rate-limit reached or login required. Use --cookies, --cookies-from-browser, --username and --password, --netrc-cmd, or --netrc (instagram) to provide account credentials

Screenshots & Screen Records

Additional context

No response

[github-actions]

This issue has been closed and labeled as duplicate. Please see issue #1399 for more details. If you believe this is not the case, you can reopen this issue.