Thanks for that! I think, for us anyway, that we will be waiting for a final fix. I hate trying to force something to work. I never feel confident that it will continue working or that it didn’t somehow affect something detrimentally that I just haven’t seen, yet. I have conflicting feelings about the length of time this bug has been around and how many people are actually using UE for iOS games. Just bigger guys that are editing the source themselves to get around it? Maybe just those that don’t update as much and aren’t affected? I really wanted to be on Xcode 9 and I feel like that caused most of my headaches. I also wanted to use the newest UE… Seems like I will forever be in the minority here. I don’t want to edit the source code and I want to stay updated. Every time I do, I have an issue. I may just need to jump ship. Can anyone see a reason for us to stay on this engine if our projects are to be released on iOS first? I hope someone can help make the decision a little easier…
Edit: I mean really… I reported this when it was in pre-release over two months ago. Is that what I should feel like is an acceptable timeframe for issue resolution? I am totally grateful for the acknowledgment and the work being done to get it fixed now, but what was the use in me saying something early?