Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ProcessorTransactionsSyncResponse Data Verification Error #539

Open
ovedaydin opened this issue Dec 13, 2024 · 8 comments
Open

ProcessorTransactionsSyncResponse Data Verification Error #539

ovedaydin opened this issue Dec 13, 2024 · 8 comments

Comments

@ovedaydin
Copy link

Sandbox Api returns modified as null but it's expecting an array.

@phoenixy1
Copy link
Contributor

Well dang, it's definitely not supposed to do that. Thank you for the report. I've reached out to the Transactions team to let them know and will respond here once there's a further update.

@ovedaydin
Copy link
Author

Well dang, it's definitely not supposed to do that. Thank you for the report. I've reached out to the Transactions team to let them know and will respond here once there's a further update.

Thank you.

@phoenixy1
Copy link
Contributor

We plan to update the API behavior on the week of January 6th. (We are delaying the fix so that we can notify customers using this endpoint and give them a chance to confirm that this will not disrupt their integrations.)

@ovedaydin
Copy link
Author

ovedaydin commented Jan 17, 2025

We plan to update the API behavior on the week of January 6th. (We are delaying the fix so that we can notify customers using this endpoint and give them a chance to confirm that this will not disrupt their integrations.)

Thank you!

@phoenixy1 is there any new update about this?

@phoenixy1
Copy link
Contributor

Yes, @ovedaydin the fix should be deployed as of yesterday (we delayed it a little past the 6th because some customers were difficult to contact over the holidays). Please let us know if you're still having issues.

@ovedaydin
Copy link
Author

@phoenixy1 It seems like there are more issues here.

{'account': {'account_id': '', 'balances': {'available': None, 'current': None, 'iso_currency_code': None, 'limit': None, 'unofficial_currency_code': None}, 'mask': None, 'name': None, 'official_name': None, 'subtype': None, 'type': None}, 'added': [], 'has_more': True, 'modified': [], 'next_cursor': 'CAESJUdXUVE3WFBrTXdDN21wUnBCTDNqSUd3ZHpXa2Q2cnRHbDNvemwiDAi++L68BhCY1emjASoMCMD4vrwGEOD1sJEC', 'removed': [], 'request_id': 'tDRt2lXWhjBBwag', 'transactions_update_status': 'HISTORICAL_UPDATE_COMPLETE'}

account name can't be None
account type can't be None

@phoenixy1 phoenixy1 reopened this Jan 21, 2025
@phoenixy1
Copy link
Contributor

@ovedaydin can you share more detail about the request you're sending to get that result? I wouldn't expect it to be possible for those fields to be empty.

@ovedaydin
Copy link
Author

I believe it tries to return some data even if it's not ready. When you wait a little bit then you get the actual data. @phoenixy1
this is the code piece I use today, try catch is used to bypass type errors for now.

            data = {"count": 500, "processor_token": processor_token}
            if cursor:
                data["cursor"] = cursor
            request = ProcessorTransactionsSyncRequest(**data)
            # if it fails due to data type then use last response
            try:
                response = client.processor_transactions_sync(request)
            except Exception:
                response = client.api_client.last_response.data
                response = json.loads(response)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants