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

Published URIs with Channel getting incorrect claim_id #460

Closed
tzarebczan opened this Issue Aug 9, 2017 · 0 comments

Comments

Projects
None yet
3 participants
@tzarebczan
Member

tzarebczan commented Aug 9, 2017

The Issue

This issue originally stemmed from here: lbryio/lbryum#143
After Publishing a file with an identity, the user is presented a link in their Publishes area. This link has the incorrect channel id in this format:
lbry://@jiggytom#6e477eded9468613c9c5b45eb58662ea302bccea/index

The channel is actually lbry://@jiggytom#e48d2b50501159034f68d53321f67b8aa5b1d771 and the index claim is lbry://index#6e477eded9468613c9c5b45eb58662ea302bccea

There is a bug in lbryum that allows it to resolve correctly, but a get fails. Wasn't sure what the root cause is, so opening an app issue on top of the lbryum one. The get returns a failure to resolve error.

Steps to reproduce

  1. Publish content under an identity, let it confirm
  2. Observe URI on the Publishes screen
  3. Notice that it's showing the claim id and not the channel id in the URI

Expected behaviour

Should show the channel id in the URI

Actual behaviour

Shows claim id in the URI

System Configuration

  • LBRY Daemon version: 0.14.2
  • LBRY App version: 0.14.3
  • LBRY Installation ID:
  • Operating system: Win 10

Anything Else

Screenshots

@kauffj kauffj added the P1 label Aug 10, 2017

@btzr-io btzr-io referenced this issue Aug 26, 2017

Closed

Improve editing UX #500

4 of 8 tasks complete

@kauffj kauffj closed this in 90c83c6 Aug 28, 2017

kauffj added a commit that referenced this issue Aug 28, 2017

kauffj added a commit that referenced this issue Aug 28, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment