Severe issues with ios 15

Literally stripped one of my games to barebones, audio, fonts, events and the thing just won't play level 1. Really not impressed with trying to export to iOS, android, nice and simple, everything works as it should. iOS however oh my!

All crashes seem to be down to font and/or audio, yet without using any fonts or audio, the crashes still occur.

Use latest c3, export to high ios version, use smallest spritesheet setting, use latest xcode. See if that makes any difference.

Otherwise try turning off 'Canvas rendering' in Safari options and see if that makes any difference, just for verification.

Tried 12/13/14, xcode running latest version, multiple setting changes in C3.

Had a couple of xcode developers look at it but because it's Cordova, they have no idea. Another chaps looking at it now and said "the code is breaking it" so not sure what's going on, if some events or files are corrupting on export.

Just tried the canvas rendering method and still the same, crashing in the same spot each time (I've also removed this spot, an event based cutscene)and it's just crashing when the layout starts instead of letting the cutscene play/fade sprite fade in.

Weirdly, I made a button that goes to a random level and that worked.. made a button that goes to another cutscene level and that crashed

Can confirm that on iOS (specifically iPhone more than iPad) my ad does not make the game pause in the background. Also that my Sprite Fonts aren't always rendering. Also that my 9-patches aren't always rendering. Sometimes they do, but it's inconsistent.

And then sometimes the audio cuts out for the rest of the session.

I've just recently had Apple tell me that by latest build is bugging out during the C3 loading screen on iPad OS 15.2, so I updated my iPad and didn't see anything. Sent them a video but might send them this thread so they can see that the construct team believes that Apple broke iOS, so Apple can realize it and fix it. That is, if Apple cares about C3 developers. What say we? I doubt it, from my limited experience with them.

Same problem here on iOS 15

But in our case is not at Cordoba export, is a Web HTML export for the website, uploaded and tested on iPhones Safari Browser or installed in PWA.

We have problems with objects Disappearing becoming invisible but they are still there in their positions as you can touch them and all the events related to that object will run

I can confirm that is definitely iOS 15 because I test the same web project into two iPhones:

iPhone8 Plus: That has iOS 14.8.1

And the game runs smoothly without any issues

XS Max: That has iOS 15.1

Here the game run with issues like objects disappearing becoming invisible but they still are in their (X,Y) positions as you can touch them and interact with them, you can see the events firing up when touched.

This is a big issue as some of the objects disappearing are the Play button, Continue Button, HUD, etc.... so you don't know where to press to start playing or also backgrounds disappearing making the app show the layer black colour instead of the BG. The Game is unplayable on this state on iPhones running iOS 15

I created a Zip file demo reproducing the BUGS here:

Zip file

Some Videos showing the problem:

This is how it should look the "Menu" layout

This is how it should look the "Game" layout

Video1

https://www.dropbox.com/s/s0pumpt08da1zez/iOS%20BUG1.MP4?dl=0

You can see at min 00:15 the BG disappearing

Video2

https://www.dropbox.com/s/1t7ca6bem1ilqkn/iOS%20BUG2.MP4?dl=0

You can see at min 00:07 the BG disappearing

Video3:

https://www.dropbox.com/s/v5t5t1zupg77ip2/iOS%20BUG3.MP4?dl=0

You can see at min 00:15 the BG disappearing

Video4:

https://www.dropbox.com/s/h5lgm13xjzt5lz7/iOS%20BUG4.MP4?dl=0

You can see at min 00:07 the BG disappearing

===========================================

To reproduce it you just need to go back & Forwards between the two layouts until you see something disappearing

I just want to emphasise my previous post that points out if something worked on iOS 14 but broke in iOS 15, it's likely Apple that broke it, and so such problems are probably best reported directly to them. If it's iOS or Safari that is broken, there's usually little we can do about it ourselves; only Apple can fix problems in iOS or Safari.

tarek2 Try switching on/off these two settings for safari on your device, verify if it makes any difference for you:

• GPU Process: Canvas Rendering
• GPU Process: WebGL

> tarek2

I googled the issues and it seems that many people reported already the bug to Apple as most HTML games are affected though it has been around 3 months now since iOS 15 and they didn't make any progress, too bad.

Would you be able to share links to those other cases of developers encountering the problem?

It seems games are still loading fine in Safari itself. Suggesting that the problem is even in WKWebView or in the way that Cordova delivers the local files to WKWebView.

Either way, I do agree with Ashley that this problem is the result of a change by Apple but I want to share a few thoughts:

• Yes, we all could file bugs/reports to Apple ourselves. But has Scirra/Construct filed or notified Apple of this problem as an engine developer? Does Scirra have a contact at Apple or relationship they can follow up on?
• Even though Apple is an insanely large and profitable company, that doesn't always mean every team is well resourced. They may be aware of this issue but haven't had time to truly investigate it. If we are able to find more clues to the cause of the issue and provide that context to Apple, it might speed up the solving of the bug.
• Ignoring the issue and hoping Apple will fix it soon isn't really a strategy for success. If what

  Ashley says is true, that Apple change things regularly and this type of situation is common (e.g. once every 2 years, with the issues persisting for months) then that suggests it's worth spending time thinking of a new strategy to handle this scenario. By that I mean, having better processes for alerting, communicating and resolving the problem with Apple.

> > tarek2

> I googled the issues and it seems that many people reported already the bug to Apple as most HTML games are affected though it has been around 3 months now since iOS 15 and they didn't make any progress, too bad.

Would you be able to share links to those other cases of developers encountering the problem?

It seems games are still loading fine in Safari itself. Suggesting that the problem is even in WKWebView or in the way that Cordova delivers the local files to WKWebView.

Either way, I do agree with Ashley that this problem is the result of a change by Apple but I want to share a few thoughts:

• Yes, we all could file bugs/reports to Apple ourselves. But has Scirra/Construct filed or notified Apple of this problem as an engine developer? Does Scirra have a contact at Apple or relationship they can follow up on?
• Even though Apple is an insanely large and profitable company, that doesn't always mean every team is well resourced. They may be aware of this issue but haven't had time to truly investigate it. If we are able to find more clues to the cause of the issue and provide that context to Apple, it might speed up the solving of the bug.
• Ignoring the issue and hoping Apple will fix it soon isn't really a strategy for success. If what

  Ashley says is true, that Apple change things regularly and this type of situation is common (e.g. once every 2 years, with the issues persisting for months) then that suggests it's worth spending time thinking of a new strategy to handle this scenario. By that I mean, having better processes for alerting, communicating and resolving the problem with Apple.

If Scirra officially declares on the Construct homepage that you can publish games on iOS and other platforms, then they should be sure that it works correctly and without failures.

Otherwise it sounds like "Yes, you can export the game to iOS from our engine, but we do not guarantee that it will work. This is your problem, deal with it yourself."

So far I don't believe I've been able to reproduce the problem myself.

Ok, that's more understandable then. I assume you've attempted to recreate though?

If someone prepares a sample which triggers the problem, you would take a look?

Getting us to reproduce the problem is just an unnecessary extra step anyway ...

I respectfully disagree with this. I think tarek2 highlighted well several reasons why you should be establishing a relationship with Apple and representing the Construct community.

> Does Scirra have a contact at Apple or relationship they can follow up on?

Absolutely not. Apple are notoriously secretive to the point of absurdity, e.g. they mark bugs as fixed but can't tell us when the fix will ship, only saying "Apple does not comment on future releases" as a standard response. If Apple made anyone available to us, we'd definitely talk to them about such issues, but they do not make any such person available nor do they appear to have a culture that would be open to such an idea.

Maybe you could reach out to Jen Simmons? She joined Apple within the last couple of years and I've heard she's fairly responsive/helpful:

twitter.com/jensimmons

I understand when Construct started out that Apple was extremely difficult to communicate with. But over the last 10 years they've changed a fair bit. Their developer relations teams are more responsive than before.

I can only repeat that if there is a problem in iOS, and you actually want it to be fixed, the fastest thing is to cut us out the process and go direct to Apple. Try contacting their developer evangelists yourself if you think that will help. In my long experience though, the best way is to file a good bug report directly with Apple. Anything else is just beating around the bush.

Seems like the bug has been solved in 15.2.1, anyone can confirm also?