Files
react-navigation/android
Krzysztof Magiera 369987f68e Make sure we access fragment manager only when view is attached (activity is foregrounded) (#52)
This change makes us reach to fragment manager only when screen container is attached to window (and therefore we are sure that the current activity is react one). The problem reported in #33 was due to the fact we'd do that when container is instantiated which does not necessarily mean that react activity is in foreground. We didn't need to actually access fragment manager while not in foreground so this change removes fragmentManager as a member and we get it directly from context when needed.

Supposedly fixes #33
2018-12-20 11:02:39 +01:00
..
2018-08-03 13:54:11 +02:00
2018-12-18 12:53:56 +01:00
2018-08-03 13:54:11 +02:00
2018-08-03 13:54:11 +02:00
2018-08-03 13:54:11 +02:00
2018-08-03 13:54:11 +02:00
2018-08-03 13:54:11 +02:00

README

If you want to publish the lib as a maven dependency, follow these steps before publishing a new version to npm:

  1. Be sure to have the Android SDK and NDK installed
  2. Be sure to have a local.properties file in this folder that points to the Android SDK and NDK
ndk.dir=/Users/{username}/Library/Android/sdk/ndk-bundle
sdk.dir=/Users/{username}/Library/Android/sdk
  1. Delete the maven folder
  2. Run sudo ./gradlew installArchives
  3. Verify that latest set of generated files is in the maven folder with the correct version number