As of April 12th, you must go to Progress SupportLink to create new support cases or to access existing cases. Please, bookmark the SupportLink URL and use the new portal to contact the support team.
We are pleased to inform you that a new release of the Android SDK v3.0.0 Beta-4 has been posted and is available for download at the following location.
This update fixes the problem described in this ticket regarding no setter of KinveyClient to authorize Twitter.
At your convenience, please download and test the fix and let us know if it works to your satisfaction.
I want to let you know that the fix for this problem has been tentatively targeted for the next sprint for this SDK. Our sprints usually last two to three weeks. As soon as I have a target date and a better description of the root cause and solution, I will update this ticket with the same.
Please let me know if you have any questions.
We have determined that this problem is a bug in our Android SDK. This issue has been escalated to Engineering and we have asked for prioritization into an upcoming release of the Android SDK.
We will confirm as soon as a target release has been identified.
To assist with the prioritization, can you share the impact of this problem on your development efforts? Are you able to work around this or is it a significant impediment to progress? Anything that you can share with respect to impact will be helpful in our prioritization efforts.
Thank you for providing a great details regarding this problem. I have given this problem an initial look and we had a conversation with Kinvey Engineering. We have some additional questions.
It turned out that there is no setter of KinveyClient instance in “Login” class constructor, which is used for executing LoginTwitter task.
Screenshots are here: