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.
Related
We have an app that registers and runs a NetworkExtension (specifically NEPacketTunnelProvider) on both iOS and macOS. This works fine (although not in the iOS simulator, of course, known limitation). However, when the network extension is running, the App Store on macOS/iOS, and TestFlight on iOS, fail to update the app. It looks like they're waiting for the NetworkExtension to terminate, but not actually asking the VPN to disconnect.
We don't want our users to have to think about killing our VPN (which should stay connected whenever possible), but we don't want them to have to think about updates either - they should happen automatically.
Are we missing something? Is there an event we should be listening on to detect that the store is trying to install an app update? Conditions when we should arrange for the VPN to terminate, safe in the knowledge that it will be restarted again after being updated?
Apple had bugs regarding this issue. It was supposed to be ok since iOS 11 (and macOS 10.13 or 10.14), but then users reported that the problem still exists. Several bugs regarding this are still probably open at Apple's bugs reports, but we can't check their status.
You can ask again at their forum, and open another bug regarding this issue.
Probably there's nothing else you can do.
Those are only some of the reports related to this issue:
https://forums.developer.apple.com/message/174708#174708
https://forums.developer.apple.com/thread/92603
https://forums.developer.apple.com/thread/126471
https://forums.developer.apple.com/message/149563#149563
https://forums.developer.apple.com/message/183927#183927
Edit: Someone just posted a question regarding this at Apple's forum. It might be you who posted to question, but maybe it's someone else, so there's another reference:
https://forums.developer.apple.com/thread/128894
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
My last release of application which is 12.8 is rejected by apple saying that i have to add the IPv6 support to the app, I read and reviewed the recommended apple doc named Supporting IPv6 DNS64/NAT64 Networks thoroughly and came to know that already i am using the NSURLConnection class for network connectivity which is mentioned in the same doc, you can see the image from doc under section "Ensuring IPv6 DNS64/NAT64 Compatibility" mentioning the name of NSURLConnection class as a one of recommended class, below is that image
See the Recommended column in above image,
I thought something might be wrong. So, I did the set up of "local IPv6 Wi-Fi network on our Mac" as per the suggestion in the same apple doc under section *"Test for IPv6 DNS64/NAT64 Compatibility Regularly" and I wondered that the app is working like a charm without any issue or warning in debugger related to network connectivity.
I want some suggestions and recommendations from you related to same issue that is i am missing something to add support to IPv6 network connectivity. I have googled around for same thing and found the solutions whatever i have already tested, but still why apple rejected the app that i need to fix.
Any help will be highly appreciated.
Note:
Also not able to get one thing that this is the version 12.8 the app is on app store from last 3 years till the day apple never asked or raised the bug for adding support to IPv6.
Don't believe everything that a reviewer says. You might think that I'm, pardon me for my language, bull-shiting. I am not. They use an iPad to test an app unless it doesn't support such. I got two of my iPhone & iPad apps rejected for the exactly same reason. In the end, they were wrong. One app which keeps track of subway train arrivals connecting a remote server got rejected at the beginning of last Jan. for that reason. But they tested the app at 4 AM according to a screenshot they showed me. No subway is running at that time in my country. The app was working as expected. When I said that to the reviwer through the resolution board, he approved it in a matter of minutes. The other app, which uses the device camera, got rejected for the same reason some 10 days ago. But it doesn't even get on the Internet in the first place. So I was very suspicous. And I appealed. After talking to an appeal board person, it turned out that the app crashed on the iPad because of its support of the camera flash, which the iPad doesn't have.
So what should you do? Talk to the reviewer and ask for more information. So let me say again. Don't believe everything they say when they mention IPv6.
Sometimes apple is really behaves like strange, Nothing was there related to IPv6 support already as i have mentioned in question the network connectivity framework i used "NSURLConnection" supports the IPv6, Still why/how the reviewer raised that issue dont know, It wasted my lot of time, Yesterday i push the app to app store and today it is approved,
Whatever #EI Tomato told was right.
Happy Coding to all!!
I too got faced the same issue. I replied the review team to test the app build again and to provide me crash logs.
And withing a day, my app is approved for distribution.
So if anyone facing the same issue, make sure you test your app against IPv6 WiFi hotspot (Apple source).
If it worked with that environment, reply app review team to review again as it worked with the suggested environment. Most probably your app will get approved after that :)
Hope it might help someone. Upvote if it answered your issue. :)
Thanks to #El Tomato.
TL;DR
[Rejection reason from Apple for my case]
Guideline 2.1 - Performance - App Completeness
We discovered one or more bugs in your app when reviewed on iPad running iOS 11.2 on Wi-Fi connected to an IPv6 network.
Specifically, your app was unresponsive upon launch.
Please see attached screenshots for details.
[My reply to them]
The app (Binary (0.0.xxxxx)) is working fine in our iPad and iPhone running iOS 11.2.1.
... MY DETAILED EXPLANATION ON HOW I TESTED THE APP ...
Can you please review again with the Binary (0.0.xxxxx)?
Is it possible for us to get the crash log, if any?
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.
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.
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.