I have the same unverified status for linkedin everything else A ok.
#metoo
Same problem as these other users. Please let me know how to resolve this issue. Thanks.
Same here for both LinkedIn & Twitter account. More detailed info for verification will help.
Also since it is public post, it affects someone who wants to do research.
Solution and correct way to verify is: in your linkedin post click on “Copy link to the post” and paste that link in verification section. It will work.
Tip: Don not past this link "https://explorer.blockstack.org/address/xxxxxx"
Correct way, It will look like “https://www.linkedin.com/feed/update/urn:li:activity:xxxxxxxxx”
Same for other verification through twitter, github.
I have been having the same problem with my eminsblock.id as well, tried twice and followed all instructions making the post public but never got verified
@jackzampolin here are the details, just tried again today:
ID: 1J52d8QdYWKxi5djaSisxmjGKcSqteBauD (eminsblock.id)
LI Link: https://www.linkedin.com/feed/update/urn:li:activity:6366908885017649152
Clicked Verify, did hard refresh, nothing worked
hi
also the same problem is for me:
https://www.linkedin.com/feed/update/urn:li:activity:6372170448414871552
I cannot verify my linkedin profile
Hi @R_I_Porter,
Thanks for reporting! There has been an issue with LinkedIn’s verification that is still open. Our developers will have to take a look and provide a fix, potentially in the next release. CC @yukan
I’m sorry for the inconvenience. If you’d like to remove your LinkedIn profile for the time being, you can click on “Edit” in your Blockstack profile, then click on the little edit pencil next to the LinkedIn logo, remove your information, and save.
It does not work for me, I already removed and reentered information. The post is definitely public at:
https://www.linkedin.com/feed/update/urn:li:activity:6552156226044608512.
My address is 1NHP69DEeuSh23XAUzLquKLXY6AFVKL5Rm
Can you give me some hint?
Linkedin verification is broken, looking at the Github it should be fixed in newer versions of blockstack.js, although some have considered removing it entirely, but is should be fixed when the blockstack browser updated it’s blockstack.js version.