[android] [native-modules-android.md] consistent code for adding package to MainApplication.kt

[ChronSyn]

Updated the documentation regarding adding packages to MainApplication.kt, so that they are consistent with https://reactnative.dev/docs/native-components-android

Further reasoning
The method listed in the pre-commit version did not correctly register the module in my testing, but the version in the proposed change does appear to work as expected

[facebook-github-bot]

Hi @ChronSyn!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[netlify]

✅ Deploy Preview for react-native ready!

Name	Link
🔨 Latest commit	051c026
🔍 Latest deploy log	https://app.netlify.com/sites/react-native/deploys/65ef274ad2605e000842f37c
😎 Deploy Preview	https://deploy-preview-4047--react-native.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[cortinico]

Thanks for sending this over @ChronSyn

Updated the documentation regarding adding packages to MainApplication.kt, so that they are consistent with reactnative.dev/docs/native-components-android

We should instead update the other page to follow the same pattern as in the template:

override fun getPackages(): List<ReactPackage> =
PackageList(this).packages.apply {
// Packages that cannot be autolinked yet can be added manually here, for example:
// packages.add(new MyReactNativePackage());
add(MyAppPackage())
}

[ChronSyn]

Thanks for sending this over @ChronSyn

Updated the documentation regarding adding packages to MainApplication.kt, so that they are consistent with reactnative.dev/docs/native-components-android

We should instead update the other page to follow the same pattern as in the template:

override fun getPackages(): List<ReactPackage> =
PackageList(this).packages.apply {
// Packages that cannot be autolinked yet can be added manually here, for example:
// packages.add(new MyReactNativePackage());
add(MyAppPackage())
}

This looks to match the pre-commit version. That didn't appear to work correctly for me. It seemed that the return type was the cause of the problems, but I wasn't sure why. However, after retesting, I've confirmed that wasn't the issue so I've reintroduced it.

I've made an amendment to your suggestion - new MyReactNativePackage() is not valid for Kotlin and will cause the native module to be null on the JS side.

Further context of why this PR was opened is available at react/react-native#41856 . That mentions the same issue, but it doesn't look like a PR was raised for the website docs to be corrected.

I've updated both files to be consistent.

[cortinico]

@ChronSyn can you also backport your change to the versioned docs?

[ChronSyn]

Updated the documentation regarding adding packages to MainApplication.kt, so that they are consistent with https://reactnative.dev/docs/native-components-android

Further reasoning
The method listed in the pre-commit version did not correctly register the module in my testing, but the version in the proposed change does appear to work as expected

[facebook-github-bot]

Hi @ChronSyn!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[netlify]

✅ Deploy Preview for react-native ready!

Name	Link
🔨 Latest commit	051c026
🔍 Latest deploy log	https://app.netlify.com/sites/react-native/deploys/65ef274ad2605e000842f37c
😎 Deploy Preview	https://deploy-preview-4047--react-native.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[cortinico]

Thanks for sending this over @ChronSyn

Updated the documentation regarding adding packages to MainApplication.kt, so that they are consistent with reactnative.dev/docs/native-components-android

We should instead update the other page to follow the same pattern as in the template:

override fun getPackages(): List<ReactPackage> =
PackageList(this).packages.apply {
// Packages that cannot be autolinked yet can be added manually here, for example:
// packages.add(new MyReactNativePackage());
add(MyAppPackage())
}

[ChronSyn]

Thanks for sending this over @ChronSyn

Updated the documentation regarding adding packages to MainApplication.kt, so that they are consistent with reactnative.dev/docs/native-components-android

We should instead update the other page to follow the same pattern as in the template:

override fun getPackages(): List<ReactPackage> =
PackageList(this).packages.apply {
// Packages that cannot be autolinked yet can be added manually here, for example:
// packages.add(new MyReactNativePackage());
add(MyAppPackage())
}

This looks to match the pre-commit version. That didn't appear to work correctly for me. It seemed that the return type was the cause of the problems, but I wasn't sure why. However, after retesting, I've confirmed that wasn't the issue so I've reintroduced it.

I've made an amendment to your suggestion - new MyReactNativePackage() is not valid for Kotlin and will cause the native module to be null on the JS side.

Further context of why this PR was opened is available at react/react-native#41856 . That mentions the same issue, but it doesn't look like a PR was raised for the website docs to be corrected.

I've updated both files to be consistent.

[cortinico]

@ChronSyn can you also backport your change to the versioned docs?

[ChronSyn]

Updated the documentation regarding adding packages to MainApplication.kt, so that they are consistent with https://reactnative.dev/docs/native-components-android

Further reasoning
The method listed in the pre-commit version did not correctly register the module in my testing, but the version in the proposed change does appear to work as expected

[facebook-github-bot]

Hi @ChronSyn!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[netlify]

✅ Deploy Preview for react-native ready!

Name	Link
🔨 Latest commit	051c026
🔍 Latest deploy log	https://app.netlify.com/sites/react-native/deploys/65ef274ad2605e000842f37c
😎 Deploy Preview	https://deploy-preview-4047--react-native.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[cortinico]

Thanks for sending this over @ChronSyn

Updated the documentation regarding adding packages to MainApplication.kt, so that they are consistent with reactnative.dev/docs/native-components-android

We should instead update the other page to follow the same pattern as in the template:

override fun getPackages(): List<ReactPackage> =
PackageList(this).packages.apply {
// Packages that cannot be autolinked yet can be added manually here, for example:
// packages.add(new MyReactNativePackage());
add(MyAppPackage())
}

[ChronSyn]

Thanks for sending this over @ChronSyn

Updated the documentation regarding adding packages to MainApplication.kt, so that they are consistent with reactnative.dev/docs/native-components-android

We should instead update the other page to follow the same pattern as in the template:

override fun getPackages(): List<ReactPackage> =
PackageList(this).packages.apply {
// Packages that cannot be autolinked yet can be added manually here, for example:
// packages.add(new MyReactNativePackage());
add(MyAppPackage())
}

This looks to match the pre-commit version. That didn't appear to work correctly for me. It seemed that the return type was the cause of the problems, but I wasn't sure why. However, after retesting, I've confirmed that wasn't the issue so I've reintroduced it.

I've made an amendment to your suggestion - new MyReactNativePackage() is not valid for Kotlin and will cause the native module to be null on the JS side.

Further context of why this PR was opened is available at react/react-native#41856 . That mentions the same issue, but it doesn't look like a PR was raised for the website docs to be corrected.

I've updated both files to be consistent.

[cortinico]

@ChronSyn can you also backport your change to the versioned docs?

[ChronSyn]

Updated the documentation regarding adding packages to MainApplication.kt, so that they are consistent with https://reactnative.dev/docs/native-components-android

Further reasoning
The method listed in the pre-commit version did not correctly register the module in my testing, but the version in the proposed change does appear to work as expected

[facebook-github-bot]

Hi @ChronSyn!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[netlify]

✅ Deploy Preview for react-native ready!

Name	Link
🔨 Latest commit	051c026
🔍 Latest deploy log	https://app.netlify.com/sites/react-native/deploys/65ef274ad2605e000842f37c
😎 Deploy Preview	https://deploy-preview-4047--react-native.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[cortinico]

Thanks for sending this over @ChronSyn

Updated the documentation regarding adding packages to MainApplication.kt, so that they are consistent with reactnative.dev/docs/native-components-android

We should instead update the other page to follow the same pattern as in the template:

override fun getPackages(): List<ReactPackage> =
PackageList(this).packages.apply {
// Packages that cannot be autolinked yet can be added manually here, for example:
// packages.add(new MyReactNativePackage());
add(MyAppPackage())
}

[ChronSyn]

Thanks for sending this over @ChronSyn

Updated the documentation regarding adding packages to MainApplication.kt, so that they are consistent with reactnative.dev/docs/native-components-android

We should instead update the other page to follow the same pattern as in the template:

override fun getPackages(): List<ReactPackage> =
PackageList(this).packages.apply {
// Packages that cannot be autolinked yet can be added manually here, for example:
// packages.add(new MyReactNativePackage());
add(MyAppPackage())
}

This looks to match the pre-commit version. That didn't appear to work correctly for me. It seemed that the return type was the cause of the problems, but I wasn't sure why. However, after retesting, I've confirmed that wasn't the issue so I've reintroduced it.

I've made an amendment to your suggestion - new MyReactNativePackage() is not valid for Kotlin and will cause the native module to be null on the JS side.

Further context of why this PR was opened is available at react/react-native#41856 . That mentions the same issue, but it doesn't look like a PR was raised for the website docs to be corrected.

I've updated both files to be consistent.

[cortinico]

@ChronSyn can you also backport your change to the versioned docs?

[ChronSyn]

Updated the documentation regarding adding packages to MainApplication.kt, so that they are consistent with https://reactnative.dev/docs/native-components-android

Further reasoning
The method listed in the pre-commit version did not correctly register the module in my testing, but the version in the proposed change does appear to work as expected

[facebook-github-bot]

Hi @ChronSyn!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[netlify]

✅ Deploy Preview for react-native ready!

Name	Link
🔨 Latest commit	051c026
🔍 Latest deploy log	https://app.netlify.com/sites/react-native/deploys/65ef274ad2605e000842f37c
😎 Deploy Preview	https://deploy-preview-4047--react-native.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[cortinico]

Thanks for sending this over @ChronSyn

Updated the documentation regarding adding packages to MainApplication.kt, so that they are consistent with reactnative.dev/docs/native-components-android

We should instead update the other page to follow the same pattern as in the template:

override fun getPackages(): List<ReactPackage> =
PackageList(this).packages.apply {
// Packages that cannot be autolinked yet can be added manually here, for example:
// packages.add(new MyReactNativePackage());
add(MyAppPackage())
}

[ChronSyn]

Thanks for sending this over @ChronSyn

Updated the documentation regarding adding packages to MainApplication.kt, so that they are consistent with reactnative.dev/docs/native-components-android

We should instead update the other page to follow the same pattern as in the template:

override fun getPackages(): List<ReactPackage> =
PackageList(this).packages.apply {
// Packages that cannot be autolinked yet can be added manually here, for example:
// packages.add(new MyReactNativePackage());
add(MyAppPackage())
}

This looks to match the pre-commit version. That didn't appear to work correctly for me. It seemed that the return type was the cause of the problems, but I wasn't sure why. However, after retesting, I've confirmed that wasn't the issue so I've reintroduced it.

I've made an amendment to your suggestion - new MyReactNativePackage() is not valid for Kotlin and will cause the native module to be null on the JS side.

Further context of why this PR was opened is available at react/react-native#41856 . That mentions the same issue, but it doesn't look like a PR was raised for the website docs to be corrected.

I've updated both files to be consistent.

[cortinico]

@ChronSyn can you also backport your change to the versioned docs?

[ChronSyn]

Updated the documentation regarding adding packages to MainApplication.kt, so that they are consistent with https://reactnative.dev/docs/native-components-android

Further reasoning
The method listed in the pre-commit version did not correctly register the module in my testing, but the version in the proposed change does appear to work as expected

[facebook-github-bot]

Hi @ChronSyn!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[netlify]

✅ Deploy Preview for react-native ready!

Name	Link
🔨 Latest commit	051c026
🔍 Latest deploy log	https://app.netlify.com/sites/react-native/deploys/65ef274ad2605e000842f37c
😎 Deploy Preview	https://deploy-preview-4047--react-native.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[cortinico]

Thanks for sending this over @ChronSyn

Updated the documentation regarding adding packages to MainApplication.kt, so that they are consistent with reactnative.dev/docs/native-components-android

We should instead update the other page to follow the same pattern as in the template:

override fun getPackages(): List<ReactPackage> =
PackageList(this).packages.apply {
// Packages that cannot be autolinked yet can be added manually here, for example:
// packages.add(new MyReactNativePackage());
add(MyAppPackage())
}

[ChronSyn]

Thanks for sending this over @ChronSyn

Updated the documentation regarding adding packages to MainApplication.kt, so that they are consistent with reactnative.dev/docs/native-components-android

We should instead update the other page to follow the same pattern as in the template:

override fun getPackages(): List<ReactPackage> =
PackageList(this).packages.apply {
// Packages that cannot be autolinked yet can be added manually here, for example:
// packages.add(new MyReactNativePackage());
add(MyAppPackage())
}

This looks to match the pre-commit version. That didn't appear to work correctly for me. It seemed that the return type was the cause of the problems, but I wasn't sure why. However, after retesting, I've confirmed that wasn't the issue so I've reintroduced it.

I've made an amendment to your suggestion - new MyReactNativePackage() is not valid for Kotlin and will cause the native module to be null on the JS side.

Further context of why this PR was opened is available at react/react-native#41856 . That mentions the same issue, but it doesn't look like a PR was raised for the website docs to be corrected.

I've updated both files to be consistent.

[cortinico]

@ChronSyn can you also backport your change to the versioned docs?

[ChronSyn]

Updated the documentation regarding adding packages to MainApplication.kt, so that they are consistent with https://reactnative.dev/docs/native-components-android

Further reasoning
The method listed in the pre-commit version did not correctly register the module in my testing, but the version in the proposed change does appear to work as expected

[facebook-github-bot]

Hi @ChronSyn!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[netlify]

✅ Deploy Preview for react-native ready!

Name	Link
🔨 Latest commit	051c026
🔍 Latest deploy log	https://app.netlify.com/sites/react-native/deploys/65ef274ad2605e000842f37c
😎 Deploy Preview	https://deploy-preview-4047--react-native.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[cortinico]

Thanks for sending this over @ChronSyn

Updated the documentation regarding adding packages to MainApplication.kt, so that they are consistent with reactnative.dev/docs/native-components-android

We should instead update the other page to follow the same pattern as in the template:

override fun getPackages(): List<ReactPackage> =
PackageList(this).packages.apply {
// Packages that cannot be autolinked yet can be added manually here, for example:
// packages.add(new MyReactNativePackage());
add(MyAppPackage())
}

[ChronSyn]

Thanks for sending this over @ChronSyn

Updated the documentation regarding adding packages to MainApplication.kt, so that they are consistent with reactnative.dev/docs/native-components-android

We should instead update the other page to follow the same pattern as in the template:

override fun getPackages(): List<ReactPackage> =
PackageList(this).packages.apply {
// Packages that cannot be autolinked yet can be added manually here, for example:
// packages.add(new MyReactNativePackage());
add(MyAppPackage())
}

This looks to match the pre-commit version. That didn't appear to work correctly for me. It seemed that the return type was the cause of the problems, but I wasn't sure why. However, after retesting, I've confirmed that wasn't the issue so I've reintroduced it.

I've made an amendment to your suggestion - new MyReactNativePackage() is not valid for Kotlin and will cause the native module to be null on the JS side.

Further context of why this PR was opened is available at react/react-native#41856 . That mentions the same issue, but it doesn't look like a PR was raised for the website docs to be corrected.

I've updated both files to be consistent.

[cortinico]

@ChronSyn can you also backport your change to the versioned docs?

[ChronSyn]

Updated the documentation regarding adding packages to MainApplication.kt, so that they are consistent with https://reactnative.dev/docs/native-components-android

Further reasoning
The method listed in the pre-commit version did not correctly register the module in my testing, but the version in the proposed change does appear to work as expected

[facebook-github-bot]

Hi @ChronSyn!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[netlify]

✅ Deploy Preview for react-native ready!

Name	Link
🔨 Latest commit	051c026
🔍 Latest deploy log	https://app.netlify.com/sites/react-native/deploys/65ef274ad2605e000842f37c
😎 Deploy Preview	https://deploy-preview-4047--react-native.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[cortinico]

Thanks for sending this over @ChronSyn

Updated the documentation regarding adding packages to MainApplication.kt, so that they are consistent with reactnative.dev/docs/native-components-android

We should instead update the other page to follow the same pattern as in the template:

override fun getPackages(): List<ReactPackage> =
PackageList(this).packages.apply {
// Packages that cannot be autolinked yet can be added manually here, for example:
// packages.add(new MyReactNativePackage());
add(MyAppPackage())
}

[ChronSyn]

Thanks for sending this over @ChronSyn

Updated the documentation regarding adding packages to MainApplication.kt, so that they are consistent with reactnative.dev/docs/native-components-android

We should instead update the other page to follow the same pattern as in the template:

override fun getPackages(): List<ReactPackage> =
PackageList(this).packages.apply {
// Packages that cannot be autolinked yet can be added manually here, for example:
// packages.add(new MyReactNativePackage());
add(MyAppPackage())
}

This looks to match the pre-commit version. That didn't appear to work correctly for me. It seemed that the return type was the cause of the problems, but I wasn't sure why. However, after retesting, I've confirmed that wasn't the issue so I've reintroduced it.

I've made an amendment to your suggestion - new MyReactNativePackage() is not valid for Kotlin and will cause the native module to be null on the JS side.

Further context of why this PR was opened is available at react/react-native#41856 . That mentions the same issue, but it doesn't look like a PR was raised for the website docs to be corrected.

I've updated both files to be consistent.

[cortinico]

@ChronSyn can you also backport your change to the versioned docs?