Issues from App Review when submitting a Python app

Question

Created Jul ’25

Replies 1

Boosts 0

Participants 2

Hi guys,

I am using Python and SciPy to develop a utility app. Planning to publish it on Apple Store for MacOS. So I submitted my app for Apple Review. But I was encountering the following "Guideline 2.5.1 - Performance - Software Requirements".

Your app uses or references the following non-public or deprecated APIs:

Contents/Frameworks/scipy/linalg/cython_blas.cpython-312-darwin.so
Symbols:
• _dcabs1_
• _lsame_

Contents/Frameworks/scipy/sparse/linalg/_propack/_spropack.cpython-312-darwin.so
Symbols:
• _lsame_

Contents/Frameworks/scipy/sparse/linalg/_propack/_zpropack.cpython-312-darwin.so
Symbols:
• _lsame_

Contents/Frameworks/scipy/sparse/linalg/_propack/_dpropack.cpython-312-darwin.so
Symbols:
• _lsame_

Contents/Frameworks/scipy/sparse/linalg/_propack/_cpropack.cpython-312-darwin.so
Symbols:
• _lsame_

Contents/Frameworks/scipy/linalg/cython_lapack.cpython-312-darwin.so
Symbols:
• _xerbla_array__

The use of non-public or deprecated APIs is not permitted on the App Store, as they can lead to a poor user experience should these APIs change and are otherwise not supported on Apple platforms.

They seem from using the SciPy library in my Python app. Is there a way to work around this issue? Please let me know if you have solved this kind of issue before.

Boost

Answer 1

fronx OP

Aug ’25

Try stripping symbols from the offending binaries:

strip -x *.so

Then check if you can still run your app.

If yes: add the stripping as a post-build step before you bundle and send your app off to Apple.

If no: compile scipy from source with an alternative BLAS/LAPACK implementation (e.g. OpenBLAS). Then try again the method described above.

1