igpapi — Instagram private API Simulator for Node.js (API reference) 4.19.0
    Preparing search index...

    Variable DirectGroupNameAndPhotoEditorScreenConst

    DirectGroupNameAndPhotoEditorScreen: ScreenDefinition<
        "DirectGroupNameAndPhotoEditor",
        "screen",
        { is_group: boolean; thread_title: string; thread_v2_id: string },
        { is_group: boolean; thread_title: string; thread_v2_id: string },
        { is_group: boolean; thread_title: string; thread_v2_id: string },
        never,
        MobileNavigation,
        DirectGroupNameAndPhotoEditorActions,
        Record<never, never>,
        never,
        "thread_v2_id",
    > = ...

    ThreadDetailsCustomGroupNameAndImageFragment, the screen where a group thread's name and photo are edited. The fragment class stays the screen's catalog identity; the public name says what the person edits on it.

    What a person sees: the group's current name. The fragment also names the group picture, but the picture change is not modelled, so the handle carries no picture and the screen models none.

    Actions: changeName(name) sends the thread's update_title request with the new name; the thread id and the current name are the screen's input and state, never caller-typed literals. Opening the screen sends nothing.

    How it is reached: from the thread's shared media (openGroupNameEditor), which the details hub opens (openSharedMedia), which the conversation opens (openThreadDetails). The screen opens on whatever thread the caller names: the library does not copy which screens the app offers for which kind of thread (owner, 2026-10-29), and the server decides what a request does.

    The Android 451 chain is direct_thread:3 → details 7 → shared media 8 → this screen 9, and update_title is its request. The group picture's request is not known.

    Guide: The group name and photo editor