This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.
Closed 10 years ago.
I submitted my app to the App Store yesterday; everything ran as it should. This morning, I upgraded Java, (not sure this has anything to do with the issue, just thought I would mention it). Now, I can't run my app in XCode 4 on any simulator or iPhone!
This is the error I'm getting:
I have looked at all of the Google and SO issues dealing with this; most are involved with OS x. This is only happening on iOS. My iPhone is iOS 5.1, as is the simulator. I have all settings for target OS set to 5.0. I am running XCode 4.4.1. I tried a different app, and it runs, no problems.
Anybody have any suggestions of what else to look at to fix this?
I made a new app, with just bare bones files in it (main.m, info.plist and Prefix.pch). Then I copied the existing files (with the exception of the 3 files above) from the app which wasn't working, and it now runs just fine.
Related
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
Recently, my first iPhone app is approved. I decided to convert it to a universal app, and since it is a basic application I did it easily. I'll resubmit the app today, but I have some concerns about the process.
Idea 1) Creating a new application on itunesconnect. However, current users of my app won't get update notification and there will be 2 different applications. So this idea sounds really stupid
Idea 2) Creating a new version of my current application, this looks good for iPhone side of the app. However, I don't have any iPad app. Defining a new version for a non-existing iPad app sounds weird.
Please correct me if I'm wrong. As I know, one have to debug app on a real device to submit .app file. In my case - universal application, do I have to test app on both iPhone and iPad ?
I really don't know what I should do about it. Please share your ideas. Thanks in advance.
Ideally you should test your universal on both an iPhone and an iPad. If you don't own an iPad but just an iPhone, then if it works well on the iPhone and on the iPad simulator, then you should be OK. But it is still possible for there to be hidden issues. One issue you can have by not testing on a real iPad is making sure all of you iPad specific images and xib files actually work on a real device due to filename case sensitivity. But you can only test on devices that you actually have.
There is no requirement that you test on any device before you can submit the app. Apple has no way to know whether you did or not. Of course it is a really bad idea to only use the simulator for testing since there are so many differences.
As for submitting the app, you must use idea 2. Create an update to your existing app in iTunes Connect. Submit the binary. It will be detected as a universal app. Then you can update the meta data with new iPhone screen shots and iPad screen shots.
This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.
Closed 9 years ago.
I have a tried and tested enterprise iPhone app that's been in heavy use for over a year, and works great. The app makes frequent use of asynchronous NSURLConnectionRequests to fetch data from a server.
I monitor availability of network connectivity using Apple's 'Reachability' sample code. I've always considered the Reachability code to be a bit fragile, but I've had it working solidly for many months - iOS 4.3 onwards.
However, I'm now seeing a problem since upgrading to iOS 6. Seemingly randomly, after a day or two of dipping in and out of the app, I open the app and notice (via the console) that the app is receiving repeated 'network available' notifications from the Reachability class.
If I stop the task (and I mean, properly stop), and relaunch, the problem goes away, and the app behaves normally again.
Of course, this could be down to a subtle issue with my integration of the Reachability code (I've mentioned that I consider it 'fragile'), but I'm wondering if anyone has seen something similar since updating to iOS 6?
I did have a play with the iOS 6 -> Settings -> Developer Settings -> Network Link Conditioner, and it certainly feels like this problem has appeared since then, but it's definitely now turned off, and I've rebooted the device.
Anyone else seeing Reachability issues since updating to iOS 6?
OK, I'm going to assume this problem, that I saw twice, has magically 'gone away'.
If anyone else also sees it, please add to comments.
This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.
Closed 10 years ago.
If we have an application that is currently live on the App Store, compatible with only iPhone devices, and we make an update compatible with both iPhone and iPad devices (Universal) what will happen?
I can think of two possibilities:
the app will not be updated - the updates will require app binaries only for iPhone devices;
there is no problem in adding the iPad support.
I did not see a clear answer in Apple's Guides. There were some discussions in the links below:
iOS Universal App question
iPhone/iPad - Breaking universal into iPhone app only
iOS: Universal App - Release as iPhone only
Does anyone have the answer, with references to Apple Guides? I need to be sure this is possible.
Second answer: it's absolutely not a problem. Those who downloaded your app on an iPad and run in "iPhone simulator" mode on their iPad, will be happily pleased to see they now have a full-fledged app. Users on an iPhone won't notice a difference.
Edit:
Closest I can find in Apple's doc is https://developer.apple.com/library/ios/#documentation/iPhone/Conceptual/iPhoneOSProgrammingGuide/AdvancedAppTricks/AdvancedAppTricks.html
It states that "The following sections highlight the changes you must make to an existing app to ensure that it runs smoothly on any type of device": essentially, update the info.plist and rework your view and view controllers.
Nothing bad will happen if that's what you're asking. Your iPhone users will only notice a difference in the apps file size (if they notice anything at all). And iPad users will notice that your app now takes up their full screen.
There is nothing in the submission or approval process that will stop you from doing this. As long as you've configured everything correctly iPhone-only to universal will be a smooth transition.
This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.
Closed 10 years ago.
I could create Sample.pkpass.
Naturally, I created a Pass Type ID, sample.cer, sample.p12 from iOS Provisioning Portal.
Also I created logo.png, logo#2x.png, pass.json, manifest.json.
Then I created S/MIME signatured, zip compressed.
Then, I tried sample.pkpass on iOS6 Simulator to Safari.
http://localhost/sample/sample.pkpass
I was able to see my Boarding Pass.
Then, I pushed the "Add" Button in the top right part of the screen.
Then, my Boarding Pass has disappeared from the screen.
So, I started Passbook App, but I could not see my Boarding Pass.
Is it because the application is running in Simulator?
This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.
Closed 10 years ago.
First things first, there are many questions similar to this, I know, but I tried all of the answers and they don't seem to be working and I think mine might be a different case (I THINK)!
I recently updated to iOS 5.1 and Xcode 4.3. All my iAds work perfectly on the Simulator, but not on my iPhone. Just to confirm my case, I ran some of my older apps, again, they all work on the simulator but not on the phone. They all call the didFailToReceiveAdWithError method.
Again to double check, I downloaded Apple's iAd Suite and tried to run them, same thing, fine on simulator but not working on the phone.
Although the iAds from my previous apps that are on the appstore seem to be working fine on my phone, I'm not sure what the problem is.
I checked today and it seems to be working fine! I have been researching for the past few days, there are lots of people having the same problem for the last few days(from all over the world). So I guess, it was a problem from Apple's side while giving out iAds.