ionic app rejected from app store - ios

I'm attempting to upload my first app to the appstore. It's built with ionic. Repo is here: https://github.com/irthos/rogo-app and is live here: https://irthos.github.io/rogo-app/
The email from apple said they tried it on a iPhone 4s:
May 17, 2015 at 4:06 PM From Apple
2.1 - Apps that crash will be rejected
2.1 Details
We were unable to review your app, as it crashed on launch on the
following device(s):
iPhone 5S running iOS 8.3
We have attached detailed crash logs to help troubleshoot this issue.
Finally, here's the ips log from Apple: http://a1837.phobos.apple.com/us/r30/Purple7/v4/30/c5/04/30c50456-c2c0-1148-8d60-f36fbb11ae26/temp..jwnucdaf.ips?downloadKey3=1432258092_57a71add8c408ca7ec7a907881e7a613
Thanks for any insight to this. I'll also post an issue on ionic's repo in case it's a bug.

Well, the crucial line is:
setValue:forUndefinedKey:]: this class is not key value coding-compliant for the key view.'
Typically I would see this on a ViewController in a Storyboard where I changed the names of one of my IBOutlets in code but did not go and re-map the ViewController outlets on the storyboard.
Since I don't know what "ionic" is, I have no idea whether you are even using storyboards (or XIB's) or what tools you use but I would look at something UI related.
Just a guess though.

Related

Installed App from TestFlight crashes due to alleged UISearchDisplayController

I implemented Dark Mode with the current beta version of Xcode in a relatively old app. I uploaded these to TestFlight for my testers. However, this crashes immediately for anyone who has the public beta of iOS 13.
I've integrated Crashlytics into the app, and the cause of these crashes is as follows:
UISearchDisplayController is no longer supported when using this version of iOS. Please migrate your application to UISearchController.
All UISearchDisplayController instances have already been replaced by the UISearchController. The app doesn't use the UISearchDisplayController anymore. There is no longer any links to the UISearchDisplayController. Nevertheless, these crashes continue to occur, but only from the installations of TestFlight.
If the app is installed directly with Xcode as a "Debug" or "Release" on an iPhone with the public beta, the crash does not occur.
Does anyone have a solution for this problem?
After receiving the same error and finding no references to UISearchDisplayController across our app, we realized we needed to search for and replace searchDisplayController from within one of our storyboards. That corrected the issue after resubmitting a beta to TestFlight.
It was working on simulator but all beta tester claimed it crashed. The problem was in story board. Search for these in your views.
*** Terminating app due to uncaught exception 'NSGenericException', reason: 'UISearchDisplayController is no longer supported when linking against this version of iOS. Please migrate your application to UISearchController.'
Successfully Runs locally, but crashed on testFlight app.
Fix:
I found UISearchDisplayController which stuck in one of the storyboard and wasn't used anymore. Search for the searchDisplayController directly into sourcecode of the storyboard and just removed it.

My CN1 app crash on startup

Since today I can't run a CN1 debug the app on my iPhone 4 (iOS 9.3.5). It crashes on startup.
I've made only minor changes:
Add a button which uses execute(URL) to open a URL.
and I've got this exception:
Library not loaded
/System/Library/Frameworks/UserNorifications.framework/UserNotifications
[...]
Reason: image not found.
Can you help me, please?
That's probably a regression due to changes that went in to implement https://github.com/codenameone/CodenameOne/issues/2208
It's probably due to this commit: https://github.com/codenameone/CodenameOne/commit/a3a70fadd7dbef661351d11dc35683be3d828eda
Can you please file an issue to keep track on this?
We're looking into it.

Error "Class VCWeakObjectHolder is implemented in both..." is crashing debug sessions

I am getting following error all the time in my iOS app:
objc[56232]: Class VCWeakObjectHolder is implemented in both
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot/System/Library/PrivateFrameworks/AVConference.framework/Frameworks/ViceroyTrace.framework/ViceroyTrace
(0x12fe564d0) and
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot/System/Library/PrivateFrameworks/AVConference.framework/AVConference
(0x12ef82e38). One of the two will be used. Which one is undefined.
The app itself runs fine but the debugger will not attach to the device process. The simulator does attach but the app crashes immediately after a breakpoint is hit.
I am running out of ideas on how to deal with it. Any help would be greatly appreciated.
Simulator -> Hardware -> Erase all content and Settings...Works for me.
I submitted bug #43377301 to https://bugreport.apple.com/
Debug messages should be off in Apple frameworks (Class VCWeakObjectHolder)
I'm currently fixing bugs in an old code base and I have no idea what this internal Apple "warning" means.
It shouldn't be displayed to the 3rd party developer. I'm using CoreBluetooth and Objective-C.

App began to crash on iOS 9.1 Beta 2

The application began to crash when installing on iOS 9.1 Beta 2. Exactly same binary (downloaded from hudson link) behaves so:
It did not crash on iOS 9.0 and iOS 9.0.1
It did not crash on either iOS 8
I have extracted the crash log, crash happens inside the call to [[NSBundle mainBundle] loadNibNamed:#"NameOfView" owner:self options:nil];. The crash itself is NSUnknownKeyException:
*** Terminating app due to uncaught exception 'NSUnknownKeyException', reason: '[< NameOfView: 0x1446a6ea0> setValue:forUndefinedKey:]: this class is not key value coding-compliant for the key .'
So far i see weird key '.' which nib loading mechanism tries to set on my class, and obviously, such is not present in nib. And this looks extraweird even more, due to iOS 9.1 beta 2 is the only version with this behaviour. Moreover, building app with XCode 7 from on same git revision gives no success crashing app - it works as expected. Has anybody experienced such behaviour after trying your release versions on iOS 9.0.1 beta 2? Want to have some feedbacks of SO community before file a bug to radar. Appreciate your help, guys.
P.S. I'd like to emphasize that the issue reproduces only on that particular binary. Building it again from the same sources in XCode 7 doesn't produce a crash. So please, don't suggest how to debug such kind of problem, how to set exception breakpoint etc.
EDIT
Since 9.1 release, it's no more reproducible.
As stated in comment to original question, there's no solution and no response on bug yet.
The openradar link: http://openradar.appspot.com/radar?id=6294934587965440
I'll be posting an updates here after the 9.1 release.
There are some empiric ways to come up with solution:
Override KVC setter setValue:forKey: and forbid empty string
key.
Use always the latest stable SDK to build.
But again, no actual response from Apple neither.
EDIT Since 9.1 release, it's no more reproducible.

Xcode 7 beta 4 - Crashes on UI recording

While trying to do UI recording for my UI tests, the app crashed after 1 event that was not recorded. Looking into the crash report, I found this error:
UNCAUGHT EXCEPTION (NSInternalInconsistencyException): ancestorFinder is not being processed by childNodeFinders
Anyone also getting this and maybe someone knows a fix for this?
At the moment, this seems a bug related to the absence of accessibility identifier on the item used to generate the event.
If your UI is created using the Interface Builder, Andy's answer is certainly relevant.
If, like me, your are creating your UI object programmatically, you can set a value to the accessibilityIdentifier property of your UI element (e.g. a UIButton).
Unfortunately that's just life with beta software, did you try reinstalling Xcode 7 beta 4.
If it still doesn't work, might be a beta thing.
Solution
Look forward to Xcode 7 beta 5
This is a bug that Apple are aware of but require more details to debug it. Please see this link for info:
https://forums.developer.apple.com/thread/10623

Resources