-
Notifications
You must be signed in to change notification settings - Fork 6
launch stalls with 'Valid api_|id must be provided #19
Comments
im sorry to hear that to clearify, i half abandoned this project and i barely work on it the app_id is already pre-packaged into the client https://github.com/TruncatedDinosour/arigram/blob/main/arigram/config.py#L25..L26 so im very confused why such error would happen, maybe you overwrote it somehow, maybe even in config.py ? maybe some other arigram users know, but i even now currently have arigram open and its fine, |
I have this error. Changed |
thats odd, weirdly still works for me and i doubt its anything with the api as i try to keep up with the changes, if it was gonna happen itd happen to me too |
maybe the AUR package is broken or something ? i dont maintain it though |
I installed from sources. My OS:
|
maybe this fixes it ? i bumped the python tg version |
I'll try in a moment. Will notify |
just in case, ill leave the house for now as i got plans with my best friend, ill be back in a couple of hours, sorry for the delay in responses in advance, id give 24/7 support if i could, but im just a teenage developer, not a large tech company <33 |
dude, relax, you don't owe me or anybody else anything. |
tried creating fresh user on system - same |
wait, I didn't try purging cache. will be back in a sec |
well, apparently I don't have cache for arigram |
i guess its because you havent even been able to log in |
I will try installing arigram on virtual machine. Hope it'll work |
its still very suspicious that it even breaks on 2 systems |
ill try it on a fresh void linux vm too |
@ truncatedDinosaur |
yeah, i know, its probably not related to that, the problem in it is that i am unable to reproduce it no matter what, im unsure whats so broken that makes your arigram install scream |
installed on fresh Ubuntu 22.04. Had an issue with libssl.so.1.1 |
but now |
hm, but now why is it broken for you two |
@bogdan: |
so, any update ? |
hey, got the same issue after a fresh arch install. |
hihi, we still dont know what the cause is, if you figure it out, please tell us <3 |
On arch I see there are two lib32-openssl packages: perhaps that is the cause of the problem $ pacman -Ss openssl
These provide the lib.ssl.so file. |
i use openssl version 1.1.1, gentoos latest |
interestingly enough it works on EndevourOS just fine. No |
yeah, its unreproducable on my gentoo, nor on a void vm, nothing, idk whats up, no clue what to fix |
Form what's been reported so far I think we can conclude the key is valid and it should be read with OK with required dependencies. Therefore, It seems like it could be down to the aur package. It is actively maintained and Imyself coul dnot see any obvious problems there, when taking a breif look: Here are the details; [aur arigram.git](https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=arigram :)
It's pulling arigram version 0.1.6.1 $ pacman -Qi arigram
I've just now posted this issue to the package maintainer for his comments on this problem experienced by only arch users. |
im guessing the issue is solved so ill close it, thank you for active convo when needed |
Not solved, yet. I have the problem both from built version and from AUR. What's even weirder is that I didn't have the problem from the start. It ran "fine", the only serious error being that I couldn't type. I solved it (in controllers.py at the line 582 changed the permission Even though in my case it may seem as an user error, I highly doubt it. |
sorry, ion rlly work on this anymore, the current state of this project is 'if it works for me its good enough for everyone' and what id suggest is forking this, i am sorry for the accumulating errors and functionality loss over time, ill reopen this just in case the community wants to solve this or yall wanna advertise any forks |
Yes, I understand. I'll try to fix it, and if I succeed I'll let you know. |
I found the error, and it was a user one. I was using
I bet that was caused by the fact that I had two python-telegram packages installed, one from AUR with the latest version and one from pip. |
hey, as this issue is still open i'd like to make it clear that this project has had its final release and i encourage to go find or start other arigram forks https://github.com/TruncatedDinoSour/arigram/releases/tag/v0.1.8 |
Ho, looks really good, but this error occurs, implyiing app_id authentication.
raise RuntimeError(f'Telegram error: {self.error_info}') RuntimeError: Telegram error: {'@type': 'error', 'code': 400, 'message': 'Valid api_id must be provided. Can be obtained at https://my.telegram.org', '@extra': {'request_id': 'updateAuthorizationState'}}
Arigram was installed from aur community package , V. 0.1.6-1
I dont have an app_id myself , although i have a telegram account of course. I had expected the ap_id would be registered somehwhere in the installe d package.
My telephone number, as entered on the command after arigram, has been recorded in the arigram/config.py
Any help, appreciated.
John
The text was updated successfully, but these errors were encountered: