guardianproject/orbot

[BUG]The user bridge connection button does not work again

Opened this issue · 2 comments

Describe the Bug
Reconnecting user bridges cannot be done.

To Reproduce
Steps to reproduce tthe essence of the problem is that you can only connect user bridges once.

  1. Insert custom bridges
  2. Click the connect button
  3. Turn off the connection to the tor
  4. Try to connect user bridges again

Expected Behavior
connecting bridges

What Custom Configuration Do You Use?
the only thing I have configured is for the rethink dns application to work.
Screenshots
IMG_20241108_101719.jpg

Smartphone (please complete the following information):

  • Device: redmi note 11s
  • OS: android 13
  • Version: 17.3.2-RC-1-tor-0.4.8.12

Crash Logs (Advanced)
If applicable, add crash logs collected using ADB Logcat.

Additional Context
deleting orbot application data helps. I take the bridges from the script to scan the available bridges.
example of which bridges I wanted to insert:

54.38.72.170:9001 7704D4990E35685E9261E330F652DEB15C2F09C3
50.120.70.214:9001 5DCEA4D2328201B0076283F266202468B1228F54
185.241.208.245:9000 C3F9572611FF1084615219D8CE3AE6848C1DCCAD
146.0.36.21:9003 32361A1EFDF684DAEDC8CA64843767A395F9EACE
163.172.45.4:3302 2ABE8A09D3403BE5CF896F77EABE23762002A761
192.42.116.200:9001 EDE1772DF32C93FBAF0B87244AC272F442CDCAF7
172.93.102.139:443 C28363EA6BA475D5E0A5EFB35BA8CA2A38A9ECE4
79.50.209.168:10101 02654B8B9803775860CDF2C7F7109FF68A1349AA
139.99.238.17:8443 84899424AEEB06870BBCD89873BD2824FACB5230
192.129.10.18:443 828DF913997A261E05F894F11CD39573356B368E
208.115.216.54:9002 806E6AB6E4BCFFA3A37F837DE94AFF6EB18CE94A
37.60.243.121:9001 A7AF201417412264D533B70EA3B2D974529FA81A
152.53.52.245:443 03A3FD57D603CD943128115E5AEBE20A4EEA984C
140.238.168.214:443 9EA65D1BB607ADA4B9A6B2A58BAA2C960DF8BDEA
185.148.1.239:9001 BC951FE44A7CB2BD40EEBBDDC5D341B30E16F5FD
185.40.4.101:8443 7A6C085A12D90C56C17A9D1A77D9D1D9B9E592D4
95.217.156.221:443 7451225CBA6B689530738AF26E5B9CA2B051827E
45.125.65.45:443 EC16F2B1D13F65836FD2B7856995828D18F32CC0
185.220.101.110:993 D13692D97236C0B8E8E19EA2DD952B5C4F9010BB
140.78.100.41:8443 C9525872E3AA926402D8998085A409C7BBDFAE59
95.99.2.91:9050 AA80B523EB781CF470CA5A91427200620FFD4281
154.216.17.140:443 D697314CFA4487E3CF5BAE45EBF9A9D8E68333DD
185.220.101.63:10063 A8A74BD885162B23FBA5DB62FBF1D6919C61AB56
91.134.90.21:444 7D7DBA4E3AFEC29D95690E0E540E084BB67B9645
95.214.52.187:9001 298EC3331E104E9E84313B10B2DF0746594EED47
23.154.177.6:443 114D0851404015C0265F1F4D4BA6A5E1E970E15E
154.22.59.44:9000 AFED437530185B2722A5B83D9CD3CDAE2A82B5F8
185.220.101.206:443 EB9DD80E64DD829A5F7C7ACA5D5FEADFEBFDD847
45.148.10.111:9400 52B3778785C2D7DAD7086F6D8BB2178354A70D1F
45.142.176.32:9001 414000EFBAD6EBC143E843BF2B651C9656578A44

by resetting the application data. the 1st time gives the opportunity and connects successfully, and the second time the connect button no longer works, even if there are other bridges. why do I have to use custom bridges, because snowflake seems to be already blocked by Roskomnadzor.

Happened to me today.

Orbot-17.2.1-RC-2-tor-0.4.8.7-fullperm-arm64-v8a-release
and
Orbot-17.3.2-RC-1-tor-0.4.8.12-fullperm-universal-release.apk