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
AdUser.get_ad_account doesn't flow api instance to AdAccount #66
Comments
This seems to be more general than the specific case I have above. It seems like any call that creates an object does not flow the api instance. I am using version 2.3.3 of this library. |
Hey @dylanlingelbach, we don't flow the api object in the manner you're describing (but that might be a good PR). The flow you're using would require the following call after you instantiate the
Alternatively, you can skip creating the session and creating the
|
@ebzlo Then why does the readme documentation say that using multiple access tokens is supported and the only area where you have to again pass the api instance is with class methods?
|
I vote that the API should flow to all fetched objects! How would I set the api on the fetched objects afterwards as it is now? I can't use set_default_api as I have many users at the same time. |
@JDaance: you can use our forked version: https://github.com/Evzdrop/facebook-python-ads-sdk We try to keep it up to date and have a few other changes there but should get you pointed in the right direction. Hope this helps! |
@rituparnamukherjee - was this fixed or no longer an issue in later versions of the SDK? Or are you saying you aren't going to fix this? |
Apologies for confusion. We have updated quite a bit on the SDK. Would you mind sending out a PR for this off of the latest SDK version. |
@rituparnamukherjee - ok, our solution is not ready for a PR, it is a pretty quick hack. Can we leave this open until you fix or we open a PR? |
When I create an
AdUser
with a specific api instance and then callget_ad_account
on that instance the api instance does not flow to the createdAdAccount
.Here is a test case that reproduces this issue:
The text was updated successfully, but these errors were encountered: