400 Bad Request; You'll need to update Instagram to the latest version before you can use the app.

[tada123]

400 Bad Request; You'll need to update Instagram to the latest version before you can use the app.

[apabinc]

I can confirm as well. I'm seeing the same behavior and until Mar 1 2024 the login was working

[prokoposgiannis]

Me too, I've been seeing the same error since March 2 while trying to upload a story on instagram.

[CaptainTron]

for now you can use this but make sure the filetype should be of .jpg
`
require("dotenv").config();

const express = require('express')
const app = express()
const port = process.env.PORT || 4000;
const fs = require('fs');

app.listen(port, () => {
console.log(Listening on port ${port})
})

const { IgApiClient } = require('instagram-private-api');
const { get } = require('request-promise');

const postToInsta = async () => {

const ig = new IgApiClient();
ig.state.generateDevice(process.env.IG_USERNAME);
await ig.account.login(process.env.IG_USERNAME, process.env.IG_PASSWORD);

const imageFilePath = '222.jpg';

try {
    const imageBuffer = fs.readFileSync(imageFilePath);

    const publish = await ig.publish.photo({
        file: imageBuffer,
        caption: 'RTTTT',
    });

    console.log(publish)

} catch (error) {
    console.error('Error reading the image file:', error);
}

}

postToInsta()`

[tiagobbraga]

It's very funny... At localhost it works, but without session.

async #login(username, password, agent) {
    this.#client = new IgApiClient();
    this.#client.state.generateDevice(username);
    this.#client.request.defaults.agent = agent;

    // this.#client.request.end$.subscribe(async () => {
    //   const serialized = await this.#client.state.serialize();
    //   console.log("serialized");
    //   delete serialized.constants; // this deletes the version info, so you'll always use the version provided by the library
    //   this.#saveSession(serialized);
    // });

    // if (this.#existsSession()) {
    //   console.log("exists");
    //   const session = await this.#loadSession();
    //   if (session && Object.keys(session).length > 0) {
    //     console.log("deserialize");
    //     await this.#client.state.deserialize(session);
    //     return;
    //   }
    // }

    console.log("login");
    await this.#client.account.login(username, password);
  }

Works with the latest version 1.46.1!

Thanks @Nerixyz

[Neoxsam]

Same here

[apabinc]

The current workaround is to overwrite the instagram-private-api package in your package.json like this:

  "dependencies": {
    ...
    "instagram-private-api": "Nerixyz/instagram-private-api#update-constants",
    ...
  }

Kudos to @Nerixyz

Reference: #1572

[dilame]

Could anyone check if it works now?

[amoraschi]

Could anyone check if it works now?

I get this error when trying to publish anything (post/story):

C:\...\node_modules\instagram-private-api\dist\core\state.js:143
            throw new errors_1.IgCookieNotFoundError(key);
                  ^

IgCookieNotFoundError: Cookie "ds_user_id" not found

[tiagobbraga]

It's very funny... At localhost it works, but without session.

async #login(username, password, agent) {
    this.#client = new IgApiClient();
    this.#client.state.generateDevice(username);
    this.#client.request.defaults.agent = agent;

    // this.#client.request.end$.subscribe(async () => {
    //   const serialized = await this.#client.state.serialize();
    //   console.log("serialized");
    //   delete serialized.constants; // this deletes the version info, so you'll always use the version provided by the library
    //   this.#saveSession(serialized);
    // });

    // if (this.#existsSession()) {
    //   console.log("exists");
    //   const session = await this.#loadSession();
    //   if (session && Object.keys(session).length > 0) {
    //     console.log("deserialize");
    //     await this.#client.state.deserialize(session);
    //     return;
    //   }
    // }

    console.log("login");
    await this.#client.account.login(username, password);
  }

[razbakov]

Issue is fixed with 1.46.1. Thanks @Nerixyz