-
Hi everyone, I have created a .app file on Mac (destination Mac AppStore), using Flet build. What is the recommended way of creating an AppStore app from this? Bearing in mind the signing of the package, and launching in a seamless way. I have been trying to follow the steps in the Flutter documentation, but these don't seem applicable (or at least, my inexperience in Xcode is hurting me). Has anyone else done this? What are the steps to get an app into TestFlight? I'd be incredibly grateful if anyone has learnt any pain points or has pointers (I'm an Xcode noob...) So far, I have managed to get XCode to package my Python app (using XIB), but I come unstuck on the code signing. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
Part 1/2: signing Within the signing script, there are additional steps to sign a a Torch.zip folder that contains a Monkey Patch for Torch (and is unzipped), along with other .dylib files. Please see #3060 as to why a patch is needed. If you are not doing this, I suggest using the example from @m00sey (thank you btw), which I have built from (see #3326). It adds in steps that I needed to get this past notarisation, which included: timestamps, dylib signing, and unzipping that Torch.zip patch.
|
Beta Was this translation helpful? Give feedback.
-
Part 2/2: Create a blank Storyboard application in Xcode (XIB might also work). You will need to:
I have found that submitting an app for notarization has taken a very, very long time. The first time, it was around 24h. After that, and I resolved a lot of the errors, it came down to 6h, and after that.. with only minor changes, it is around 15minutes. So it does look like there is some kind of delta check they are operating. Following that.. your app should be good to go and past Apple's notarization process. Please note, I have tried to Sandbox my app and continually run into issues. I have Numpy bundled (fairly ubiquitous library), and Gatekeeper throws errors for "_multiarray_umath.cpython-311-darwin.so", saying that Apple cannot verify that it is free of malware. I have been unable to resolve this issue, and so have decided to ditch the Mac AppStore and Sandboxing altogether (a lot of effort to accept a 30% tax..). Honestly.. the most painful process possibly imaginable from Apple. Their entire documentation leaves a lot to be desired, and the process is in general, unnecessarily convoluted and complex.. |
Beta Was this translation helpful? Give feedback.
Part 1/2: signing
Just wanted to share the process. I have got a Flet app containing Torch to a point of passing notarisation, and through Xcode (although, no sandboxing).
Within the signing script, there are additional steps to sign a a Torch.zip folder that contains a Monkey Patch for Torch (and is unzipped), along with other .dylib files. Please see #3060 as to why a patch is needed. If you are not doing this, I suggest using the example from @m00sey (thank you btw), which I have built from (see #3326).
It adds in steps that I needed to get this past notarisation, which included: timestamps, dylib signing, and unzipping that Torch.zip patch.