Skip to content

How to update existing modules for newer tool versions #19

Description

@brody2consult

See comment below for recommended procedure (as a workaround)

As requested in (updated):

For recent updates it is recommended to copy the updated entries from the following general areas into android/build.gradle:

For major version updates it is generally recommended to regenerate and copy the needed artifacts for Android into the existing module.

Labeled as a bug; I hope to get this documented in the near future.

TODO items (updated):

  • document a workaround upgrade procedure
  • add upgrade documentation in a similar style to: https://docs.expo.io/versions/v34.0.0/workflow/upgrading-expo-sdk-walkthrough/
  • fix generated android/build.gradle to read and use the packageIdentifier value from package.json, in order to make this Android build artifact zero percent customized
  • consider ideas for smoother upgrade support such as:
    • make an actual module template in a similar style to the react-native project template
    • make a native module seed similar to the Nativescript plugin seed

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions