Optional app.json component parameter to specify supported platforms for component about react-native-test-app HOT 8 CLOSED

It's entirely possible (and from your comment, highly probable!) that the issue here is on our end. @sveinar, let's take a look at our integration pattern and see if we should be doing something different now that we've combined our test apps (previously, we had separate apps for each platform, but they were recently merged into one)

from react-native-test-app.

Yes, but it can live on our backlog until we get around to taking action on it.

Feel free to resolve this :)

from react-native-test-app.

Alternatively (additionally?) it would be nice to allow the different platforms to align on the same keys. As far as I can tell, the appKey property is used to initialize the component through various reflection-based means, but that means (implies?) that the different platforms can't share keys.

TL;DR: I have a scenario I want on all of my platforms, but I don't want N separate entries 😁

from react-native-test-app.

TL;DR: I have a scenario I want on all of my platforms, but I don't want N separate entries 😁

The appKey is just the key you use to register a React app, typically via AppRegistry.registerComponent. In the case of Android, iOS and macOS, we also support using said appKey to find a corresponding native class with the right interface. This particular special case happens at runtime though. None of this should prevent you from reusing the key for multiple platforms. You don't have to create separate entries if you don't want to. Is this not working as intended? What issues are you seeing?

from react-native-test-app.

Very possibly and it would be epic if the support already exists. Hoping that it is possible to resolve (via reflection) perhaps "Auth" to e.g. com.company.auth.AuthFragment for instance on Android..and on iOS, I guess the NSClassFromString("Auth") would resolve to the equivalent Auth controller right?

from react-native-test-app.

Very possibly and it would be epic if the support already exists. Hoping that it is possible to resolve (via reflection) perhaps "Auth" to e.g. com.company.auth.AuthFragment for instance on Android..and on iOS, I guess the NSClassFromString("Auth") would resolve to the equivalent Auth controller right?

Yes, this is how it's always been, since the very first release. You just need to make sure that your classes are appropriately named and/or exported (if you have a Swift class, you can decide what the Obj-C name is).

from react-native-test-app.

@sveinar, @evancharlton: Is this still needed?

from react-native-test-app.

Thanks, I'll close this for now. Let me know if you want to reopen it.

from react-native-test-app.