App not starting correctly with Metal

[ThomasH99]

With 7.0.246, I compile my app locally with Xcode and get the below trace and after showing the splash screen the screen just turns white and nothing more happens (and no more trace in Xcode).

I've deleted most of my own log messages from the trace.

I can see the SKPayment error: I haven't activated payments yet, but it has compiled earlier before turning on metal, so I guess that shouldn't be a reason.

I also see this in case it's useful:

GSFont: "Untitled1" already exists.
<SKPaymentQueue: 0x12d058a90>: Error in remote proxy while checking server queue: Error Domain=SKInternalErrorDomain Code=12 "(null)" UserInfo={storefront-country-code=USA, client-environment-type=Sandbox}
Failed to create directory /var/mobile/Containers/Data/Application/6AF82F04-85BF-4A08-95FD-5D0A494477B5/Documents/cn1storage/
[EDT] 0:0:0,4 - Codename One revisions: 7dd4e7d08b3442d90959477ee52a5ae8c4361b29
[EDT] 0:0:0,6 - init() - STARTED
<SKPaymentQueue: 0x12d058a90>: Error in remote proxy while checking server queue: Error Domain=SKInternalErrorDomain Code=12 "(null)" UserInfo={storefront-country-code=USA, client-environment-type=Sandbox}
[EDT] 0:0:0,23 - Native Logs Reader initialized correctly
[EDT] 0:0:0,25 - Log started 30/05/2026 00:10
[EDT] 0:0:0,186 - init() - DONE - go to welcome screen...
[EDT] 0:0:0,186 - start()
[EDT] 0:0:0,187 - startApp()
Reachability Flag Status: -R t------ networkStatusForFlags
[EDT] 0:0:4,599 - Form: ScreenMain
Reachability Flag Status: -R t------ networkStatusForFlags
-[MTLDebugRenderCommandEncoder setRenderPipelineState:]:1639: failed assertion `Set Render Pipeline State Validation
For stencil attachment, the renderPipelineState pixelFormat must be MTLPixelFormatInvalid, as no texture is set.
'
warning: could not execute support code to read Objective-C class data in the process. This may reduce the quality of type information available.

[shai-almog]

SKPaymentQueue is a warning you get if you have any reference to the purchase API in the code but don't have any products defined. It isn't critical and things will still work as expected so there's no need to fix it. Just remove the purchase reference or add a product.

[ThomasH99]

Thanks. Any way I can get around this to continue testing metal or I have to wait for next build?

[shai-almog]

Since this is on a local build you can just copy the change to the metal file from the PR: #5110

[ThomasH99]

Great, I’d like to try that, but I’ve no experience with this kind of stuff so I need a bit of help: which file to where, and before or after the local generation of the xcode project?

[shai-almog]

Sorry I linked to the wrong PR which is probably the source of the confusion. That's a separate PR meant to catch bugs like this in CI. This is the PR: #5106

After generating the project find the file CN1Metalcompat.m and apply this diff into the file: https://github.com/codenameone/CodenameOne/pull/5106/changes

[ThomasH99]

Thanks! With 7.0.247, the app starts and runs well. I have a few small issues I'll report separately (but not sure they're even related to metal). Overall, the UI seems to feel a bit faster/smoother. However, I get flooded by logs like this in Xcode (when running on the device connected to Xcode):

metal-HUD: 7656,155.67,423.49,16.67,0.89,16.67,0.89,16.67,0.90,16.67,0.90,16.67,1.10,16.67,1.10,16.67,1.14,16.67,1.14,16.67,1.21,16.67,1.21,16.67,1.13,16.67,1.13,16.67,1.18,16.67,1.18,16.67,1.11,16.67,1.11,16.67,0.60,16.67,0.60,33.34,0.59,33.34,0.59,16.67,0.50,16.67,0.50,16.67,0.47,16.67,0.47,16.67,0.79,16.67,0.79,16.67,0.73,16.67,0.73,16.67,1.07,16.67,1.07,16.67,0.99,16.67,0.99,16.67,1.05,16.67,1.05,16.67,1.07,16.67,1.07,16.67,1.06,16.67,1.06,16.67,1.23,16.67,1.23,16.67,0.99,16.67,0.99,16.67,1.09,16.67,1.09,16.67,1.05,16.67,1.05,16.67,0.93,16.67,0.93,16.67,0.99,16.67,0.99,16.67,1.06,16.67,1.06,16.67,1.03,16.67,1.03,16.67,1.05,16.67,1.05,16.67,1.07,16.67,1.07,16.67,0.88