we are currently using version 2.x of the Amazon Login SDK in our application. We would like to update to the latest version 3.0.2. The new version introduces some changes especially concerning the Context object which is needed to authorize the user with Amazon. In the old version we could use an Application context for that which we handed over to the AmazonAuthorizationManager. The new SDK now requires a RequestContext for authorization, which can only be initialized with an Activity or Fragment context. Given the architecture of our application, which relies heavily on dependency injection, this context change makes it very difficult for us to integrate the new SDK without major refactoring. Also, there is always the potential risk of a memory leak, when passing an Activity/Fragment context around in an application. We could of course keep the RequestContext in each Activity where we need it but this would break up our architecture quite a bit, which tries to separate business logic and UI/UX as much as possible.
It would really help us, if the RequestContext could be initialized with an Application context as well. Are there any plans to provide this option in the future?