Rejection - MKLocalSearchCompleter without results

Good day fellows


We had our app rejected 2 times recently because one of our app features, that need to provide a city and we've been using

MKLocalSearchCompleter since 2 years ago without any issue.


The app review team claims that this search table does not show any results for them and we're not able to reproduce it. We are short of ideas:


- We use plain MKLocaleSearchCompleter with a query string as in documentation, nothing more involved.

- We've tested almost all the simulators/devices with any kind of setup (Region, Language, etc).

- From what I see they're using a VPN, we've try to reproduce in that situation (also with other network limitations, location disabled, etc, etc) but still works fine for us.


Do you guys have any idea how to reproduce this situation?

How does you app behave if no match is found ?

MKLocalSearchCompleter is just for auto completion, so it is an optional help.


If no match found, what do you do when user validates its search request ?

Just “No results” That is what they see, but even using “Paris” they get no results at all or any direction. It is like the mapkit domain is blocked for them (I know how it sounds)

I'm having the same issue—submitted an app for review a few days ago and it was also rejected due to no results being returned by my implementation of MKLocalSearchCompleter. I haven't been able to reproduce the bug that App Store Review has been describing on any devices or simulators, even with location services turned off.


EDIT: It appears as though App Store Review is experiencing a "The request timed out." error. I submitted a new binary that displays the MKLocalSearchCompleter's errors in an alert.

Having the same issue here. We have a city field that needs to be entered at signup and started getting rejected for this not working. Couldn't figure out why so I added an error handler and they sent another rejection with a screenshot that reads, "The request timed out."


This only started happening June 3rd for us. I've tried reproducing it, but haven't had any luck. I've noticed it started happening when our reviewers appear to be in a different country. Our app was previously reviewed during local business hours in the U.S., but now it's always between 1-4am. I'm wondering if MKLocalSearchCompleter isn't accessible in certain regions? Not sure what else it could be?
Have either of you been able to resolve this issue? It's delaying our app release.

Sadly no. The app suddenly got approved.
But now we have exactly the same rejection reason. We are unable to reproduce this.
We started seeing this about six to eight weeks ago, and it severely delayed our release. We were able to solve it be submitting screencasts of the app working correctly in a live environment.

Then we were good for a couple of releases, until it recently started happening to them again, and as a result delaying our release again.

Have anyone been able to solve this?
Hello, did you find a solution for the problem? I have the same issue.
The localSearchCompleter works perfectly fine in all my devices, but not in the iPad of my app reviewer.
Having the same issue. During App Review, MKLocalSearchCompleter throws a "The request timed out" error and returns no results. Works perfectly on every simulator and real device I've tested on. Frustrating to say the least – has anyone figured out a solution for this?
Wanted to give an update on my situation -- after submitting an appeal to the App Review Board, the app was again rejected, but then was randomly put back into review and approved a few hours later. Very odd...but whatever works I suppose.
Rejection - MKLocalSearchCompleter without results
 
 
Q