android / android/nowinandroid

[Bug]: Search empty-state copy reads "explorer" instead of "explore"

Open Beginner friendly
#2,127 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Kotlin
Stars
21.8k
Forks
4.6k
Avg merge
19h 20m
Merged PRs (30d)
2

Description

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Is there a StackOverflow question about this issue?

- [x] I have searched StackOverflow

### What happened?

The empty-results message on the Search screen contains a grammar error. When a
search returns no results, `EmptySearchResultBody` renders:

> Try another search or **explorer** Interests to browse topics

The word "explorer" (a noun) should be "explore" (a verb) to read correctly:

> Try another search or **explore** Interests to browse topics

The faulty text comes from the `feature_search_api_try_another_search` string
resource:

https://github.com/android/nowinandroid/blob/main/feature/search/api/src/main/res/values/strings.xml#L22

```xml
Try another search or explorer

It is assembled into the final sentence in SearchScreen.kt
(EmptySearchResultBody), where the bold "Interests" link and " to browse topics"
are appended:

https://github.com/android/nowinandroid/blob/main/feature/search/impl/src/main/kotlin/com/google/samples/apps/nowinandroid/feature/search/impl/SearchScreen.kt#L231-L253

This is a user-facing copy fix only and does not change app behavior. The existing
SearchScreenTest builds its expected string from the same resource, so it
continues to pass without modification.

### Relevant logcat output

```shell

```

### Code of Conduct

- [x] I agree to follow this project's Code of Conduct

Contributor guide

Open the contributing guide

Research direction

Start with feature/search/api/src/main/res/values/strings.xml and inspect the feature_search_api_try_another_search resource. Check how SearchScreen.kt assembles it in EmptySearchResultBody, then run the existing SearchScreenTest. Done means the empty-results message uses “explore” and the test still passes.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin
Domain
mobile
Issue type
Bug
Difficulty
1/5
Estimated time
Under an hour
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
84/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.