Hi,
I am using a third party component in Xamarin for authentication and this component is launching an activity. When back from the authentication I am trying to navigate to new activity and I am getting the following error:
No CurrentActivity found.
I think that I understand why I am getting this error. It is because the activity from the third party component is not extending activitybase. When debugging I am able to see that the ActivityBase.CurrentActivity is not null before calling the component, however it is null after.
Any idea how I could make this work?
Thank you,
Alexis Theriault
Comments: I did the same modification in my implementation and finally it does not help me completely.. I have the following problem in the following scenario using the developer options 'Dont keep activities'. -Start my home activity -launching a third party activity which does not extend ActivityBase -This cause my home activity to be destroyed -call the navigationservice -Does not work since there is no more CurrentActivity. If I do not set the CurrentActivity to null on destroy it is working fine. I am thinking that keeping the currentactivity even when the activity is destroyed should not cause a memory leak since at some point a new activity will be created and the reference to the destroyed activity will be lost. Any other idea? Thanks, Alexis
I am using a third party component in Xamarin for authentication and this component is launching an activity. When back from the authentication I am trying to navigate to new activity and I am getting the following error:
No CurrentActivity found.
I think that I understand why I am getting this error. It is because the activity from the third party component is not extending activitybase. When debugging I am able to see that the ActivityBase.CurrentActivity is not null before calling the component, however it is null after.
Any idea how I could make this work?
Thank you,
Alexis Theriault
Comments: I did the same modification in my implementation and finally it does not help me completely.. I have the following problem in the following scenario using the developer options 'Dont keep activities'. -Start my home activity -launching a third party activity which does not extend ActivityBase -This cause my home activity to be destroyed -call the navigationservice -Does not work since there is no more CurrentActivity. If I do not set the CurrentActivity to null on destroy it is working fine. I am thinking that keeping the currentactivity even when the activity is destroyed should not cause a memory leak since at some point a new activity will be created and the reference to the destroyed activity will be lost. Any other idea? Thanks, Alexis