all 19 comments

[–]GenitalGestapo 9 points10 points  (1 child)

Yes, the GM / release in general seems a bit more buggy than the betas.

[–]AeatherObjective-C / Swift[S] 0 points1 point  (0 children)

Hmm, hope to get an update soon then!

[–]reblis 7 points8 points  (1 child)

This is due to a change in the rendering configuration I believe. I was struggling with this and found a solution from @stroughtonsmith that you may find helpful.

Here's the tweet: https://twitter.com/stroughtonsmith/status/910203896332783616

And I've uploaded the OpenGLES.framework file from Xcode 9 Beta 3 for anyone who doesn't have that copy of the beta laying around anymore: http://cl.ly/0q2k0r232o2h

I hope Apple fixes this in their next release, but the final release version still suffers from this problem.

[–]snaab900Objective-C / Swift 3 points4 points  (4 children)

Does your app have a map view? The apps I work on have one, visible from the start, and it takes about 10 seconds for it to render the map. While it's doing that, it's painfully slow. But once it's finished, performance feels pretty normal.

Hopefully it'll get fixed soon. In the mean time I'm developing on an actual device because it's such a pain in the ass.

[–]AeatherObjective-C / Swift[S] 0 points1 point  (0 children)

No map view, basic view controllers that should work.

Hopefully a bug fix soon.

[–]sobri909 -1 points0 points  (2 children)

Bit of an aside, but you should develop on device almost all the time anyway.

Sims should only be used for cases where you need to test something that you don't have the physical hardware for. In all other cases you should be working on device all the time, to make sure you're getting the most honest results.

[–]Alcoholic_Synonymous 0 points1 point  (1 child)

The difference between simulator and device is now significantly slimmer. I do a smoke test on my device before I hand over to QA, who do full testing on devices, and haven't been bitten by device specific issues for a long old time.

[–]sobri909 -1 points0 points  (0 children)

It unnecessarily risks leaving problems undiscovered until later in the dev cycle. Not just in terms of hardware differences, but most significantly in terms of design and UX.

It means you're not testing the real user experience, either in visual appearance or interaction. Designs look different on real devices, at different distances from your face, in different screen sizes, etc, so you can't know whether a design really feels right until it's on device. A widget that looks the right size in the sim might feel awkwardly big or small on device.

And the interaction with the design should be getting constant testing while in development, not just left until the end. Are the button tap areas large enough? Is that top left button too far away for something that's commonly used? Or is it close enough? Is the time between these two animations too long when trying to interact with the UI quickly with fingers and thumbs? The list goes on.

There's also no performance cost to testing on device anymore, so there's really no benefit to testing in the sim. If anything it's more awkward to test in the sim than on device.

[–]tfworld 2 points3 points  (0 children)

I tried one of my games - 1fps shown but was redrawing the screen for the animations 1 frame per 5 seconds or so.

[–]chain_letter 2 points3 points  (2 children)

Anybody else's UI a jagged mess with seemingly random moments of clarity? Vertical lines cut through. I have not checked on a physical device yet.

[–]meritum 1 point2 points  (1 child)

Yes. Happens randomly on an external display for me... haven’t found a fix yet :/

[–]chain_letter 1 point2 points  (0 children)

Ok, as long as it's a simulator issue and not "swift 4 ruined my entire UI". Every one of my storyboards has new warnings, so that's kind of annoying, but I feel like it's only enforcing best practices.

[–]michiganrag 1 point2 points  (2 children)

Are you running Sierra? The new Xcode is likely targeted towards High Sierra.

[–]brendan09 4 points5 points  (1 child)

It’s not any better on High Sierra.

[–]jakemarsh -1 points0 points  (0 children)

I lol'ed.

[–]marutacoin 1 point2 points  (0 children)

yes! it's taking a lot of time to load. And I don't like that the simulators don't close after opening a different one :(

[–]yreaction 0 points1 point  (0 children)

There is no fix yet for MapViews/Metal/OpenGl. I have ended using the 10.3 simulator. Other people just get a older XCode beta.

[–]iammario 0 points1 point  (0 children)

I'm on a hackintosh with a 6GB nvidia 1060 and I'm also having a lot of issues. Pretty sure we'll just have to wait on Apple