# App settings is just spinning

**URL:** <https://community.homey.app/t/app-settings-is-just-spinning/63167>\
**Category:** Developers\
**Tags:** app, homey-pro\
**Created:** [April 30, 2022, 2:49am UTC](https://community.homey.app/t/app-settings-is-just-spinning/63167 "2022-04-30T02:49:11Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![frodeheg](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/frodeheg/32/49010_2.png) [@frodeheg](https://community.homey.app/u/frodeheg)\
**Post date:** [April 30, 2022, 2:49am UTC](https://community.homey.app/t/app-settings-is-just-spinning/63167/1 "2022-04-30T02:49:11Z")

</div>

I have created a settings/index.html file which is an exact copy of the one from the documentation  
( [App Settings - Homey Apps SDK](https://apps.developer.homey.app/advanced/custom-views/app-settings) ) however all I get when clicking the configure app button that appear is a spinning icon that spins forever. Are there more requirements that need to be met than those described on that page?

(I even tried to download the source code for [GitHub - jurgenheine/com.tuya.cloud: Connect homey to the Tuya cloud](https://github.com/jurgenheine/com.tuya.cloud) renamed the app name to mytest and try to run it, even for this one I got the spinning icon - which is odd because it works if I use the app store version)

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [April 30, 2022, 5:54am UTC](https://community.homey.app/t/app-settings-is-just-spinning/63167/2 "2022-04-30T05:54:46Z")

</div>

Works okay(-ish) for me:

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/5/85f3d4b104f7ae724e0a38d8b43503e33fd02907.jpeg)

You can open the settings from [the developer page](https://tools.developer.homey.app/tools/app-settings) and open your browser’s developer console to see if there are any errors being thrown.

---

<div class="post-metadata">

**Author:** ![frodeheg](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/frodeheg/32/49010_2.png) [@frodeheg](https://community.homey.app/u/frodeheg)\
**Post date:** [April 30, 2022, 10:21am UTC](https://community.homey.app/t/app-settings-is-just-spinning/63167/4 "2022-04-30T10:21:44Z")

</div>

Thanks, seems like the developer interface works a bit better than the phone interface, I’m will investigate further later today as I need to leave for an appointment.

---

<div class="post-metadata">

**Author:** ![frodeheg](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/frodeheg/32/49010_2.png) [@frodeheg](https://community.homey.app/u/frodeheg)\
**Post date:** [April 30, 2022, 9:53pm UTC](https://community.homey.app/t/app-settings-is-just-spinning/63167/5 "2022-04-30T21:53:27Z")

</div>

So the difference between my phone interface and the developer tools interface is that on my phone I see a white page with a spinning icon in the middle while the developer tools interface gives me the correct index.html setup page shown except that it is grayed out (disabled) with a spinning icon in the middle. So I get no progress in both places. I just wonder, is this the behavior that is expected if Homey.ready(); is not called? I wonder if the signal is not getting through.

---

<div class="post-metadata">

**Author:** ![frodeheg](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/frodeheg/32/49010_2.png) [@frodeheg](https://community.homey.app/u/frodeheg)\
**Post date:** [April 30, 2022, 10:38pm UTC](https://community.homey.app/t/app-settings-is-just-spinning/63167/6 "2022-04-30T22:38:20Z")

</div>

Ok, I figured it out.  
So, it turns out that if I copy paste the example code from firefox in Ubuntu then I get one invisible character copied between each paragraph. Not sure what this invisible character is but it may be related to LF + CR(?). In any case, this invisible character will make the javascript code unprocessable, so if I just delete this invisible character then the javascript will be able to execute and as such call Homey.ready()

So I guess this is more of a firefox + linux or maybe just linux problem…
