Picolab / Manifold-production-instance

Tracking issues with our production instance of Manifold
0 stars 0 forks source link

A cloud agent connection causes the screen to go blank #11

Closed b1conrad closed 4 months ago

b1conrad commented 3 years ago

Matthew Hailstone created a connection between a thing (with the manifold_cloud_agent app installed) and his Evernym connect.me wallet. Not sure how far along the connection got, but now the screen goes blank when he opens up that agent.

To do: have him show the exact symptoms.

b1conrad commented 3 years ago

When he visits this page (while logged in as himself), "Just keeps spinning and doesn’t come up."

To do: watch over his shoulder as this happens and have him try a few things.

b1conrad commented 3 years ago

The only thing suspicious on the pico side is that the crippled connection doesn't have a key their_endpoint which could produce a run-time error in the browser, since JavaScript... Never mind, it should just be undefined but perhaps that causes a problem downstream.

This would happen here and here.

The field, renamed endPoint and then (surprisingly) invitation is used as part of the id for the input field to send a basicmessage. I don't know what would happen when it is undefined. Let's simulate this...

Looks like you would see this error message in the browser console, "Uncaught TypeError: Cannot read property 'concat' of undefined" and then the page would never finish loading.

b1conrad commented 3 years ago

For Matthew's case, removed the crippled agent from his pico's list of connections by sending a well-crafted /sky/event/ to it. That solves his immediate problem.

We still need to make the page more robust.

b1conrad commented 3 years ago

The issue has been resolved, for this owner, for this case. Issues have been raised in two other repositories to improve robustness.

b1conrad commented 4 months ago

We will do nothing further with this issue here. When moving to the v1 pico engine (issue #9) we will not use the Manifold Cloud Agent app, because we will only support DIDComm v2 going forward.