-
Notifications
You must be signed in to change notification settings - Fork 1
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
Owner entity type person is not supported #5
Comments
Hello, @mkriegs. Thanks for making an issue! What version of the action are you using? |
Hello @Arisamiga , same result with master and 1.2.1 best regards |
Hello @mkriegs The Image gets put inside the embed of the post and the specific API I am currently using allows for external images. I am using the Share API https://learn.microsoft.com/en-us/linkedin/marketing/integrations/community-management/shares/share-api which appears to be working. 🤔 Are you trying to post blog posts on an organization account or have you turned on creator mode on your LinkedIn Profile? Can you please try to use Thank you! |
Hello @Arisamiga result with dev-2: Select "Create a new access token" and click "Create Token" Select your app and make sure you have the best regards |
Hello @mkriegs Seems like LinkedIn changed and removed the product used for the API. So the application cannot get the actual user ID. I made a commit now f6e9cd6 which should fix it. Can you please try to use the master branch and see if it works? Make sure to use "profile and openid as well as w_member_social" scopes Thanks! |
Hey @Arisamiga didnt change anythink, changed back to @master { |
Hello @mkriegs Sorry for that. The release did not build as expected. Can you please try to run the action again? Make sure to also have the scopes " Thanks :D |
Hey, @Arisamiga it worked out! post is on linkedin! best regards |
Hey @Arisamiga if i do cron each 1 hour i get all the time this error. Who to resolv this ? body: '{"errorDetailType":"com.linkedin.common.error.BadRequest","message":"com.linkedin.content.common.exception.BadRequestResponseException: Content is a duplicate of urn:li:share:7141138937766391808","errorDetails":{"inputErrors":[{"description":"Duplicate post is detected","input":{},"code":"DUPLICATE_POST"}]},"status":422}' best regards Michael :) |
Hello @mkriegs
I would suggest Forking the Repository and adding fields that you want so you can personalize it for your own RSS thread!
This happens because you have uploaded the same post before. I am thinking of ways to mitigate this and adding a file might be a good way. I will create a issue with this idea! Also let me know If you want me to close this issue sense it has been resolved. Thank you. |
I will be closing this issue as it has been resolved. If you have any further problems don't hesitate to reopen it. |
Hey @Arisamiga , sorry didnt find time to respond to you. thanks for the help and bug release, aswell as new feature. best regards |
Hey, can you help here ?
Linkedin-RSS/index.js
Line 46 in f7f98d9
Looks like it should be like this: "author": "urn:li:person:8675309"
https://learn.microsoft.com/de-de/linkedin/consumer/integrations/self-serve/share-on-linkedin#creating-a-share-on-linkedin
best regards Michael
{
status: 400,
headers: {
'x-li-responseorigin': 'RGW',
'content-type': 'application/json',
'x-restli-error-response': 'true',
'x-restli-gateway-error': 'false',
'x-restli-protocol-version': '2.0.0',
'content-length': '68',
date: 'Sun, 10 Dec 2023 12:26:57 GMT',
'x-li-fabric': 'prod-ltx1',
'x-li-source-fabric': 'prod-lva1',
'x-li-pop': 'prod-lva1-x',
'x-li-proto': 'http/1.1',
'x-li-uuid': 'AAYMJu7uDegAHiAVXD7aaQ==',
'set-cookie': [
'bcookie=""; domain=.linkedin.com; Path=/; Secure; Expires=Mon, 09-Dec-2024 12:26:57 GMT; SameSite=None',
'lidc="b=TB32:s=T:r=T:a=T:p=T:g=4690:u=1061:x=1:i=1702211217:t=1702286985:v=2:sig="'
],
'x-li-route-key': '"b=TB32:s=T:r=T:a=T:p=T:g=4690:u=1061:x=1:i=1702211217:t=1702286985:v=2:sig="'
},
body: '{"message":"Owner entity type person is not supported","status":400}'
}
Error: Failed to post on LinkedIn
The text was updated successfully, but these errors were encountered: