One of my apps recently were rejected due to not running on iPad in compatibility mode. However, I fixed the problem and they load fine in Compatibility mode on iOS6 on my iPad simulator through xcode. So I reuploaded my app and about 7 hours later it already went into review and got rejected for the same reason, they said that the app crashed on iPad.
So, how do I read specifically the .crash file returned by apple?
Related
I have 2 Apps in the AppStore since iOS 10 and both apps have iPad, iMessage Stickers and Apple Watch apps. They have been working great up until the release of all the new Apple software, Xcode 9, iOS 11 & WatchOS 4.
The apps did not need anything changed for Swift 4 but my first error occurred when I try and submit my archived apps to the AppStore. I get error messages referencing missing app icons which isn’t the case. I found a workaround here on stack overflow by editing the archived files Plist and then submit to AppStore and this works but is inconvenient and obviously I shouldn’t have to do this.
My next problem is now when I go to use the apps on my Apple Watch they crash every time on startup. I don’t have any crashes when it’s run on the simulator so I’m thinking the only thing I’ve modified since testing is the Plist of the archive.
Here is the link to the fix I was using to allow me to successfully upload my apps.
AppStore Upload Temporary Fix
Apple has rejected my app due to the following reasons:
1) We found that your app crashed on iPhone 5 running iOS 6.0.1, which is not in compliance with the App Store Review Guidelines.
2) Your app crashed on launch on both Wi-Fi and cellular networks.
I'm running Xcode version 4.3.2, which isn't compatible with iPhone 5 i think, so i'm suggesting that my app rejected because i tested it in old Xcode version which doesn't support iPhone 5 architecture, right?
for the second reason Apple rejected my app i think because even my app doesn't use internet connection through the code i have to check the availability of internet connection on launch by taking advantage of Reachability library, right?
note that i tested my app on both simulator and actual devices all running iOS 5.1.1 and lower not iOS 6
any help? thanks on advance !
Simple:
Build, Debug, and Test using a more recent version of Xcode, using the Simulator and Devices (with iOS 6)
Remove the issues cited, and any other crashing issues
Re-Submit
Reachability is not necessary. Your app will need to to handle errors gracefully (not crash/explode/leak/fall into a weird state).
I have an app in app store.
After updating my app, it crashes right after it launches. (see a black screen for less than a second and then it is like i pressed the home button.)
I tested it on my iphone attached to xcode and it is okay in debug mode.
i tested it in 5.1.0 and it is okay.
when i download it from app store it crashes.
any one had troubles with 5.1.1 ?
Apple acknowledges that there is a problem with the newly uploaded binaries in the AppStore. By the moment app developers are recommended to hold off on submitting applications to the App Store until this issue is resolved. Here is a link.
I am working on a universal application where I am stuck at one point. I was able to successfully launch my application both on iPhone and iPad but since 2-3 days, I am not able to launch my application on neither iPhone nor iPhone simulator but it runs smoothly on iPad/iPad simulator.
Also when I run my app choosing iPhone device it shows message like Running the App on iPhone simulator but I am not able to see any effect on my simulator. I am using Xcode 4.2.1 and I guess the issue is pertains to the same.
I don't know whether it is a solution or not but got a way out by reinstalling the iOS Simulator.
I have faced same problem. This probably happens when you replace the application with the newScheme/EditScheme by mistake.
Just carefully check when you run your application is there your application name appear. This will be immediate left at where you choose iPhone simulator or iPad simulator version.
I have an iPhone App published for a while, developed under the SDK3, and everything works great. Some weeks ago, when Apple released the SDK4 I made some changes to my app to support multitasking (it plays audio in the background).
In my simulator and my device (iPhone 3GS iOS4) the app runs great, there is no problem at all. But, now when I submit the update, a lot of users are contacting me because they say that the app freezes on the splash screen and after waiting about 40-60 seconds, it crashes.
By asking to the users, I have determinate that the problem is only in those devices that haves iOS4 (iPhone 3Gs and 4G).
I tested the app over and over in my simulator and my device but it never happens to me!! Some one have any idea or information about this?
I will really appreciate it. Thanks.
After search for the crashes, and try over and over, I can't reproduce the bug on
my devices. So, I decide to start reading at the Apple Developer Forums and I
found a thread where my suspicions are affirmed: this problem is caused by an internal
iOS4 bug.
"There's a bug in the App Store's code signing process. Talk to DTS: they can
help you with the workaround. Mention rdar://7909951."
"...but it should be the cause of nearly all "failed to launch in time" inside
libobjc:_mapStrHash..." (This appears in some of my app crashes)
Here is the link to the post: failed to launch in time in iOS4
There is no certain solution, but some suggest that a start is changing from arm6 to arm7 and try.
You can try changing some code in the app for producing a different binary and submit it again.
I hope it can help anyone else.
Check the crash report on itunesconnect.apple.com
iPhone 3G also supports iOS 4, except it "doesn't support multitasking" (presumably due to lack of RAM?). If you're only seeing crashes on the 3GS and 4, then that might be the issue.
Default.png is shown on launch, but it's also shown on the foreground when the OS didn't manage to get a screenshot while backgrounding, or for various other reasons (e.g. your app was launched with openURL, so the UI is likely to be different).