We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Logs keep showing the following message:
Starting from version 22 and above, the impressions metric is no longer supported for the queried user. Please refer to the documentation at https://developers.facebook.com/docs/instagram-api/reference/ig-user/insights for a list of supported metrics.","type":"OAuthException","code":100,"fbtrace_id":
open postiz app, go to the analytics tab then look at the log.
that all metrics should be present and accounted for.
shows
Linux
whatever came in the docker container
No response
None
The text was updated successfully, but these errors were encountered:
No branches or pull requests
📜 Description
Logs keep showing the following message:
Starting from version 22 and above, the impressions metric is no longer supported for the queried user. Please refer to the documentation at https://developers.facebook.com/docs/instagram-api/reference/ig-user/insights for a list of supported metrics.","type":"OAuthException","code":100,"fbtrace_id":
👟 Reproduction steps
open postiz app, go to the analytics tab then look at the log.
👍 Expected behavior
that all metrics should be present and accounted for.
👎 Actual Behavior with Screenshots
shows
Starting from version 22 and above, the impressions metric is no longer supported for the queried user. Please refer to the documentation at https://developers.facebook.com/docs/instagram-api/reference/ig-user/insights for a list of supported metrics.","type":"OAuthException","code":100,"fbtrace_id":
💻 Operating system
Linux
🤖 Node Version
whatever came in the docker container
📃 Provide any additional context for the Bug.
No response
👀 Have you spent some time to check if this bug has been raised before?
Are you willing to submit PR?
None
The text was updated successfully, but these errors were encountered: