# Emualator Not show in IDX

**URL:** <https://community.firebasestudio.dev/t/emualator-not-show-in-idx/9879>\
**Category:** General\
**Created:** [March 22, 2025, 1:31pm UTC](https://community.firebasestudio.dev/t/emualator-not-show-in-idx/9879 "2025-03-22T13:31:51Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![klassic](https://sea2.discourse-cdn.com/flex002/user_avatar/community.firebasestudio.dev/klassic/32/2005_2.png) [@klassic](https://community.firebasestudio.dev/u/klassic)\
**Post date:** [March 22, 2025, 1:31pm UTC](https://community.firebasestudio.dev/t/emualator-not-show-in-idx/9879/1 "2025-03-22T13:31:51Z")

</div>

I was working on a project and all of a sudden this happend

![image](https://us1.discourse-cdn.com/flex002/uploads/idxcommunity/original/2X/0/0c6917632f50ed3673d993846dc019e2791a1625.png)

@Idx

---

<div class="post-metadata">

**Author:** ![kirupa](https://sea2.discourse-cdn.com/flex002/user_avatar/community.firebasestudio.dev/kirupa/32/4_2.png) [@kirupa](https://community.firebasestudio.dev/u/kirupa)\
**Post date:** [March 23, 2025, 5:56pm UTC](https://community.firebasestudio.dev/t/emualator-not-show-in-idx/9879/2 "2025-03-23T17:56:47Z")

</div>

If you restart your workspace, does this error go away?

---

<div class="post-metadata">

**Author:** ![klassic](https://sea2.discourse-cdn.com/flex002/user_avatar/community.firebasestudio.dev/klassic/32/2005_2.png) [@klassic](https://community.firebasestudio.dev/u/klassic)\
**Post date:** [March 23, 2025, 6:11pm UTC](https://community.firebasestudio.dev/t/emualator-not-show-in-idx/9879/3 "2025-03-23T18:11:31Z")

</div>

Yeah..it’s working now.. Thanks @kirupa

---

<div class="post-metadata">

**Author:** ![kirupa](https://sea2.discourse-cdn.com/flex002/user_avatar/community.firebasestudio.dev/kirupa/32/4_2.png) [@kirupa](https://community.firebasestudio.dev/u/kirupa)\
**Post date:** [March 23, 2025, 6:12pm UTC](https://community.firebasestudio.dev/t/emualator-not-show-in-idx/9879/4 "2025-03-23T18:12:49Z")

</div>

Glad that worked. We’ll continue to improve our story here to ensure you (and others) don’t get caught with this bug in the future.
