Hello,
Starting November 1, 2025, all new apps and updates to existing apps submitted to Google Play and targeting Android 15+ devices must support 16 KB page sizes.
Zoom Meeting SDK native libraries are not yet compatible with 16 KB page sizes. This may prevent us from publishing updates once the requirement takes effect.
Could you please confirm when the Meeting SDK will be updated to support this requirement?
Thank you,
Best regards
Thanks for posting in our developer forum.
Our Android Meeting SDK already supports 16KB page size. If you faced any issues building the SDK application on the 16KB page size device, please let us know.
Elaine
Hi @elaine.ku
Can you tell me the specific version of the Android Meeting SDK that supports 16KB page size device?
Yes. It does not comply with 16KB page size requirements.
@michaelchen27 We support 16KB page size starting from Android Meeting SDK 6.3.0.
@AboveCloud9 Can you please provide the version you are using, and the errors you are facing with? Thank you!
We are testing our application with the Zoom Meeting SDK v6.6.0.33395 on an Android emulator that enforces 16KB page size (ARMv9/16KB memory pages). When launching the app, we receive an alert dialog stating that the app is not compliant with 16KB page size.
On inspecting the native libraries (.so files) inside the SDK using readelf, we observed that they are compiled with 4KB page size alignment instead of 16KB. This indicates that the current SDK release is not compatible with devices/environments that enforce 16KB page size.
@AboveCloud9 Are the 4KB page size .so files for armeabi-v7a? I checked with objdump, and the .so files under arm64-v8a should all be 16KB-aligned. Also, could you help take a screenshot of that alert dialog? Thank you!
Hi Team! I hope everything is going well.
We need your help to understand an unexpected behavior related to the migration from v6.1.1.22760 to v6.3.10.27979. The main goal of this migration is to comply with Google Play’s requirement to support 16KB memory page sizes, which will be enforced starting on November 1, 2025.
After applying v6.3.10.27979 and calling joinMeetingWithParams(meetingNo, password, displayName), the password dialog is shown to users (this does not happen with v6.1.1.22760).
For our use case, this behavior doesn’t make sense, since users are already logged into the app and receive a push notification that should allow them to join the meeting directly.
Implementation
ZoomSDKInitParams initParams = new ZoomSDKInitParams();
initParams.jwtToken = jwtToken;
initParams.enableLog = true;
initParams.logSize = 5;
initParams.enableGenerateDump = true;
initParams.domain = WEB_DOMAIN;
initParams.videoRawDataMemoryMode = ZoomSDKRawDataMemoryMode.ZoomSDKRawDataMemoryModeStack;
try {
Locale language = new Locale.Builder().setLanguageTag(languageLocale).build();
mZoomSDK.setSdkLocale(cordova.getActivity().getApplicationContext(), language);
} catch (Exception ex) {
mZoomSDK.setSdkLocale(cordova.getActivity().getApplicationContext(), Locale.US);
}
mZoomSDK.initialize(cordova.getContext(), this, initParams);
MeetingService meetingService = mZoomSDK.getMeetingService();
meetingService.addListener(this);
JoinMeetingParams params = new JoinMeetingParams();
params.displayName = displayName;
params.meetingNo = meetingNumber;
params.password = meetingPassword;
JoinMeetingOptions opts = new JoinMeetingOptions();
opts.no_audio = noAudio;
opts.no_video = noVideo;
int response = meetingService.joinMeetingWithParams(cordova.getActivity().getApplicationContext(), params, opts);
We also tried using the handZoomWebUrl method, sending the URL with the encrypted_password. However, the dialog still appears requesting the displayName, only after filling it in is it possible to join. I don’t have found any official documentation mention this field on the URL.
Finally, we also tried using the encrypted_password when invoking joinMeetingWithParams, but again the dialog appears, and after the user type the encrypted_password manually, it shows an error saying that the pwd is inválida.
Could you help identify the cause of this behavior? Have there been any changes to the SDK’s releases in this regard? Is it possible to work around it with some configuration?
Thank you in advance, and apologies for the lengthy explanation.