-
Notifications
You must be signed in to change notification settings - Fork 229
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
Support new Telegram version for android #2184
Comments
Another Telegram DB schema change, here we go... |
One user sent the db and of course it wasn't being decoded because of a new version. I just update the decode and the database can be parsed. if you have time please check sepinf-inc/telegram-decoder#3. I didn't remember well where I have to change in the iped project to get the new plugin version. |
Thanks @hauck-jvsh! I'll run a regression test on old DBs to check if it is fine. I would also appreciate if you can send the new DB to me for inclusion into the regression data set. |
Hi @hauck-jvsh. The build for the new telegram plugin version 1.0.11 is failing:
Seems some classes are missing... Could you take a look? |
Just reverted your merged PR on telegram-decoder project main branch until the build is fixed. |
Strangely it was building in my project, but when I make a clean build it stops. I fix it now, I think that now it is correct. |
Thanks @hauck-jvsh. I had a hard time struggling with jitpack.io and the telegram-decoder project pom.xml files, seems ok now, I just started the regression test, should have results later today or tomorrow. |
Comparison to 4.1.6 is fine, no exceptions, more chats, many more messages and more search hits for common words. But I should have compared to master, it was already decoding more info than 4.1.6. Just started the processing of all 108 android DBs with master and I should have results tomorrow. |
Results look fine on the 108 sample android DBs comparing to master: no exceptions, same number of chats and messages, but we got more contacts and more search hits for common words as expected, since senders and message bodies from the new Telegram version were being returned as unknown. |
Telegram may have changed the database scheme as two users reported that the database is present but is not being decoded by IPED.
The text was updated successfully, but these errors were encountered: