fixed react native 81 sdk compatibility issues #1514
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request updates the React Native HMS Android module to improve compatibility with React Native 0.81 by ensuring that event and command maps are returned as
MutableMapinstances. It also refactors the usage of the current activity throughoutHMSManagerto consistently usereactApplicationContext.currentActivity, which is a more reliable way to access the current activity in React Native modules.React Native 0.81 compatibility improvements
getExportedCustomDirectEventTypeConstants,getExportedCustomBubblingEventTypeConstants, andgetCommandsMapinHMSHLSPlayerManagerandHMSSDKViewManagerto wrap maps withHashMap, ensuring the returned type matches the expectedMutableMapsignature for React Native 0.81. [1] [2] [3] [4] [5]Activity access refactoring
currentActivitywithreactApplicationContext.currentActivityinHMSManager, making activity access more robust and preventing potential null pointer issues. This change affects PIP registration, screenshare, audioshare, and lifecycle callback registration/unregistration. [1] [2] [3] [4] [5] [6] [7] [8] [9]