KeyError: 'eplus' / part of config file name: config.eplus #2664
Comments
|
it's a bug, i think if you remove the file extension "eplus" or change it to .json (if your config is in json format) it would fix it. |
|
Ok, removed the extention, and getting the next error (this config file was working for at least 2 years): Traceback (most recent call last): Same error when using the following config file for new registration: Traceback (most recent call last): Thanks for your work and support |
|
'id' is supposed to be b64 encoded string. I suggest you delete 'id' and 'password' (password is not used any more) from your config file and try again |
|
Thank you. Registration works. Now I got some Infos in json notation. What are the next step. Please excuse, but where can I find such infos. Greetings Jörg |
|
Next step is to just login. yowsup already automatically stored this information and will use it when the same phone number is supplied. If interested, on linux you can find this auto persisted config at I still need to add some documentation to describe this. |
|
A good feature. But now I am falling into the issue: Traceback (most recent call last): Starting the Demos with: python yowsup-cli demos --config-phone 49xxxxxxxxx --config-cc 49 -y will open the client. The command /L is bringing up the error. |
|
Ok, tryied the following: Then the next Problem raises: |
refs #2664 On python2 a long phone will have type 'long' instead of 'int' which will cause an error during construction of phone storage dir
Previously configs with no extension were treated as keyval, will now attempt detect config type if file has no extension through trial parses. Fixed error when a config file has an extension, but is neither .json nor .yo refs #2664
|
I've updated master with fixes to issues mentioned here, can you please try and confirm if it worked? Thanks for posting the error outputs! |
|
The three fix are working. But evrey time there is a "but" When sending a message from the command line the first time, the following error is reportet: python yowsup-cli demos --config-phone 49163xxxxxx --config-cc 49 -s 49162xxxxxxx "Dies ist ein Test" I 2019-04-23 23:32:17,232 yowsup.layers.network.layer - Connecting to e2.whatsapp.net:443 Tryiong it again will give the following error: Exception in thread YowPingThread-3: In both cases the message is send. Starting the command line client Messages are send without error. |
|
Thanks for the update. I think the "send message and exit" demo is partially broken; it does successfully send the message but fails to properly shutdown. The "echo" demo also should work fine but will not cleanly exit when requested. I'll work later on updating those demos. The command line client should work fine as you described though. |
|
Hi! It seems I have this same issue. I've just registered and when I execute:
and
Appears this exception and message doesn't sent: Could you help me? |
|
@felipefreitas that's not the same issue, |
|
fixed in v3.1.0 |
|
Again this issue since 29. April 2019 round 8 PM [https://github.com//issues/2702] |
|
@HeinzFo read my last comment and look at your yowsup version |
|
@tgalal Yes shure I have installed v3.1.0 yesterday but the issues is pressent. Regrads |
|
obviously what you are describing has absolutely nothing to do with this issue title "KeyError: 'eplus' / part of config file name: config.eplus " |
and others
My next issue:
Traceback (most recent call last):
File "yowsup-cli", line 518, in
if not parser.process():
File "yowsup-cli", line 416, in process
super(DemosArgParser, self).process()
File "yowsup-cli", line 193, in process
self._config = self._config_manager.load_path(self.args["config"])
File "/opt/fhem/yowsup-master/yowsup/config/manager.py", line 78, in load_path
configtype = self.guess_type(path)
File "/opt/fhem/yowsup-master/yowsup/config/manager.py", line 103, in guess_type
return self.MAP_EXT[ext]
KeyError: 'eplus'
eplus is part of the config file Name: config.eplus
The text was updated successfully, but these errors were encountered: