You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the Android Lifecycle Listeners page, it's stated that you should implement a class that implements the Package interface, but there's no information on how this class actually gets hooked into the app itself. There's also zero documentation anywhere else I can find about the Package interface, and the source code similarly contains no information.
It would be appreciated if there was even just a one-liner about how classes implementing Package are automatically detected and included. Had to test and hope it worked for myself, but having clear official documentation on how it works would be much better.
Thank you for filing this issue!
This comment acknowledges we believe this may be a bug and there’s enough information to investigate it.
However, we can’t promise any sort of timeline for resolution. We prioritize issues based on severity, breadth of impact, and alignment with our roadmap. If you’d like to help move it more quickly, you can continue to investigate it more deeply and/or you can open a pull request that fixes the cause.
Summary
In the Android Lifecycle Listeners page, it's stated that you should implement a class that implements the
Package
interface, but there's no information on how this class actually gets hooked into the app itself. There's also zero documentation anywhere else I can find about thePackage
interface, and the source code similarly contains no information.It would be appreciated if there was even just a one-liner about how classes implementing
Package
are automatically detected and included. Had to test and hope it worked for myself, but having clear official documentation on how it works would be much better.Link to the related docs page
https://docs.expo.dev/modules/android-lifecycle-listeners/
Anything else?
No response
The text was updated successfully, but these errors were encountered: