I am using Apple Reachability v3.0.
Apple rejected my app because this is not working in iOS 7.0.3 on iPhone 5s.
We found that your app exhibited one or more bugs, when reviewed on iPhone 5s running iOS 7.0.3, on both Wi-Fi and cellular networks, which is not in compliance with the App Store Review Guidelines.
Specifically, we found that your app displays the error message: "No Internet Connection" after the user login.
this error message is not displayed on a device running iOS7.
Please help me with the solution.
Solved it!
Instead of using Reachability provided by Apple, I used AFNetworking Reachability.
Now, it works fine.
It sounds like Apple rejected your app for being broken in some way.
Try following up with them asking for more information about the problems they ran into. They'll probably be able to provide some information about what they were seeing. Fix those problems and resubmit and you should be all good to go.
You can also use NSURLSession for maintaining the network connection. This is introduced in iOS 7 so its easy to manage your checks and tasks.
Related
I have an app which uses a login screen to login the users. I have just submited the app for review at Apple and recieved the following rejection message.
"During our review, we found that your app displays no content when reviewed on iPhone and iPad running iOS 14.6 on WiFI. While we cannot provide technical assistance with the reported issues, we have put together the following resources which discuss common issues seen in apps during review.
Review device details:
Device type: iPhone and iPad
OS version: iOS 14.6
Next Steps
Please run your app on a device to reproduce the issues, then revise and submit your app for review. If at first you're unable to reproduce the issue, try the following:
For new apps, uninstall all previous versions of your app from a device, then install and follow the steps to reproduce.
For app updates, install the new version as an update to the previous version, then follow the steps to reproduce.
If we misunderstood the intended behavior of your app, please reply to this message in Resolution Center to provide information on how these features were intended to work."
I have followed everything they said. I tested on both a physical device and simulator. I use wifi, i have the same iOS version and tested it on both iPad and iPhone. I do not get a blank screen. I cannot seem to reproduce this. Has anyone ever faced this problem and how can I resolve this? I am using an Express app as the backend that is hosted on AWS.
I can also mention that the connection is over HTTP and not HTTPS which is said to be ok if you only add a string to the info.plist file. But maybe its related to that?
My Info.plist on iOS:
I have uploaded my app to Apple store. I am using iOS 10.2. After upload, I got a rejection message:
Your app crashes on iPad and iPhone running iOS 10.2 connected to an IPv6 network when we:
Specifically, we found that the app crashes after sending messages on Wi-Fi
How can I solve this?
If you app contains webservices and you have implemented NSURConnection then please convert all NSURLConnection to NSURLSession . .
My App got rejected for the same reason, but it was not the issue. The reason my app got rejected because it got crashed on login button click.
It was working when i compile and run with xcode (ie xcode 8.2.1) but apple said it was crashing.
So i tried running it in release mode because we usually run our app in debug mode when we run on xcode.
from
to
And my App crashed when i ran it on release mode and i found the bug, it happened when the compiler tried to optimise a decryption function.
I think there is some issue with the new llvm 8.0 compiler.
Now my App got even approved by AppStore.
The answer is fairly simple, you're going to have to try and reproduce the crash and fix it.
Apple won't let apps into the App Store of which it finds crashes for. I'd recommend finding a friend/family member who has an IPv6 enabled network (if you can't enable it yourself) and attempting to use your app in various conditions under that network.
The App Review network, like the networks deployed by service providers, does support IPv6-to-IPv6 connectivity. Thus, if your server supports IPv6, your app will talk to it directly, without going through the NAT64 translator.
Please check your link is support ipv6 or not use this LINK
and read more
Just add a CDN (Example: Cloudflare) to your domain, change nameservers accordingly and make sure IPv6 compatibility feature is turned ON. This worked for me
I've a problem with IPV6.
Apple reject my app with error:
We discovered one or more bugs in your app when reviewed on iPad and iPhone running iOS 10.0.2 on Wi-Fi connected to an IPv6 network.
Specifically, your app stayed static at the launch screen and there was no further content loaded.
We've attached screenshot(s) for your reference.
But my sever is not supporting IPV6. I use library AFNetworking to connect server. Please help me some solution? Thank you for any support!
I got this error a month ago, then I updated AFNetworking to last version and Apple's Reachability class too, my problem solved, you can try this, I hope it'll work.
Please see this link:
Supporting IPv6 DNS64/NAT64 Networks
This may be helpful:
Transitioning to IPv6-only networks
It covers the topic you described.
My application is been reject by apple . They have message me that
During review, your app crashed on iPad running iOS 9.2.1 and iPhone running iOS 9.2.1 when we:
-Launch app
-Logged in
This occurred when your app was used:
- Offline
- On Wi-Fi
- On cellular network
But it is working fine on simulator and ios devices .
It dont know whats wrong with it .
Here are the crash reports
http://a697.phobos.apple.com/us/r30/Purple69/v4/f4/65/c0/f465c0c1-0261-7798-dca8-9b48c0de869a/temp..lfhkdwhz.crash?downloadKey3=1454075117_e097b43bf35613b18c897f3917dcd353
http://a401.phobos.apple.com/us/r30/Purple49/v4/cb/6c/c8/cb6cc858-d47a-aba8-0a7c-1bf304c4c56f/temp..rhzbnjqi.crash?downloadKey3=1454075117_556853386b65ca6d799acd6f6ce64fac
I dont know where are these crashes and how to resolve them ?
If you have read Apple instructions, they said its crashed on offline test. That means while there is no internet connection there is not available.
Simply follow these steps:
Check Internet Reachability at every place in the app where its used
After adding it test App on the device in which Apple testers found crash to make sure its working now.
Add appropriate alert messages for no internet connection
Note:
Thing is Simulator may not give you crash all time. Its best to test on real device before submit App for review
Hope it will help for you.
My app uses BLE (Bluetooth 4) to connect to a physical peripheral.
My users and I have repeatedly encountered a bug where, at some point, the app stops connecting to the peripheral - you can see an indication that the BLE peripheral is discovered and the connection was established, but then few seconds after, the connection is dropped.
Things go back to normal only after restarting the iDevice.
I’ve done a very long work on checking it and researched this issue thoroughly, until I got to the conclusion that this must be a bug in iOS (tested with 7.1, but probably occurs on 8.0 as well).
My tests and findings:
Occurs with every BLE supporting iDevice.
Occurs with both my own BLE peripheral and with other 3rd party BLE products, both known to work perfectly in normal cases.
It can sometimes work well for even 50 launches, but then eventually it’ll fail.
Network & factory settings reset did not help.
Tested and occurred with various applications: ##
My own app.
Clean new Xcode project that’s only scanning for peripherals and trying to connect to the first and only discovered peripheral.
Apple’s BLE example app: Health Thermometer (with relevant modifications since I don’t have this particular peripheral).
3rd party apps, including the generic LightBlue.
Important note: Every one of the options above worked perfectly for a while (multiple launches), at some point suddenly stopped and then worked again after a restart of the device.
The connection procedure seems to fail when trying to discover the peripheral’s services - i.e. it gets discovered and connected normally, but when initiating discovery of services, it stops responding (didDiscoverServices isn't called).
I have of course tried many approaches found online with no luck.
Can anyone shed some light on this problem?
Is it a known issue?
Was it fixed in a recent iOS update?
Is it going to be fixed?
You can imagine the negative affect such an issue has on my users’ experience, as BLE connection is essential to the product.
I'll appreciate your advice and suggestions on how to solve it.
Thanks!
Update:
Apple responded to my tech support request:
Bottom line(s):
They said they had fixed some BLE related bugs in iOS 8 and urging us to test if it still happens in iOS 8.
They said to start with that and if not, try to diagnose the problem with a utility app they provide.
So far for me it didn't happen with iOS 8, but on the other hand I can see posts about other Bluetooth issues, that are not necessarily related but who knows.
Full answer:
I’m responding to your finding that you and your customers find that
after some point of use, iOS BLE fails to maintain a connection. You
indicate that the problem was identified with iOS 7.1. There have been
issue regarding iOS BLE which have been reported and have been fixed
with iOS 8.0. To best determine whether your issue has been addressed,
of course the simplest means would be to install iOS 8 and to see if
the issue can be replicated. However, as you report that you can
replicate the problem on your deivce with iOS 7.1 the first thing
would be to obtain the Bluetooth Server profile, install it to your
deivce, replicate the problem, then obtain a BLE Server log when the
problem occurs. The profile will have the BLE server report additional
logging details which can help to report issues that the server
encounters. We can see if the issue is one which has been reported
previously. Something to consider is that for all new bug report
issues, Core Bluetooth engineering is requesting that all issues be
regressed with the currently shipping version of iOS - that is 8.0.
For customers with iOS 7.x, there will be no more iOS 7 updates - all
software fixes and bug fixes will be with iOS 8. For this reason, only
issues which are reported with iOS 8 will be investigated. You can
obtain the BLE server profile from the Apple Developer bug report web
page https://developer.apple.com/bug-reporting/ios/bluetooth/. The
instructions for installing the profile and capturing the log, are
presented on the web page. If you capture a log with iOS 7.x, you can
send it to me for review. However, this will be somewhat of an
academic exercise - to know if iOS solves the issue, or whether it
persists, we will need to see if the issue occurs under iOS 8.
Something to keep in mind, once you update a device to iOS 8, you will
not be able to restore it to a previous version. I’m happy to
review your results. If however, the problem persists under iOS 8,
it’s best to submit a bug report to get Core Bluetooth engineering’s
attention on this matter. You can submit a bug report using the Apple
Developer bug report web page. - http://bugreport.apple.com
So it looks like the problem is solved with recent iOS update (either 8.0 or 8.1).