UPSTREAM FIX

magento2-37746: GraphQL wishlist query returns Missing key "model" in Wishlist value data

Community fix magento2-37746 merged into magento/magento2 on 2026-07-17, not in a release yet; applies cleanly to 27 releases from 2.4.6 to 2.4.7-p10.

GraphQL wishlist query returns Missing key "model" in Wishlist value data edited

Pull request title: Missing key \"model\" in Wishlist value data
Pull request: magento/magento2#37746
Issues: #36909 human
Author: @Vasudev-22
Merged: 2026-07-17
Fixed in: no release yet
Reported on: 2.4.5-p1
Categories: —
Components: magento/module-wishlist-graph-ql

Labels

Area: Product
Component: Wishlist
Priority: P2
Severity: —
Reported on (labels): 2.4.5-p1

Issue

Title and steps come from the upstream issue and pull request.

Description

{
    "errors": [
        {
            "debugMessage": "Missing key \"model\" in Wishlist value data",
            "message": "Internal server error",
            "category": "internal",
            "locations": [
                {
                    "line": 3,
                    "column": 5
                }
            ],
            "path": [
                "wishlist",
                "items"
            ]
        }
    ],
    "data": {
        "wishlist": {
            "items": null,
            "items_count": null,
            "sharing_code": null
        }
    }
}

Steps to reproduce

1. Create a customer

mutation {

  createCustomer(

    input: {

      firstname: "John"

      lastname: "Doe"

      email: "test1@example.com"

      password: "Test1234"

      is_subscribed: true

    }

  ) {

    customer {

      firstname

      lastname

      email

      is_subscribed

    }

  }

}

2. Get a graphQL token

mutation {
  generateCustomerToken(email: "test1@example.com", password: "Test1234") {
    token
  }
}

3. Query wishlist

query {
  wishlist {
    items {
      added_at
      description
      id

      product {
        name
        image {
          url
        }
        sku
      }
      qty
    }
    items_count
    sharing_code
  }
}

Expected result

    "data": {
        "wishlist": {
            "items": null,
            "items_count": null,
            "sharing_code": null
        }
    }

Actual result

{
    "errors": [
        {
            "debugMessage": "Missing key \"model\" in Wishlist value data",
            "message": "Internal server error",
            "category": "internal",
            "locations": [
                {
                    "line": 3,
                    "column": 5
                }
            ],
            "path": [
                "wishlist",
                "items"
            ]
        }
    ],
    "data": {
        "wishlist": {
            "items": null,
            "items_count": null,
            "sharing_code": null
        }
    }
}

Taken from the upstream issue.

Code match per tag

Each tag was checked with git apply --check against that tag's files. A clean match means the change applies; it is not a test result. Tags that already contain the fix are marked.

Line	Code match per tag	Tests
2.4.6	2.4.6 clean 2.4.6-p1 clean 2.4.6-p2 clean 2.4.6-p3 clean 2.4.6-p4 clean 2.4.6-p5 clean 2.4.6-p6 clean 2.4.6-p7 clean 2.4.6-p8 clean 2.4.6-p9 clean 2.4.6-p10 clean 2.4.6-p11 clean 2.4.6-p12 clean 2.4.6-p13 clean 2.4.6-p14 clean 2.4.6-p15 clean	2.4.6: no test data 2.4.6-p1: no test data 2.4.6-p2: no test data 2.4.6-p3: no test data 2.4.6-p4: no test data 2.4.6-p5: no test data 2.4.6-p6: no test data 2.4.6-p7: no test data 2.4.6-p8: no test data 2.4.6-p9: no test data 2.4.6-p10: no test data 2.4.6-p11: no test data 2.4.6-p12: no test data 2.4.6-p13: no test data 2.4.6-p14: no test data 2.4.6-p15: no test data
2.4.7	2.4.7 clean 2.4.7-p1 clean 2.4.7-p2 clean 2.4.7-p3 clean 2.4.7-p4 clean 2.4.7-p5 clean 2.4.7-p6 clean 2.4.7-p7 clean 2.4.7-p8 clean 2.4.7-p9 clean 2.4.7-p10 clean	2.4.7: no test data 2.4.7-p1: no test data 2.4.7-p2: no test data 2.4.7-p3: no test data 2.4.7-p4: no test data 2.4.7-p5: no test data 2.4.7-p6: no test data 2.4.7-p7: no test data 2.4.7-p8: no test data 2.4.7-p9: no test data 2.4.7-p10: no test data
2.4.8	2.4.8 conflict 2.4.8-p1 conflict 2.4.8-p2 conflict 2.4.8-p3 conflict 2.4.8-p4 conflict 2.4.8-p5 conflict	2.4.8: no test data 2.4.8-p1: no test data 2.4.8-p2: no test data 2.4.8-p3: no test data 2.4.8-p4: no test data 2.4.8-p5: no test data
2.4.9	2.4.9 conflict	2.4.9: no test data

Triage

Model @cf/cloudflare/clef. Probability this is a bug fix: 98.4%. Probability it is security relevant: 1.6%.

Show the model's answers and probabilities

Question	Answer	Probabilities	Confidence
Change kind	bugfix	bugfix 97.3%, refactor 1.1%, tests_only 0.5%, feature 0.5%, dependency 0.4%, docs_only 0.3%	93.7%
Area	graphql_api	graphql_api 93.1%, customer 3.1%, other 1.2%	85.0%
Reported version	2.4.5-p1	2.4.5-p1 58.6%, 2.4.5 5.5%, 2.4.5-p4 1.5%	34.1%
Scope	0.69 of 2	1 47.4%, 0 42.0%, 2 10.6%	11.9%
Risk	0.21 of 2	0 82.2%, 1 14.5%, 2 3.4%	54.5%
Worth backporting	1.73 of 2	2 77.7%, 1 17.6%, 0 4.7%	45.5%

Download

For cweagans/composer-patches, choose a version below and download the bundle. Copy its magento2-37746/ folder into patches/composer/, merge composer.patches.json into composer.json, then run composer install. Test files are always removed; paths are relative to each package root, using the default -p1 level.

Bundle README (what the ZIP ships)

# magento2-37746

Community fix merged upstream into magento/magento2, adapted by magento.watch.
This is not a patch published by Adobe.

Pull request: https://github.com/magento/magento2/pull/37746
Issue: https://github.com/magento/magento2/issues/36909
Author: @Vasudev-22
Source commit: 38af8e2f1276d77cd7f0b16a62fc63b5277fa82a
Modifications: test files and documentation removed, paths rewritten relative to each Composer package.
Licence: OSL-3.0 / AFL-3.0, as the original Magento Open Source code.
Maintainer: Łukasz Bajsarowicz (@lbajsarowicz)

Licence: Magento Open Source code under OSL-3.0 and AFL-3.0. The bundle carries the original author, source commit and the list of modifications.