Closed daytenjs closed 7 months ago
Moreover, when I "refresh source schema" in the replication tab of the connection settings, it tells me it removes the table (that I have successfully imported many times)
This connector would also greatly benefit from a "full overwrite" setting... so that if it skips dates, it will pick them up on later syncs...
Thanks @daytenjs, I triaged and added this ticket to the team's backlog!
@sajarin this is because the source is using version 1_2
for most of those reports which is no longer support by App Store Connect. Effectively the source is mostly broken and wont pull those vital reports anymore. Should be a three character change to get the source to pull using the correct version key.
For more information: https://developer.apple.com/documentation/appstoreconnectapi/download_sales_and_trends_reports#3022173
References in the Airbyte source: https://github.com/airbytehq/airbyte/blob/2da66e9cf14976b243e330ea39b7469a3d11813f/airbyte-integrations/connectors/source-appstore-singer/source_appstore_singer/source.py#LL40C13-L50C14
The App Store connector has been archived and won't get updates in the future. We're closing this issue to focus on features and connectors in our roadmap. Thanks for understanding! 🚀
Environment
Current Behavior
I get like 8 print outs of the following:
I also get
despite definitely having data for that date.
The job ends up skipping like half the dates (that I know are in fact there), and I'm getting massively incomplete data, with entire weeks skipped.
Expected Behavior
I've already gotten all the data before, suddenly it stopped syncing (with no user changes) latest dates, on a reset and re-sync these issues started. The "invalid vendor id" issue has been around since I started using the connector. The vendor id works fine when I use python to call the Appstore API.
Logs
3878c2c0_44b4_428b_b671_21d8ed40b50d_logs_127_txt.txt
Steps to Reproduce