Closed firefish475 closed 5 months ago
I open this bug report because I could not send email to cmeng.gm@gmail.com for some unknown reason. My mail isp just gives me the error could not send mail.
Just realise that aTalk built during system debug, and the built for playstore official release has completely two different behaviour. aTalk release version has problem, has lead to user unable to login. Problem under investigation.
Issue raised to AS team for solution: https://issuetracker.google.com/issues/321988935
Just release aTalk 3.3.2, please try out and see if this has fixed the problem. Note: JingleFile send still facing problem. awaiting AS team feedback.
Version 3.3.2 logs in ok on my devices.
Thanks for your update.
File sending indeed fails. sth like "must not be null and must exist"
The JingleFile sent is working correctly without problem in system testing via Debug | ADB install in Android Studio.
The problem only happen in app compiled for playstore release, it throws AbstractMethodError during file sending. I have raised the issue with the Android Studio development team for action. Refer to the link for more detail: https://issuetracker.google.com/issues/321988935
For aTalk v3.3.3: Temporary disable 'Jingle Outgoing File Offer', use only HTTP file upload instead to allow file transfer on aTalk
2024-01-23@21.25.32-logs.zip
Info below can help developer fix the problem:
Just starting the app.
The account configure does not sign in. It stays offline and no buddy list occurs.
The problem occurs every time I log in. It isn't possible to use atalk due to that. This is the case with version 3.3.1 from F-Droid and from Google Playstore. From F-Droid I could install version 3.2.4 and it works. It signs in and the buddy list is displayed.
Just sending this bug report again because I cannot find it in any outbox.