Skip to content
This repository was archived by the owner on Aug 9, 2021. It is now read-only.

Error: There is already a transport with this key #110

Closed
joaoaguiam opened this issue Oct 11, 2018 · 7 comments
Closed

Error: There is already a transport with this key #110

joaoaguiam opened this issue Oct 11, 2018 · 7 comments
Assignees
@oed
Labels
bug Something isn't working

Comments

@joaoaguiam
Copy link
Contributor

Describe the bug
When opening the box the following error occurs: "Error: There is already a transport with this key"

To Reproduce

  1. Deploy version 1.0.0-beta-8
  2. Open box

Screenshots
screen shot 2018-10-10 at 19 06 34

Desktop (please complete the following information):

  • OS: Mac
  • Browser Chrome
@oed
Copy link
Contributor

oed commented Oct 11, 2018

Ty, I'll try to reproduce this today!

@joaoaguiam
Copy link
Contributor Author

Hi @oed , I tried to rollback to the version 1.0.0-beta-7 and the platform runs correctly. Error is only happening on version beta-8 and beta-9.

@oed oed self-assigned this Oct 18, 2018
@oed oed added this to the Sprint 7 milestone Oct 18, 2018
@oed oed added the bug Something isn't working label Oct 18, 2018
@oed
Copy link
Contributor

oed commented Oct 18, 2018

This error has also been reported separately on our discord.

@michaelsena michaelsena changed the title Error: There is already a transport with this key on version 1.0.0-beta-8 Error: There is already a transport with this key on version 1.0.0-beta-10 Oct 18, 2018
@oed oed changed the title Error: There is already a transport with this key on version 1.0.0-beta-10 Error: There is already a transport with this key Oct 19, 2018
@oed
Copy link
Contributor

oed commented Oct 19, 2018 •
edited
Loading

This error is coming from ipfs, libp2p in particular. Still haven't been able to figure out why it happens, but it seems like it's only happening for some people when building their react projects. The dist builds provided by 3box-js are not affected by this. So while we try to figure out a solution for this problem you can use this workaround:

copy the 3box dist file to your public folder:

$ cp node_modules/3box/dist/3box.min.js public/

edit your public/index.html file, add the following inside of the <head></head> tags:

<script src="./3box.js" type="text/javascript"></script>

Now the ThreeBox object should be globally available in your project.

Depending on your config you might need to add the following in the js files that use the ThreeBox object:

/*global ThreeBox*/

@michaelsena michaelsena modified the milestones: Sprint 7, Sprint 8 Nov 13, 2018
@oed
Copy link
Contributor

oed commented Nov 27, 2018

This error seems to be an issue with react-scripts not supporting ES6 (which ipfs uses). See this comment for how to address it: #134 (comment)

@oed oed removed this from the Sprint 8 milestone Nov 27, 2018
@oed oed mentioned this issue Jan 21, 2019
Closed
@oed
Copy link
Contributor

oed commented Jan 21, 2019

@joaoaguiam when you get around to, can you try out this solution and see if it works: 3box/3box-dapp#238 (comment)

@oed
Copy link
Contributor

oed commented May 13, 2020

I believe this error is no longer around. Please repopen if you see it surfacing again :)

@oed oed closed this as completed May 13, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@oed oed

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@oed @michaelsena @joaoaguiam