Massive number of warning messages and stuck at 50%

[kjrose]

So I'm trying to implement this within a xcode project as a cocoapod.

Everytime I attempt to activate it I get

"[warn] Relay's onion key had invalid exponent" about 300 times and then it suddenly stops.

And I reach "50 Loading relay descriptors" and no further. I'm trying to figure out what could be going wrong, because I'm using the straight CocoaPod with the torrc within it.

I'm doing further testing to see if I can narrow down what the issue is.

[kjrose]

Within the Relay onion key issues I have another odd message

"I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 1/7235, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of exit bw = 0% of path bw.)

I'm wondering if this is because the geoip is out of date perchance?

[kjrose]

It eventually fails with Tor Setup did timeout.

[kjrose]

Ok, I found the problem.

The versions of Tor and openSSL in the cocoapod are out of date.

How can I submit the newversions so you are updated?

[chrisballinger]

Hey thanks for taking a look. I'll update the build scripts shortly

[serjooo]

Hello,

I'm experiencing similar issues on ios version 10.3.1 I tested on everything greater im able to connect to tor successfully. Any tips on fixing this issue for a specific ios version?

Also, didn't get the chance to test on ios version < 10.3.1 so not sure if it works on those versions; however, pretty sure it doesn't work on ios 10.3.1.

[rainwolf]

I'm using it on iOS 10.2 and it works flawlessly for me.

[serjooo]

@rainwolf I see.. Could ios version specific problems arise? Because as I said I tried on everything great than 10.3.1 and it works perfect. I'm wondering if the problem could be from the device itself.

Anyways I'm downloading the 10.3.1 simulator right now, to see if it might be from the device and not an os version specific problem, since I only have one device to test for 10.3.1.

[serjooo]

Update: I tested on the simulator for O.S 10.3.1 it worked as well. I'm guessing its because the device I am testing on.. Not sure what is wrong.. This is what I'm getting.

I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
Nov 26 12:42:22.000 [notice] Bootstrapped 40%: Loading authority key certs
2017-11-26 12:42:22.141729+0200 DownloadManager[206:3553] 40 Loading authority key certs
Nov 26 12:42:23.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus.
Nov 26 12:44:57.000 [warn] Received a bad CERTS cell: At least one certificate expired.
Nov 26 12:44:57.000 [warn] Problem bootstrapping. Stuck at 40%: Loading authority key certs. (DONE; DONE; count 11; recommendation warn; host 74A910646BCEEFBCD2E874FC1DC997430F968145 at 199.58.81.140:443)
Nov 26 12:44:57.000 [warn] 11 connections have failed:
Nov 26 12:44:57.000 [warn]  10 connections died in state handshaking (Tor, v3 handshake) with SSL state SSL negotiation finished successfully in OPEN
Nov 26 12:44:57.000 [warn]  1 connections died in state connect()ing with SSL state (No SSL object)
2017-11-26 12:44:57.742628+0200 DownloadManager[206:3553] 40 Loading authority key certs
Nov 26 12:45:29.000 [warn] Problem bootstrapping. Stuck at 40%: Loading authority key certs. (DONE; DONE; count 12; recommendation warn; host 92CFD9565B24646CAC2D172D3DB503D69E777B8A at 178.16.208.57:443)
Nov 26 12:45:29.000 [warn] 12 connections have failed:
Nov 26 12:45:29.000 [warn]  11 connections died in state handshaking (Tor, v3 handshake) with SSL state SSL negotiation finished successfully in OPEN
Nov 26 12:45:29.000 [warn]  1 connections died in state connect()ing with SSL state (No SSL object)

[serjooo]

Update: Turned out that the device's date was changed, and that was the reason why it wasn't able to build the circuit or get certs.