@kapa.ai Any known workaround for the Apple Search Ads #48573 bug ? The V4 API of Apple Search Ads is decomissioned tomorrow and we're trying to move to Airbyte's connector 0.3.1, but we're getting the

failed with status code '400' and error message 'The request needs to ask for rowTotals or granularity to fetch data'\")"

error when upgrading.

Based on the knowledge sources provided, there doesn't seem to be specific information about a workaround for the Apple Search Ads bug #48573 or the error message you're encountering. However, I can provide some relevant information and suggestions based on the available sources: 1. The Apple Search Ads connector has been updated to version 0.3.0 to support the V5 API. This update was made in preparation for the V4 API being decommissioned, as mentioned in the [Changelog](https://docs.airbyte.com/integrations/sources/apple-search-ads#changelog). 2. There was a known issue with the OAuth authentication process for the Apple Search Ads connector, which was fixed in version 0.2.1. This fix set the authentication grant_type to client_credentials, as noted in the [Github issue #46879](https://github.com/airbytehq/airbyte/issues/46879). 3. For the specific error you're encountering, the knowledge sources don't provide a direct solution. However, the error message suggests that the request needs to include rowTotals or granularity parameters to fetch data. This might be related to changes in the V5 API requirements. Given this information, here are some suggestions: 1. Ensure you're using the latest version of the Apple Search Ads connector (0.3.1 as you mentioned). 2. Double-check your connector configuration, especially any settings related to data granularity or row totals. 3. Review the Apple Search Ads API V5 documentation to see if there are any new requirements for data requests that might not be reflected in the current connector version. 4. If the issue persists, it would be advisable to report this specific error to the Airbyte community or support channels, as it might be a new bug that hasn't been addressed yet. Unfortunately, the knowledge sources don't provide a direct workaround for your specific error. You may need to reach out to Airbyte support or create a new issue on their GitHub repository with the details of this error for further assistance.