# Entire screen NO LONGER WORKS after screen name changed to contain question mark

**URL:** https://community.thunkable.com/t/entire-screen-no-longer-works-after-screen-name-changed-to-contain-question-mark/62280
**Category:** Questions about Thunkable X
**Tags:** bugs, help
**Created:** [December 27, 2018, 5:08pm UTC](https://community.thunkable.com/t/entire-screen-no-longer-works-after-screen-name-changed-to-contain-question-mark/62280 "2018-12-27T17:08:37Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![AyushS](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/ayushs/32/70663_2.png) [@AyushS](https://community.thunkable.com/u/AyushS)
#### Post date: [December 27, 2018, 5:08pm UTC](https://community.thunkable.com/t/entire-screen-no-longer-works-after-screen-name-changed-to-contain-question-mark/62280/1 "2018-12-27T17:08:37Z")

</div>

I’ve found a big (and quite annoying) issue in Thunkable X. I used to have a screen called ‘Screen 6’. When I changed the screen name to ‘Why Change?’, the screen no longer allows me access to any areas of it - either the to designer or to the blocks (see image below).

 ![Picture1](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/3/b/3b265000ccd8cef187fb452e9b546f9ae9d89fe2.png)  
 ![Picture2](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/d/5/d574efbdf7a4d005f00e7243abc6dbef661dfc4e.png)  
Since I also changed the name of every other screen in my app at the same time, I can only assume that this error occurred because of the question mark in the screen name. I really need access to this screen - does anyone have any ideas on how to fix this?

---

<div class="post-metadata">

### Author: ![AyushS](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/ayushs/32/70663_2.png) [@AyushS](https://community.thunkable.com/u/AyushS)
#### Post date: [December 27, 2018, 5:43pm UTC](https://community.thunkable.com/t/entire-screen-no-longer-works-after-screen-name-changed-to-contain-question-mark/62280/2 "2018-12-27T17:43:01Z")

</div>

With a bit of testing, I’ve found that most other characters are fine in screen names - however both question marks ‘?’ and slashes ‘/,’ stop the screen from working completely.

---

<div class="post-metadata">

### Author: ![paulmw](https://avatars.discourse-cdn.com/v4/letter/p/22d042/32.png) [@paulmw](https://community.thunkable.com/u/paulmw)
#### Post date: [December 27, 2018, 11:35pm UTC](https://community.thunkable.com/t/entire-screen-no-longer-works-after-screen-name-changed-to-contain-question-mark/62280/3 "2018-12-27T23:35:37Z")

</div>

Yes, we need to disable those characters. Don’t add them in any component name.

---

<div class="post-metadata">

### Author: ![ioannis](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/ioannis/32/146956_2.png) [@ioannis](https://community.thunkable.com/u/ioannis)
#### Post date: [November 8, 2024, 11:52am UTC](https://community.thunkable.com/t/entire-screen-no-longer-works-after-screen-name-changed-to-contain-question-mark/62280/4 "2024-11-08T11:52:13Z")

</div>