Can't submit to App Store Connect: Invalid font GCDWebUploader.bundle/fonts/glyphicons-halflings-regular.woff

Question

Can't submit to App Store Connect: Invalid font GCDWebUploader.bundle/fonts/glyphicons-halflings-regular.woff

johnmalatras opened this issue 7 months ago · comments

It appears that there is an odd issue myself and other folks are facing with the GCDWebUploader package (which SBTUITestTunnel depends on) after adding a widget target to your project. When uploading a build to App Store Connect, I get the error:

ITMS-90853: Invalid font - There was an error validating the font at 'Substack.app/GCDWebServer_GCDWebServer.bundle/GCDWebUploader.bundle/Contents/Resources/fonts/glyphicons-halflings-regular.woff'. Font not supported by platform.

More cases of this can be found in this issue. As GCDWebUploader is deprecated and we are using a Subito-it fork (which you also can't raise an issue on), I'm hoping this could be resolved here. Could this font be removed from the fork? Otherwise any other ideas for solutions?

Tomas Camin · Answer 1 · Sun Dec 10 2023 01:56:39 GMT+0800 (China Standard Time)

While the issue could be addressed modifying the GCDWebServer fork I would strongly recommend you to ensure not including SBTUITestTunnel in your AppStore builds as detailed in the setup documentation here

John Malatras · Answer 2 · Sun Dec 10 2023 03:13:52 GMT+0800 (China Standard Time)

I'm wrapping all imports/usages in #if DEBUG but it appears to be building GCDWebServer anyways

Tomas Camin · Answer 3 · Sun Dec 10 2023 03:58:04 GMT+0800 (China Standard Time)

I would suggest to have a dedicated target that does not include the sbtuitesttunnel and other testing libraries at all. The problem is that although wrapping with if DEBUG guarantees the code is not executed it does prevent the code from being compiled (and copied into the final binary).

John Malatras · Answer 4 · Mon Dec 11 2023 03:33:49 GMT+0800 (China Standard Time)

Interesting, so is the suggestion to have two targets for the main application? One which isn't linked to sbtuitesttunnel and one which is and is used for tests?

Tomas Camin · Answer 5 · Mon Dec 11 2023 03:38:04 GMT+0800 (China Standard Time)

Yes, this guarantees that no testing code ends up in production with the additional benefit of reducing the size of the app bundle.

…

On Sun, Dec 10, 2023 at 20:34 John Malatras ***@***.***> wrote: Interesting, so is the suggestion to have two targets for the main application? One which is linked to sbtuitesttunnel and one which is and is used for tests? — Reply to this email directly, view it on GitHub <#200 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGVUELVHKZYYBNM4RYBCG3YIYFCPAVCNFSM6AAAAABAN5HVO2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBZGA3DAMJRGQ> . You are receiving this because you commented.Message ID: ***@***.***>

John Malatras · Answer 6 · Mon Dec 11 2023 05:15:40 GMT+0800 (China Standard Time)

But in this case if you try to build the production target which has the sbtuitesttunnel dependency removed locally, it cannot find sbtuitesttunnel in AppDelegate. I suppose this new target without sbtuitesttunnel will need to strictly be used for production CD and not locally.

As the root cause here is a bug in the upstream library, could the invalid font be removed in the meantime? As it stands anyone with a widget cannot submit to Apple and we'll need to refactor some of our CI/CD process to support this new target.

Tomas Camin · Answer 7 · Mon Dec 11 2023 21:39:09 GMT+0800 (China Standard Time)

Would using #if canImport(SBTUITestTunnelServer) work instead?

John Malatras · Answer 8 · Tue Dec 12 2023 02:05:44 GMT+0800 (China Standard Time)

Yep that works! Awesome, I'll create a new target that I only have to use for UI tests which includes SBTUITestTunnelServer. Thanks for the help!