By Nov 1 all apps should support 16Kb page sizes.
2 Likes
Has there been any progress?
Yes, Mobile Payments SDK 2.3.1 supports the new requirements. 
Hi Bryan, could check that with the team?
Since I have checked the apk with the script provided by the Google team. It shows that the native lib libregister.so is UNALIGNED.
And it comes from the mobile payment SDK:
./caches/transforms-4/1aac5d497aac1f3cb408c20178eaf918/transformed/jetified-mobile-payments-sdk-2.3.1/jni/arm64-v8a/libregister.so
Hi Brian. 2.3.1 still doesn’t meet google requirements. Please check with the dev team since deadline is just around the corner
What isn’t working with the requirement? Are you getting an error or a warning?
It’s analysis tool that shows native libraries that aren’t meet google requirements about 16kb page sizes. It still highlights square mobile payment sdk (as shows on screenshot). It means that 2.3.1 version still doesn’t meet google requirements about 16kb page sizes support
Right, that is a warning about that native library.
It’s warning about square mobile payment sdk package deps, which means that Google won’t allow to publish updates for the app that has this deps starting Nov 1, until this is fixed
Right, it is a warning and the team is aware of this.
Can we get more clarification as to what you mean with your last statement? Is it:
- Google should approve app updates which use Mobile Payments SDK version 2.3.1 despite it having that warning.
Or:
- The Square team is aware that Mobile Payments SDK version 2.3.1 still has a problem.
Google should approve app updates which use Mobile Payments SDK version 2.3.1 despite it having that warning.
You need to be more specific) google accepts updates with this warning until Nov 1. After that it won’t accept any app updates until this problem is fixed. Optionally devs can extend deadline up to May 2026. But I don’t know approval rate for that.
In case I can’t make it. I have it extended. It seems more easier than what I expected.
However, please keep upgrade the SDK, Square team. Thanks.
It looks like version 2.3.2 has the fix and would be accepted by Google