Skip to content
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

Trying to join two communities results in infinite connecting #2114

Closed
kingalg opened this issue Nov 24, 2023 · 1 comment
Closed

Trying to join two communities results in infinite connecting #2114

kingalg opened this issue Nov 24, 2023 · 1 comment
Assignees
Labels
bug Something isn't working mobile react-native

Comments

@kingalg
Copy link
Collaborator

kingalg commented Nov 24, 2023

Version: [email protected] (iOS 337)
System: android, ios

Steps to recreate:

  1. Have links to two working communities on any device
  2. With third app try to join first community but DON'T choose a username
  3. Without closing the app click on the link to join second community
  4. You will get popup with "You already belong to a community We're sorry but for now you can only be a member of a single community at a time."

**How it should work - user is joining first of the two communities that he tried to join (and this is how it's currently working on desktop (Version: 2.0.3-alpha.8). This is something that for desktop was fixed in the issue #1847 ).

How it's working - after user gets a popup from point 4 they see "Connecting to peers" view and never connect to any community.**

Logs from mobile that tried to join two communities:

--------- beginning of main
11-24 11:32:27.178 20407 20474 E NODEJS-MOBILE: 2023-11-24T10:32:27.177Z backend:Tor Nov 24 11:32:27.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
11-24 11:32:27.178 20407 20474 E NODEJS-MOBILE: Nov 24 11:32:27.000 [notice] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection
11-24 11:32:27.340 20407 20474 E NODEJS-MOBILE: 2023-11-24T10:32:27.340Z backend:Tor Nov 24 11:32:27.000 [notice] New control connection opened from 127.0.0.1.
11-24 11:32:27.361 20407 20474 E NODEJS-MOBILE: 2023-11-24T10:32:27.361Z backend:Tor Nov 24 11:32:27.000 [notice] Bootstrapped 30% (loading_status): Loading networkstatus consensus
11-24 11:32:28.630 20407 20474 E NODEJS-MOBILE: 2023-11-24T10:32:28.629Z backend:Tor Nov 24 11:32:28.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
11-24 11:32:28.694 20407 20474 E NODEJS-MOBILE: 2023-11-24T10:32:28.694Z backend:Tor Nov 24 11:32:28.000 [notice] Bootstrapped 40% (loading_keys): Loading authority key certs
11-24 11:32:29.147 20407 20458 D WEBSOCKET CONNECTION: Starting on 11000
11-24 11:32:29.214 20407 20810 D TrafficStats: tagSocket(266) with statsTag=0xffffffff, statsUid=-1
11-24 11:32:29.215 20407 20809 D TrafficStats: tagSocket(267) with statsTag=0xffffffff, statsUid=-1
11-24 11:32:29.224 20407 20474 E NODEJS-MOBILE: 2023-11-24T10:32:29.223Z backend:SocketService socket connection
11-24 11:32:29.224 20407 20474 E NODEJS-MOBILE: 2023-11-24T10:32:29.224Z backend:SocketService init: connection
11-24 11:32:29.245 20407 20448 I ReactNativeJS: websocket connected
11-24 11:32:29.698 20407 20474 E NODEJS-MOBILE: 2023-11-24T10:32:29.697Z backend:Tor Nov 24 11:32:29.000 [notice] The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services.
11-24 11:32:29.702 20407 20474 E NODEJS-MOBILE: 2023-11-24T10:32:29.701Z backend:Tor Nov 24 11:32:29.000 [notice] Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors
11-24 11:32:29.702 20407 20474 E NODEJS-MOBILE: Nov 24 11:32:29.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/7768, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)
11-24 11:32:29.822 20407 20474 E NODEJS-MOBILE: 2023-11-24T10:32:29.822Z backend:Tor Nov 24 11:32:29.000 [notice] New control connection opened from 127.0.0.1.
11-24 11:32:29.864 20407 20474 E NODEJS-MOBILE: 2023-11-24T10:32:29.864Z backend:Tor Nov 24 11:32:29.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/7768, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)
11-24 11:32:30.255 20407 20474 E NODEJS-MOBILE: 2023-11-24T10:32:30.254Z backend:Tor Nov 24 11:32:30.000 [notice] Bootstrapped 50% (loading_descriptors): Loading relay descriptors
11-24 11:32:30.922 20407 20474 E NODEJS-MOBILE: 2023-11-24T10:32:30.921Z backend:Tor Nov 24 11:32:30.000 [notice] The current consensus contains exit nodes. Tor can build exit and internal paths.
11-24 11:32:32.321 20407 20474 E NODEJS-MOBILE: 2023-11-24T10:32:32.321Z backend:Tor Nov 24 11:32:32.000 [notice] New control connection opened from 127.0.0.1.
11-24 11:32:34.558 20407 20416 W com.quietmobile: Cleared Reference was only reachable from finalizer (only reported once)
11-24 11:32:34.584 20407 20448 I ReactNativeJS: create network saga
11-24 11:32:34.591 20407 20448 I ReactNativeJS: create network saga: saving PSK
11-24 11:32:34.621 20407 20449 W unknown:ReactNative: Attempt to set local data for view with unknown tag: -1
11-24 11:32:34.621 20407 20449 W unknown:ReactNative: Attempt to set local data for view with unknown tag: -1
11-24 11:32:34.822 20407 20474 E NODEJS-MOBILE: 2023-11-24T10:32:34.821Z backend:Tor Nov 24 11:32:34.000 [notice] New control connection opened from 127.0.0.1.
11-24 11:32:36.708 20407 20449 W unknown:ReactNative: Attempt to set local data for view with unknown tag: -1
11-24 11:32:36.708 20407 20449 W unknown:ReactNative: Attempt to set local data for view with unknown tag: -1
11-24 11:32:37.334 20407 20474 E NODEJS-MOBILE: 2023-11-24T10:32:37.334Z backend:Tor Nov 24 11:32:37.000 [notice] New control connection opened from 127.0.0.1.
11-24 11:32:38.422 20407 20407 I ImeTracker: com.quietmobile:5bfb1724: onRequestShow at ORIGIN_CLIENT_SHOW_SOFT_INPUT reason SHOW_SOFT_INPUT
11-24 11:32:38.429 20407 20407 D CompatibilityChangeReporter: Compat change id reported: 163400105; UID 10279; state: ENABLED
11-24 11:32:38.429 20407 20407 D InputMethodManager: showSoftInput() view=com.facebook.react.views.textinput.ReactEditText{f414ec8 VFED..CL. .F.P..ID 45,0-931,141 #28d aid=1073741825} flags=0 reason=SHOW_SOFT_INPUT
11-24 11:32:38.438 20407 20407 I AssistStructure: Flattened final assist data: 3132 bytes, containing 1 windows, 18 views
11-24 11:32:38.490 20407 20407 D InsetsController: show(ime(), fromIme=true)
11-24 11:32:38.721 20407 20407 I ImeTracker: com.quietmobile:5bfb1724: onShown
11-24 11:32:39.828 20407 20474 E NODEJS-MOBILE: 2023-11-24T10:32:39.828Z backend:Tor Nov 24 11:32:39.000 [notice] New control connection opened from 127.0.0.1.
11-24 11:32:42.300 20407 20474 E NODEJS-MOBILE: 2023-11-24T10:32:42.299Z backend:Tor Nov 24 11:32:42.000 [notice] Bootstrapped 56% (loading_descriptors): Loading relay descriptors
11-24 11:32:42.471 20407 20474 E NODEJS-MOBILE: 2023-11-24T10:32:42.471Z backend:Tor Nov 24 11:32:42.000 [notice] New control connection opened from 127.0.0.1.
11-24 11:32:42.601 20407 20474 E NODEJS-MOBILE: 2023-11-24T10:32:42.601Z backend:Tor Nov 24 11:32:42.000 [notice] Bootstrapped 62% (loading_descriptors): Loading relay descriptors
11-24 11:32:42.896 20407 20474 E NODEJS-MOBILE: 2023-11-24T10:32:42.896Z backend:Tor Nov 24 11:32:42.000 [notice] Bootstrapped 71% (loading_descriptors): Loading relay descriptors
11-24 11:32:43.127 20407 20474 E NODEJS-MOBILE: 2023-11-24T10:32:43.127Z backend:Tor Nov 24 11:32:43.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
11-24 11:32:43.141 20407 20474 E NODEJS-MOBILE: 2023-11-24T10:32:43.141Z backend:Tor Nov 24 11:32:43.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
11-24 11:32:43.276 20407 20474 E NODEJS-MOBILE: 2023-11-24T10:32:43.276Z backend:Tor Nov 24 11:32:43.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
11-24 11:32:43.429 20407 20474 E NODEJS-MOBILE: 2023-11-24T10:32:43.429Z backend:Tor Nov 24 11:32:43.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
11-24 11:32:43.618 20407 20474 E NODEJS-MOBILE: 2023-11-24T10:32:43.617Z backend:Tor Nov 24 11:32:43.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
11-24 11:32:43.618 20407 20474 E NODEJS-MOBILE: Nov 24 11:32:43.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
11-24 11:32:43.941 20407 20474 E NODEJS-MOBILE: 2023-11-24T10:32:43.941Z backend:Tor Nov 24 11:32:43.000 [notice] Bootstrapped 100% (done): Done
11-24 11:32:44.848 20407 20474 E NODEJS-MOBILE: 2023-11-24T10:32:44.848Z backend:Tor Nov 24 11:32:44.000 [notice] New control connection opened from 127.0.0.1.
11-24 11:32:54.820 20407 20407 W WindowOnBackDispatcher: sendCancelIfRunning: isInProgress=falsecallback=ImeCallback=ImeOnBackInvokedCallback@216356058 Callback=android.window.IOnBackInvokedCallback$Stub$Proxy@92ab7ce
11-24 11:32:54.845 20407 20407 I ImeTracker: com.google.android.apps.nexuslauncher:577b85cd: onCancelled at PHASE_CLIENT_ANIMATION_CANCEL
11-24 11:32:54.845 20407 20407 I ImeTracker: com.quietmobile:c5428db8: onRequestHide at ORIGIN_CLIENT_HIDE_SOFT_INPUT reason HIDE_SOFT_INPUT_BY_INSETS_API
11-24 11:32:54.846 20407 20407 I ImeTracker: com.quietmobile:c5428db8: onFailed at PHASE_CLIENT_VIEW_SERVED
11-24 11:33:04.528 20407 20407 I ImeTracker: com.quietmobile:e3348bd0: onRequestHide at ORIGIN_CLIENT_HIDE_SOFT_INPUT reason HIDE_SOFT_INPUT
11-24 11:33:04.532 20407 21241 V SoLoader: libimagepipeline.so not found on /data/data/com.quietmobile/lib-main
11-24 11:33:04.532 20407 21241 V SoLoader: libimagepipeline.so not found on /data/data/com.quietmobile/lib-0
11-24 11:33:04.532 20407 21241 V SoLoader: libimagepipeline.so not found on /data/data/com.quietmobile/lib-1
11-24 11:33:04.532 20407 21241 V SoLoader: libimagepipeline.so not found on /data/data/com.quietmobile/lib-2
11-24 11:33:04.533 20407 21241 V SoLoader: libimagepipeline.so not found on /data/data/com.quietmobile/lib-3
11-24 11:33:04.533 20407 21241 D SoLoader: libimagepipeline.so found on /data/app/~~H1HykVbP0fcHFfVMRnsfPQ==/com.quietmobile-mEIOqVQIthTScIc9SJSpyw==/lib/arm64
11-24 11:33:04.533 20407 21241 D SoLoader: Not resolving dependencies for libimagepipeline.so
11-24 11:33:04.540 20407 20407 D InsetsController: show(ime(), fromIme=true)
11-24 11:33:04.543 20407 20407 W RemoteInputConnectionImpl: requestCursorAnchorInfo on inactive InputConnection
11-24 11:33:04.544 20407 20407 I ImeTracker: com.quietmobile:768aa279: onCancelled at PHASE_CLIENT_ANIMATION_CANCEL
11-24 11:33:04.560 20407 20407 W WindowOnBackDispatcher: sendCancelIfRunning: isInProgress=falsecallback=ImeCallback=ImeOnBackInvokedCallback@216356058 Callback=android.window.IOnBackInvokedCallback$Stub$Proxy@c33e197
11-24 11:33:04.774 20407 20407 I ImeTracker: com.quietmobile:64135cfc: onRequestHide at ORIGIN_CLIENT_HIDE_SOFT_INPUT reason HIDE_SOFT_INPUT_BY_INSETS_API
11-24 11:33:04.776 20407 20407 I ImeTracker: com.quietmobile:e3348bd0: onHidden
11-24 11:34:23.671 20407 20407 D CompatibilityChangeReporter: Compat change id reported: 150939131; UID 10279; state: ENABLED
11-24 11:34:24.653 20407 20474 E NODEJS-MOBILE: 2023-11-24T10:34:24.653Z backend:Tor Nov 24 11:34:24.000 [notice] New control connection opened from 127.0.0.1.
@kingalg kingalg added the bug Something isn't working label Nov 24, 2023
@kingalg kingalg added this to Quiet Nov 24, 2023
@kingalg kingalg moved this to Next Sprint in Quiet Nov 24, 2023
@siepra siepra moved this from Sprint to In progress in Quiet Jan 26, 2024
@siepra siepra self-assigned this Jan 26, 2024
@siepra siepra mentioned this issue Jan 26, 2024
4 tasks
@siepra siepra moved this from In progress to Waiting for review in Quiet Jan 29, 2024
@siepra siepra changed the title Trying to join two communities on mobile is causing crash of the app Trying to join two communities results in infinite connecting Jan 29, 2024
@siepra siepra moved this from Waiting for review to Merged in Quiet Jan 30, 2024
@siepra siepra moved this from Merged to (Mobile) Ready for QA in Quiet Jan 31, 2024
@kingalg
Copy link
Collaborator Author

kingalg commented Feb 7, 2024

[email protected] | iOS 350

Fixed.

It's working correctly on both Android and iOS.

@kingalg kingalg closed this as completed Feb 7, 2024
@kingalg kingalg moved this from (Mobile) Ready for QA to Done in Quiet Feb 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working mobile react-native
Projects
Archived in project
Development

No branches or pull requests

2 participants