search

lightningrodlabs / we-tauri

Creating a group coherence with holochain apps
https://lightningrodlabs.org/we
Other
43 stars 4 forks source link

Spinning wheel of doom when creating new group #16

Closed Kasimirsuterwinter closed 2 years ago

Kasimirsuterwinter commented 2 years ago

OS: Windows Launcher Version: 0.7.1 Holochain Version: 0.0.169 We version: 0.0.7

After adding an avatar and name for a new group and clicking "ok" it just spins and spins and nothing happens.

The same thing happens for me with Holochain version 0.0.165. However with HC 0.0.162 it works right away.

matthme commented 2 years ago

Okay, that seems expected. The current version of We only works with Holochain 0.0.162 because later versions introduced changes that it is not compatible with. With the next Launcher release it should choose the right version of Holochain automatically again when an app is being installed from the App Library (that feature slipped through the cracks when upgrading the User Interface of the Launcher) so this hopefully shouldn't happen again.

Kasimirsuterwinter commented 2 years ago

Thanks for the quick reply! That's great to hear :)

I am still having some trouble inviting another member to my group. I assume they need to be on the same version of HC and We (which they are) but when I add them with their public key and send an invite, they don't get anything... does it just take a while to gossip?

matthme commented 2 years ago

Is this with We version 0.0.7? I specifically intended to fix that because it was not working properly in version 0.0.6. Requirements are that both are in We version 0.0.7 and Holochain version 0.0.162. Also sometimes the DNA hash differs when the app is installed from the App Library vs. installed from the filesystem after downloading it from github. To make sure you are both in the same network, compare the DNA hashes that you see in "App Details" (by clicking on the 3 horizontal dots). You should have the same set of DNA hashes.

matthme commented 2 years ago

FYI we found yet another bug that caused problems with invitations and has now been fixed with v0.0.8. I'll probably close this issue in a few days if no more problems with invitations occur.