I have deployed a game made in Unity via TestFlight and do not know what to make of this issue - the game runs perfectly on all iPhone 6s and above. On iPhone 6 however and an iPad, it crashes right after the splash screen.
Crash report said initially it had to do with the Metal graphics settings - since (this is another problem) I haven't been able to get the crash reports from the last 2 builds, I am led to think it is still a graphics problem.
I've googled everything and found a few threads saying it was a Unity 5.5.0 problem and also that older devices do not support Metal. So today I updated to Unity 5.5.2f1 and removed Metal from the Graphics settings as
various links have said this has been an issue - https://forum.unity3d.com/threads/crash-on-startup-5-5-0f1-ios-10.446813/
https://issuetracker.unity3d.com/issues/ios-crash-on-presentrenderbuffer-gl-renderbuffer-in-presentgles-when-loading-a-scene-on-iphone-6s
but even with OpenGLES2 and 3 both in the options with Metal removed, it still crashes on just these older devices.
What is happening here? How can I fix this?
I am on the most updated Xcode, etc.
Related
I’m having an issue with games I’ve been developing for iOS using SpriteKit
The issue deals with when the games are deployed through TestFlight and installed on iPhone devices.
On some phones the games will not display correctly. They will appear zoomed in from the center and be clipped at the edges.
Here is a screen shot (taken from an iPhone 6) of what one of the games is supposed to look like:

Here is what the game can look like when it is clipped (screen shot taken from an iPhone X):

I have three iPhone devices I’ve been using for testing:
iPhone 5 running iOS 10.3.3
iPhone 6 running iOS 11.2.1
iPhone 8 running iOS 11.2.1
On all three of these devices the game displays correctly whether I install the game through TestFlight or deploy directly from Xcode.
I also have a tester who has an iPhone 7 Plus running iOS 11, and games installed from TestFlight on his device display correctly as well.
And, of course, the games display fine in all versions of the IOS simulator I’ve used for testing and debugging,
At one point I was able to have temporary access to an iPhone 6s that was having the problem. I could not find any change I could make in SpriteKit that would allow the game to display correctly. Furthermore the View Debugging feature of Xcode indicated everything was fully visible on the screen when it was clearly clipped on the device.
Also, for another user, I was able to get the game to display correctly by having them perform a factory reset of the phone in reinstalling a backup
All of this seems to indicate the problem does not lie with the code for the games, and is rather some physical problem with the phones themselves.
It is also very confusing, and I’m unclear about the cause and how to fix it.
At any rate, this does not appear to be a problem I can solve from my end of things, and I feel that I may need to reach out to Apple for help, only I’m unsure of the best way to go about this.
I don’t know if I could try logging a bug report, as I do not have clear steps on how to reproduce the problem.
I’m wondering if there is anyone I can contact through my developer account that I have that could help to troubleshoot this issue.
What suggestions do people have for dealing with this problem?
On my iPad Mini I can only install up to iOS 9.3, the website looks fine there and on any other device. But colleagues with a new iPad and iOS 11.0.3 have the website only filling about 60% of the screen (both portrait and landscape mode).
see iPod photo a colleague sent me
I made the website for 100% screen width on all devices and never had a problem, worked fine the last 2 years. I would say the website code is sober, the problem comes from iOS. But since I can only check iOS 9.3 or iOS 11, I do not exactly know at which version of iOS the error exactly started.
I can not find any information whatsoever about where this may come from or other people mentioning such a problem. Does iOS11 handle viewport different?
I have simulator screen problems, after installment of last beta, it's happen randomly, when i build any project, usually on 3-4 time, when i hit play. Have to quit Simulator Application, and start it again.
Anyone have same issue ?
Screenshot:
It seems that Metal is the default renderer for the new simulator and some of the older Apple devices do not support it :
Mac computers that support Metal
For example, I have a mid 2011 Mac-mini and had to switch it to OpenGL to get the simulator working (as suggested by #Jeremy Huddleston Sequoia)
I am in the process of testing one of my apps. It works fine on iphone 4s and 5. On iphone 6 however, my tester is reporting that every now and then the app goes to background and he need to relaunch. I would assume it is crashing but he is not able to replicate it (which means there is something really wrong).
Any idea how to go about figuring out what's going on there? All three phones are on ios 9.0.2 all code base is Swift 2.0.
You could add Crashlytics. I included a link below. It works really well. It will send you crash reports with a stack trace.
Crashlytics Link
I have some strange problems of memory management on iOS 5.1.1, I'm NOT using Automatic Reference Counting in the project. Everything works well on iPad 3 5.1 or other devices with 5.1 or lower, this issue happens to two different project (one game and one app). So I think I have coded the right retain/release stuff.
Generally some Objective-C objects are released before it should be. When access it later, app crash. This happens on an iPad 3 LTE, an iPad 3 Wifi and an iPod Touch 4, all running iOS 5.1.1. It never happened on any device running iOS 5.1 or lower. I haven't found any pattern for this. Sometimes even an UIView which is still one the screen get released, if user touches a button, app crashes.
I understand these kind of issue can be debugged with NSZombies. But when I enable NSZombies, this kind of problem never happened.
It looks like a bug of iOS 5.1.1 to me, I'm wondering if it can be fixed on app side.