I'll submit again with that build and see if it works. So for v6.5.0 there won't be that *-appstore-compliant *option anymore, it will be simply already compliant? Thanks
On Fri, Mar 31, 2023 at 10:28 AM Cristián Maureira-Fredes < cristian.maureira-fre...@qt.io> wrote: > Hey Pedro, > > Glad you managed to reduce the amount of invalid symbols. > > There is no other PySide distribution, so I think the safe bet > would be to build Qt, but only the modules you need by yourself > with that option, then building PySide only for those modules, > and then packaging your app, or wait for 6.5 which should not include > those symbols according to > https://codereview.qt-project.org/c/qt/qtbase/+/437376 > > > Maybe you can try the RC wheels of PySide? > they can always be found in > https://download.qt.io/snapshots/ci/pyside/dev/latest/split_wheels/ > > and if those don't present the issue, maybe you just need to wait for > the official release of 6.5.0 > > If that doesn't work, it'd be something we'd need to explore for maybe > 6.5.1 if possible. > > Cheers! > > On 3/31/23 09:42, Pedro Ferreira wrote: > > Hello again, I've been able to get rid of the izma issues by building on > > a arm mac, that somehow improved things but they still complain about > > these 2: > > > > Symbols: _responsibility_get_pid_responsible_for_pid, > > _responsibility_spawnattrs_setdisclaim > > > > I found this ticket: https://bugreports.qt.io/browse/QTBUG-109032 > > <https://bugreports.qt.io/browse/QTBUG-109032> > > and apparently there's an option when building Qt that you can use: > > *-appstore-compliant* > > * > > * > > Is there a build of PySide/Qt that was build with this option that I can > > use? > > Thanks > > > > On Tue, Mar 28, 2023 at 3:13 PM Pedro Ferreira <plferrei...@gmail.com > > <mailto:plferrei...@gmail.com>> wrote: > > > > Hello Cristián, thanks for the reply. So are these symbols from > > python rather than Qt? > > I'll ask in another forum, thanks! > > > > On Mon, Mar 27, 2023 at 3:56 PM Cristián Maureira-Fredes via PySide > > <pyside@qt-project.org <mailto:pyside@qt-project.org>> wrote: > > > > Hey Pedro, > > > > thanks for reaching out on this. > > > > There are a couple of symbols that are guarded by the dev build > > of Qt > > https://codereview.qt-project.org/c/qt/qtbase/+/437376 > > <https://codereview.qt-project.org/c/qt/qtbase/+/437376> > > > > But many of the others, like > > _lzma_stream_encoder, _lzma_alone_decoder, etc > > are present in CPython while building > > > > > https://github.com/python/cpython/blob/a059395921e4402c13a860aaa8fc44fea2023aa3/PCbuild/liblzma.vcxproj > < > https://github.com/python/cpython/blob/a059395921e4402c13a860aaa8fc44fea2023aa3/PCbuild/liblzma.vcxproj > > > > > > > > It could be that also there are some artifacts from pyinstaller, > > but I don't have experience getting applications to the App Store > > so you might want to ask on the forum.qt.io <http://forum.qt.io> > > or in some apple related > > forum. Maybe there people with more experience might help you. > > > > Cheers > > > > > > On 3/27/23 10:42, Pedro Ferreira wrote: > > > Hello, I have an application written with PySide that I'm > > trying to > > > submit to the Mac Store. I'm using PyInstaller to package it > > and sign it. > > > > > > I submitted the app but on the review process I got a > > rejection with > > > this message: > > > > > > > > > Your app uses or references the following non-public or > > deprecated APIs: > > > Symbols: _lzma_alone_decoder, _lzma_get_check, _lzma_end, > > > _lzma_stream_decoder, _lzma_properties_size, > > > _lzma_check_is_supported, _lzma_raw_decoder, > > > _lzma_properties_encode, _lzma_auto_decoder, _lzma_code, > > > _lzma_properties_decode, _lzma_easy_encoder, > > _lzma_lzma_preset, > > > _lzma_stream_encoder, _lzma_alone_encoder, > _lzma_raw_encoder, > > > _responsibility_spawnattrs_setdisclaim, > > > _responsibility_get_pid_responsible_for_pid > > > > > > > > > > > > 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. > > > > > > > > > > > > I'm assuming this comes from Qt/PySide but have no idea how I > > can solve > > > this. Is there a different build that I can use that maybe > > doesn't have > > > these symbols? Or some other idea, not sure what to do. > > > > > > Thanks > > > > > > _______________________________________________ > > > PySide mailing list > > > PySide@qt-project.org <mailto:PySide@qt-project.org> > > > https://lists.qt-project.org/listinfo/pyside > > <https://lists.qt-project.org/listinfo/pyside> > > > > -- > > Dr. Cristián Maureira-Fredes > > Senior R&D Manager > > > > The Qt Company GmbH > > Erich-Thilo-Str. 10 > > D-12489 Berlin > > > > Geschäftsführer: Mika Pälsi, > > Juha Varelius, Jouni Lintunen > > Sitz der Gesellschaft: Berlin, > > Registergericht: Amtsgericht > > Charlottenburg, HRB 144331 B > > _______________________________________________ > > PySide mailing list > > PySide@qt-project.org <mailto:PySide@qt-project.org> > > https://lists.qt-project.org/listinfo/pyside > > <https://lists.qt-project.org/listinfo/pyside> > > > > -- > Dr. Cristián Maureira-Fredes > Senior R&D Manager > > The Qt Company GmbH > Erich-Thilo-Str. 10 > D-12489 Berlin > > Geschäftsführer: Mika Pälsi, > Juha Varelius, Jouni Lintunen > Sitz der Gesellschaft: Berlin, > Registergericht: Amtsgericht > Charlottenburg, HRB 144331 B >
_______________________________________________ PySide mailing list PySide@qt-project.org https://lists.qt-project.org/listinfo/pyside