[Android][0.29] No longer possible to access Activity from SimpleViewManager

[marcshilling]

According to the 0.29.0 upgrade docs, it's now very easy to extend ReactContextBaseJavaModule and use getCurrentActivity to get the activity reference in native Android modules. However, it no longer appears to be possible to get access to the current activity from native Android UI Components.

Continuing a discussion started here, I need access to the activity so that I can create a FragmentManager to add a Fragment to the FrameLayout being vended from SimpleViewManager. There was a suggestion that ReactContext.getCurrentActivity() be made public, which seems like a bad idea, but I can't think of another way.

[satya164]

Have you tried 49f20f4#commitcomment-18177294 ?

[marcshilling]

Yeah, that's me discussing the issue in those comments also 😛 . After that discussion went nowhere, I decided to open this issue.

[satya164]

@marcshilling yes, but you didn't reply if view.getContext works.

[marcshilling]

It didn't.

[InnerPeace080]

hi . this is my workaround to solve this problem . hope it will help u
InnerPeace080@c0838f0

now. we can use getPackages(Activity activity)

[marcshilling]

@InnerPeace080 you should send a pull request so we can get this in core!

[nickjanssen]

+1 I also cannot access Activity any longer, I need it in the constructor phase in order to get a SplashScreen working. Calling getCurrentActivity() in the constructor simply returns null.

public class SplashScreen extends ReactContextBaseJavaModule {

    public SplashScreen(ReactApplicationContext reactContext) {
        super(reactContext);

        getCurrentActivity() // null
    }

[marcshilling]

@nickjanssen that's actually different from the issue being discussed here. You are extending ReactContextBaseJavaModule, which has access to getCurrentActivity(). See this comment about why you can't use getCurrentActivity() in the constructor.

This issue is regarding SimpleViewManager extensions not having getCurrentActivity(), which is an issue that still remains in 0.30.0.

[skevy]

@foghina any thoughts on this? Seems like something super useful to get fixed.

[foghina]

Having getPackages take an Activity parameter is a much worse idea than making ReactContext#getCurrentActivity() public, for the following reasons:

1. We don't want to tie package / module / viewmanager (and ultimately ReactContext / react instance) creation to an Activity, as we want to be able to initialize a react instance in any context.
2. As the current in getCurrentActivity() suggests, the Activity can change over time. Holding a reference to whatever the activity was at react instance creation time is both incorrect and a memory leak.

As long as we properly document getCurrentActivity() (I think it already is documented in caps that you shouldn't hold references to the result), it should be fine to make it public.