updateCustomer Query unable to update ShippingAddress

[alejdig]

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

1. Use the UpdateCustomerMutation

2. Send a Payload that uses billing such as

   const res = await client.mutation({
     updateCustomer: {
       __args: {
         input: {
           id,
           email,
           lastName,
           firstName,
           **shipping**
         },
       },
       __scalar: true,
     },
   });

3. See Error Network response was not ok. Status: 403

4. Use the mutation with the billing Address Instead

5 Billing Address gets updated, error Code is still 403. Network response was not ok. Status: 403 but the changes do get reflected in the response

Expected behavior Should update the shipping address

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Plugin Versions

• WPGraphQL Version: 0.2.0
• WordPress Version: 6.5.3
• WooCommerce Version: 8.8.3

Additional context Add any other context about the problem here. Network response was not ok. Status: 403

[alejdig]

This is very interesting, as can be seen, i get a forbidden 403 response but the edit still goes through?

https://github.com/wp-graphql/wp-graphql-woocommerce/assets/139802813/51e7e746-67bf-47b9-9d4f-a2a885a038a7

Invalid Secret key

{
                "type": "GRAPHQL_DEBUG",
                "message": "invalid-secret-key | Signature verification failed",
                "stack": [
                    "\/var\/www\/vhosts\...com\/wp-content\/plugins\/wp-graphql-headless-login\/src\/Auth\/Request.php:33"

[alejdig]

Solved: This happened because i had https://github.com/wp-graphql/wp-graphql-jwt-authentication installed and i was using it's jwtRefreshToken instead of the authToken from headless-login