Search Results + Deep Link

Question

Created Jun ’15

Replies 4

Boosts 0

Participants 3

I'm using CoreSpotlight to index some basic stuff to kick the tires on the new search API. When I click on an item in the search results I would like to take the user to a view deep in the app. I can take the user to a specific view just fine, but it skirts all the navigation that would happen getting to the view, so there is no navigation back out. It's just a standalone view in the app at that point. If you cancel out fo the the search and go directly into the app you're still stuck on that view without any navigation.

If I take a different approach and try `restoreUserActivityState` from the AppDelegate and then follow the chain through kicking off segues, I can see in the log that all the view controllers are hit, but I don't actually navigate through them.

Am I doing something wrong, or is this just a function of being seed 1 and I should file a radar?

Boost

Answer 1

bclark1 OP

Jun ’15

I went ahead and filed a radar after spinning up a very simple app to highlight the desired functionality.

0

Answer 2

DTS Engineer OP

Apple

Jun ’15

I went ahead and filed a radar after spinning up a very simple app to highlight the desired functionality.

Thanks. What was the bug number?

Share and Enjoy
—
Quinn "The Eskimo!"
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1@apple.com"

0

Answer 3

bclark1 OP

Jun ’15

The issue # is 21510308. I also tried presenting the view modally and wuth pushViewController. My thinking was that coming from an app search, maybe the context makes more sense for this view that's buried deep inside the app to be presented as a modal window on top of whatever the current state of the app (in the background) is. Then when you return to the app from the background you haven't totally destroyed the app's state/context with this new view heirarchy. I honestly don't know at this point what the desired way to handle this sort of thing would be. I've updated the ticket with these comments as well.

0

Answer 4

wuudles OP

Aug ’15

Hi,

Did you ever figure this issue out? Are we still responsible for pushing out every viewcontroller in our navigation stack?

Thanks

0