# Tag with Spaces Not Properly Recognized When Creating a New Note

**URL:** https://community.bear.app/t/tag-with-spaces-not-properly-recognized-when-creating-a-new-note/14802
**Category:** Bear Web
**Created:** [January 31, 2025, 2:17pm UTC](https://community.bear.app/t/tag-with-spaces-not-properly-recognized-when-creating-a-new-note/14802 "2025-01-31T14:17:00Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![ffmich](https://dub1.discourse-cdn.com/flex013/user_avatar/community.bear.app/ffmich/32/1515_2.png) [@ffmich](https://community.bear.app/u/ffmich)
#### Post date: [January 31, 2025, 2:17pm UTC](https://community.bear.app/t/tag-with-spaces-not-properly-recognized-when-creating-a-new-note/14802/1 "2025-01-31T14:17:00Z")

</div>

**Operation system** : Windows 11

**Web Browser** : Chrome Version 132.0.6834.160

* * *

## Bug report

**Steps to Reproduce** :

1. Select a tag with spaces in its name in the sidebar.
2. Create a new note using the new note button.

**Feature Used** : Create New Note

**Observed Behavior** :  
The tag is added to the note, but the last hash character is missing, causing it to not be properly recognized as a valid tag.

**Expected Behavior** :  
When a tag name contains spaces, the hash character at the end should be added correctly to ensure the tag is recognized.

---

<div class="post-metadata">

### Author: ![ffmich](https://dub1.discourse-cdn.com/flex013/user_avatar/community.bear.app/ffmich/32/1515_2.png) [@ffmich](https://community.bear.app/u/ffmich)
#### Post date: [January 31, 2025, 2:32pm UTC](https://community.bear.app/t/tag-with-spaces-not-properly-recognized-when-creating-a-new-note/14802/2 "2025-01-31T14:32:22Z")

</div>

A duplicate tag has also appeared in the sidebar. It remains visible even after refreshing, logging out and back in, or clearing the local cache. However, the duplicate does not appear in the native app version.

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/bear/original/2X/5/544fe65898495cb03f2f774dcf436101df77e62d.png)

---

<div class="post-metadata">

### Author: ![bru](https://dub1.discourse-cdn.com/flex013/user_avatar/community.bear.app/bru/32/179_2.png) [@bru](https://community.bear.app/u/bru)
#### Post date: [January 31, 2025, 4:11pm UTC](https://community.bear.app/t/tag-with-spaces-not-properly-recognized-when-creating-a-new-note/14802/3 "2025-01-31T16:11:31Z")

</div>

Hi, thanks for the bug report.

You’re absolutely right, and it’s easy to replicate. I added it to the list and will fix asap.

---

<div class="post-metadata">

### Author: ![ffmich](https://dub1.discourse-cdn.com/flex013/user_avatar/community.bear.app/ffmich/32/1515_2.png) [@ffmich](https://community.bear.app/u/ffmich)
#### Post date: [February 3, 2025, 8:59am UTC](https://community.bear.app/t/tag-with-spaces-not-properly-recognized-when-creating-a-new-note/14802/4 "2025-02-03T08:59:31Z")

</div>

> A duplicate tag has also appeared in the sidebar. It remains visible even after refreshing, logging out and back in, or clearing the local cache. However, the duplicate does not appear in the native app version.

I think this behaviour is related to tag case

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/bear/original/2X/b/b9d39a6b4c6bca838015a1c5a27bca5b289752a0.png)

---

<div class="post-metadata">

### Author: ![bru](https://dub1.discourse-cdn.com/flex013/user_avatar/community.bear.app/bru/32/179_2.png) [@bru](https://community.bear.app/u/bru)
#### Post date: [February 4, 2025, 10:20am UTC](https://community.bear.app/t/tag-with-spaces-not-properly-recognized-when-creating-a-new-note/14802/5 "2025-02-04T10:20:27Z")

</div>

The issue with tags (with spaces) appearing “truncated” when creating a new note should be solved now on web.bear.app  
The web app is now also doing a better job at avoiding duplicate tags, but it is not yet correcting those that already exist.

---

<div class="post-metadata">

### Author: ![ffmich](https://dub1.discourse-cdn.com/flex013/user_avatar/community.bear.app/ffmich/32/1515_2.png) [@ffmich](https://community.bear.app/u/ffmich)
#### Post date: [February 25, 2025, 9:34am UTC](https://community.bear.app/t/tag-with-spaces-not-properly-recognized-when-creating-a-new-note/14802/6 "2025-02-25T09:34:51Z")

</div>

> The web app is now also doing a better job at avoiding duplicate tags, but it is not yet correcting those that already exist.

Hi bru, any updates or workarounds for fixing duplicate tags that were created before this bug was fixed? I have a few, and it’s a bit frustrating to guess where the notes are actually located.

---

<div class="post-metadata">

### Author: ![bru](https://dub1.discourse-cdn.com/flex013/user_avatar/community.bear.app/bru/32/179_2.png) [@bru](https://community.bear.app/u/bru)
#### Post date: [February 25, 2025, 7:21pm UTC](https://community.bear.app/t/tag-with-spaces-not-properly-recognized-when-creating-a-new-note/14802/7 "2025-02-25T19:21:34Z")

</div>

Probably not what you want to hear, but the quickest way to fix it is by making sure all affected notes have the tag you want to keep (I think removing and readding the tag should do the trick), and then use the native Bear app to delete the duplicates. You make me wonder if it would make sense to have some utilities like this available in Bear Web during the beta testing… we’ll think about it.

---

<div class="post-metadata">

### Author: ![ffmich](https://dub1.discourse-cdn.com/flex013/user_avatar/community.bear.app/ffmich/32/1515_2.png) [@ffmich](https://community.bear.app/u/ffmich)
#### Post date: [February 25, 2025, 9:13pm UTC](https://community.bear.app/t/tag-with-spaces-not-properly-recognized-when-creating-a-new-note/14802/8 "2025-02-25T21:13:13Z")

</div>

Still better than having to deal with duplicates! 😄 By the way, I managed to resolve the top-level duplicates, but I’m still experiencing issues with nested tag duplicates. The notes don’t appear under either of the duplicate tags in the sidebar, even though I can find them via global search. Both tags are present in search results and the note is shown two times in the results list.

Another odd behavior I noticed is that when I create notes in the web interface, depending on the selected tag, the case of some tags in the native app changes from uppercase to lowercase.

I can share a video in DM if it helps.
