GraphQL Bundle Options could not resolved via `customer` query

[larsroettig]

Preconditions (*)

1. Open Source 2.4.3

Steps to reproduce (*)

1. Create Bundle Product with one Select
2. Order this Bundle
3. Use GraphQL to fetch Customer Orders

Expected result (*)

• No Error for this Request

Actual result (*)

Problem is in

magento2/app/code/Magento/BundleGraphQl/Model/Resolver/Order/Item/BundleOptions.php

Line 151 in eadd3a9

implode(',', $options),

Options: Could be a string if you only one Bundle Option

Query

{
  customer {
    orders(pageSize: 20) {
      items {
        id
        order_date
        total {
          grand_total {
            value
            currency
          }
        }
        items {
          product_name
          ... on BundleOrderItem {
            id
            product_name
            entered_options {
              label
              value
            }
            selected_options {
              label
              value
            }
            bundle_options {
              id
              label
              uid
              values {
                product_sku
              }
            }
          }
          __typename
        }
        status
      }
    }
  }
}

Error

 "errors": [
    {
      "debugMessage": "Warning: implode(): Invalid arguments passed in module-bundle-graph-ql\/Model\/Resolver\/Order\/Item\/BundleOptions.php on line 151",
      "message": "Internal server error",
      "extensions": {
        "category": "internal"
      },
      "locations": [
        {
          "line": 26,
          "column": 13
        }
      ],
      "path": [
        "customer",
        "orders",
        "items",
        0,
        "items",
        0,
        "bundle_options"
      ]
    }
  ],

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[github-jira-sync-bot]

Unfortunately, not enough information was provided to create a Jira ticket. Please make sure you added the following label(s): Reproduced on 2.4.x, ^Area:.*

Once all required labels are present, please add Issue: Confirmed label again.

[github-jira-sync-bot]

Unfortunately, not enough information was provided to create a Jira ticket. Please make sure you added the following label(s): Reproduced on 2.4.x, ^Area:.*

Once all required labels are present, please add Issue: Confirmed label again.