<@U04S8PLJWMT> getting below error on google ads s...
# replication-ask-ai
m
@kapa.ai getting below error on google ads source Config validation error: None is not of type 'string'
k
Config validation error: None is not of type 'string' in Google Ads Source This is a known issue. Here's what's happening and what you can do: Root Cause The error occurs when a null/None value appears in an optional config field that the connector's JSON schema only accepts as
type: string
. The CDK's config validation then rejects it with
None is not of type 'string'
. [GitHub Issue] Known Triggers for Google Ads 1.
customer_id
/
customer_ids
field handling
— The connector internally transforms
customer_id
(singular string) into
customer_ids
(list). If either field ends up as
None
in the config, validation fails. [source.py] 2. Platform-level null injection — In abctl/Kubernetes deployments, the Airbyte platform can inject
null
values for optional fields into the connector config, which then fails schema validation. [GitHub Issue] Recommended Steps 1. Ensure all required fields are non-null strings in your source configuration: ◦
client_id
◦
client_secret
◦
refresh_token
◦
developer_token
◦
customer_id
(provide as a comma-separated string, e.g.
"1234567890"
) 1. Do not leave optional fields as empty strings or null — for example, if
end_date
is not needed, omit it entirely rather than passing
null
or
""
. The connector explicitly handles empty
end_date
by removing it. [source.py] 2. Use
customer_id
(singular string) when creating via API
, not
customer_ids
(list) — the connector spec expects the singular form and converts it internally. Platform-Level Issue The 422 error on
updateSource
after a failed check/discover is a platform infrastructure bug (not a connector bug), already routed to the Airbyte platform team. [GitHub Issue] A similar fix was applied to other connectors (e.g., Amazon Seller Partner) by updating optional field schemas to accept
["string", "null"]
and patching the CDK to strip null values before validation. [CDK fix PR] A similar fix may be needed for the Google Ads connector — you may want to follow or comment on GitHub Issue #60900 for updates. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
m
@kapa.ai i am providing every optional field but still getting same error
k
I'm sorry, but the knowledge sources do not contain enough information to provide a definitive solution for your specific case where all optional fields are provided but the error persists. Based on what the knowledge sources do describe, here are the most relevant points: What the logs confirm Even when all fields are correctly provided, the error can still occur because: • The Airbyte platform itself injects null values into the connector config at runtime (in abctl/Kubernetes deployments), overriding what you originally configured. This is a platform-level bug, not something you can fix by adjusting your config. [GitHub Issue] • The connector sidecar then attempts to call
updateSource
with the modified config, which fails with
422 Unprocessable Entity
. [GitHub Issue] What has been confirmed by the Airbyte team > "This appears to be a platform infrastructure error, not a connector bug. Routing to the platform team." [GitHub Issue] Suggested next steps 1. Check your deployment type — if you are on `abctl`/Kubernetes, this is a known open issue with no confirmed fix yet in the knowledge sources. 2. Try Airbyte Cloud — the same credentials have been confirmed to work on Airbyte Cloud even when failing on OSS. [GitHub Issue] 3. Follow or comment on GitHub Issue #60900 directly — this is the active tracking issue and the best place to get updates from the platform team. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.