Problem Handling `google.protobuf.Struct` Nested Fields in gRPC Requests

Bug Report
1

Hello,

I am experiencing issues with Apidog when sending gRPC requests that include nested fields using the google.protobuf.Struct type. Specifically, I am trying to send a message with a structure like the following (see JSON example below), but the value of categorization is not being parsed or read correctly in the server response:

json

{
    "title": "Compra en MERCADONA AS LAGOAS",
    "amount": -23.3,
    "accountingDate": "2025-04-16T08:25:00",
    "predictions": {
        "fields": {
            "categorization": {
                "struct_value": {
                    "fields": {
                        "subcategory": {
                            "string_value": "Proveedores"
                        },
                        "categoryCode": {
                            "number_value": 6010
                        },
                        "category": {
                            "string_value": "Compras/Gastos"
                        }
                    }
                }
            }
        }
    }
}

My Protobuf definition for the relevant message is:

text

syntax = "proto3";

import "google/protobuf/struct.proto";

message CocoMovementModel {
    // ... other fields
    google.protobuf.Struct predictions = 14;
}

When I send this request using Apidog, the server returns the following error:

text

Error: Exception calling application: 'NoneType' object has no attribute 'categorization'

I have tried adjusting the JSON format and checked my import settings for .proto files, but the field is still not parsed correctly. Other tools (like grpcurl or custom clients) work as expected.

Steps to reproduce:

  1. Create a gRPC project in Apidog and import the .proto file as shown above.
  2. Send a request with the JSON body provided.
  3. Observe that the categorization field in the Struct is not received/parsed correctly by the server, causing the above error.

Additional Info:

  • Apidog version: 2.7.38

Is there any recommended workaround or upcoming fix for handling complex structs in gRPC requests with Apidog? Thanks for your support!

2

Hello, thank you for your feedback. I will report this issue to our engineering team for further investigation.