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

[bug]: Unable to log in #40

Open
ixzh opened this issue Aug 11, 2024 · 10 comments
Open

[bug]: Unable to log in #40

ixzh opened this issue Aug 11, 2024 · 10 comments
Labels
bug Something isn't working duplicate This issue or pull request already exists

Comments

@ixzh
Copy link

ixzh commented Aug 11, 2024

Describe the bug

can't log in

Reproduction steps

  1. install via cargo
  2. start tgt
  3. input phone number with leading country code
  4. nothing follow suits
    ...

Expected behavior

a telegram code sent to other sessions to login

Logs and screenshots

No response

Method of Installation

Cargo

tgt version

1.0.0

Operating System (including version and architecture)

MacOS Sonoma 14.5

Terminal and Command Line Interface (CLI) (including versions)

kitty

rustc and rustup target (including versions)

1.8.1

@ixzh ixzh added the bug Something isn't working label Aug 11, 2024
@FedericoBruzzone
Copy link
Owner

FedericoBruzzone commented Aug 11, 2024

thank you for your feedback!

Try:

rm -rf ~/.tgt/.data

And let me spare what happens.

If that doesn't work you can try:

System Settings -> Privacy and Security -> '"libtdjson.1.8.29.dylib" may be blocked from use...' -> Allow Anyway

Let me know if any of these steps work :D

@Andreal2000 Andreal2000 changed the title [bug]: [bug]: Unable to log in Aug 11, 2024
@ixzh
Copy link
Author

ixzh commented Aug 12, 2024

I uninstalled already. Reinstall just now but unsuccessfully. Below the error:

Caused by:
  process didn't exit successfully: `/var/folders/2h/mwf7088d00j8b1t6sfctrbsh0000gn/T/cargo-installEuHTcT/release/build/tdlib-rs-8992cd49ea29b239/build-script-build` (exit status: 101)
  --- stdout
  cargo:rerun-if-changed=build.rs

  --- stderr
  thread 'main' panicked at /Users/void/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tdlib-rs-1.0.5/build.rs:163:40:
  called `Result::unwrap()` on an `Err` value: reqwest::Error { kind: Decode, source: TimedOut }
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
error: failed to run custom build command for `tgt v1.0.0`

Caused by:
  process didn't exit successfully: `/var/folders/2h/mwf7088d00j8b1t6sfctrbsh0000gn/T/cargo-installEuHTcT/release/build/tgt-23d1bc3283febd9c/build-script-build` (exit status: 101)
  --- stdout
  cargo:rerun-if-changed=build.rs

  --- stderr
  thread 'main' panicked at /Users/void/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tdlib-rs-1.0.5/src/build.rs:85:40:
  called `Result::unwrap()` on an `Err` value: reqwest::Error { kind: Decode, source: TimedOut }
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error: failed to compile `tgt v1.0.0`, intermediate artifacts can be found at `/var/folders/2h/mwf7088d00j8b1t6sfctrbsh0000gn/T/cargo-installEuHTcT`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.

@FedericoBruzzone
Copy link
Owner

FedericoBruzzone commented Aug 12, 2024

From this error I can infer that tgt never started right? This error is at compile time!

The error message you're encountering while trying to compile a Rust project suggests that the build process failed due to a reqwest::Error which is related to an HTTP request that timed out. This seems to be happening in the build script of the tdlib-rs crate, which is causing the entire build process to fail.

reqwest::Error { kind: Decode, source: TimedOut }: indicates that a network request made during the build process took too long and eventually timed out.

Show me the output of

export RUST_BACKTRACE=1
cargo install tgt

PS It is related to this #41

@FedericoBruzzone
Copy link
Owner

FedericoBruzzone commented Aug 13, 2024

Related also to #45 -> solved by running twice, seems to be a network problem

@FedericoBruzzone FedericoBruzzone added the duplicate This issue or pull request already exists label Aug 13, 2024
@ixzh
Copy link
Author

ixzh commented Aug 13, 2024

hey I reinstalled successfully using cargo. however Im stuck at the same step. I checked the follow place

System Settings -> Privacy and Security -> '"libtdjson.1.8.29.dylib" may be blocked from use...' -> Allow Anyway

but there is no such prompt I could allow anyway, like other 3rd party app will usually prompt if I understood correctly .

@Andreal2000
Copy link
Collaborator

Andreal2000 commented Aug 13, 2024

Hi,

Please, i suggest you to delete your last comment because you exposed your phone number.

Anyway, i think the problem is that you used as county calling code 00 and by reading this is not a valid code.

Retry by using the country code of your country, if you don't know it can be found it in the link that i send in this comment.

@ixzh
Copy link
Author

ixzh commented Aug 14, 2024

Hi,

Please, i suggest you to delete your last comment because you exposed your phone number.

Anyway, i think the problem is that you used as county calling code 00 and by reading this is not a valid code.

Retry by using the country code of your country, if you don't know it can be found it in the link that i send in this comment.

I'm from singapore, tried 65 and +65 instead of 0065, same effect no follow up action.:(

@FedericoBruzzone
Copy link
Owner

Ok, you should use +65 or 65.

Please follow the next steps:

rm -rf ~/.tgt/.data/

and restart tgt.

And then, send us the content of:

~/.tgt/.data/tdlib_rs/tdlib_rs.log

@ixzh
Copy link
Author

ixzh commented Aug 18, 2024

I find the log contains some personal info. I just wonder if it could be due to my use of VPN?

@Andreal2000
Copy link
Collaborator

The tdlib_rs.log and tgt.log.YYYY-MM-DD shouldn't contains any personal info.
Try repeat the installation and login without VPN and let us know if it work.
If the problem is not solved, send us the two logs i mention in the first phrase of this comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

3 participants