Hi, we’re running into policy violations with our Android Google Play store submissions because the pulse SDK is not build with 16KB page sizes. We were able to request a short extension but are warned that in the near future we will be unable to submit to the google play store if this isn’t resolved. Is this on anyone’s radar at kitware? Is there any release roadmap planned in the near future that will address this?
I am not getting that warning warning when I open up the Pulse project from the main branch in our repo.
The repo has a PulseC built using the NDK 28b, which does build with 16KB pages by default
It’s possible, while the code difference is minimal between 4.3.1 (which is in the unity asset store) and the 4.3.2 binaries in our repository… they were built with different NDK versions and options (Which might also be the reason why 4.3.1 wanted libc++)
I am pretty sure both of those issues were addressed in our repo… I do have confirmation by a 3rd party that the repo PulseC did meet the 16KB page requirement
It seems like I should just make a 4.3.2 asset package from our repo…
Oh no, it looks like I specified the static libc++ linkage on the wrong project, it should have been specified for the PulseC library
So that explains why you needed to manually add libc++ (I assume meta already has that library on it, but stock android does not)
It also looks like 4.3.1 was build using a dockcross from earlier this year with NDK r25 which requires a compiler option be set to get the 16kb page size, and doing some house keeping on the repo a few months later resulted in it containing the same code as 4.3.1, just built with an updated dockcross with NDK 28b which does 16KB by default…
Hard to QA all these targets and requirements…
Again, I will see if I can just update our 4.3.2 repo with libc++ statically linked android libraries (and create a 4.3.3 tag) and then build a unity asset with PulseC.a files as well for iOS/xrOS
I think that will cover most of the issues you ran into
Thanks for the feedback!!
Thanks @abray we have been using the Asset Store package considering it to be the most stable “official” release. We can use the version from the repo but we weren’t sure how much special setup we would need to figure out on all platforms vs the unity package and also largely due to the incompatibility between versions and we don’t have an automated way to rebuild all the states on the fly (we would love to be able to though) we don’t want to change the version unless we absolutely have to, in this case we have no choice or we can no longer publish to the google play store.