# Error accessing private space on iOS

**URL:** <https://discuss.huggingface.co/t/error-accessing-private-space-on-ios/54291>\
**Category:** Spaces\
**Created:** [September 10, 2023, 8:34am UTC](https://discuss.huggingface.co/t/error-accessing-private-space-on-ios/54291 "2023-09-10T08:34:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ethanyang1](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/ethanyang1/32/19339_2.png) [@ethanyang1](https://discuss.huggingface.co/u/ethanyang1)\
**Post date:** [September 10, 2023, 8:34am UTC](https://discuss.huggingface.co/t/error-accessing-private-space-on-ios/54291/1 "2023-09-10T08:34:13Z")

</div>

![IMG_1912](https://us1.discourse-cdn.com/hellohellohello/original/3X/2/e/2efbbe73ee1d449bba7886eaf2087a8e2a1590c9.jpeg)

As you can see in the screenshot, I can’t access the private space with my HF account logged in on my iOS chrome. I tried turning off the cross-website tracking in Chrome and Safari, and it still doesn’t work.

Besides making the space public, is there anyway that I can access it on my iPhone? And why it behave like that?

quote from the screenshot in case the pic upload fails:  
" Private spaces may not currently work in

Safari or iOS.

- On MacOS, we suggest switching to another browser temporarily for this Space.
- On iOS, the only workaround currently is to turn off cross-site tracking prevention.

Spaces run on a different domain, and cookies need to be shared with [huggingface.co](http://huggingface.co) for private Spaces to work."

---

<div class="post-metadata">

**Author:** ![FashionStash](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/fashionstash/32/38869_2.png) [@FashionStash](https://discuss.huggingface.co/u/FashionStash)\
**Post date:** [February 7, 2024, 1:07pm UTC](https://discuss.huggingface.co/t/error-accessing-private-space-on-ios/54291/2 "2024-02-07T13:07:57Z")

</div>

Don’t know if the op got the problem fixed, but here is my own experience against that security issue when PRIVATE Space needs to be accessed while being in a Private Browsing mode in browsers.

Because, since the 7, February 2024, there is now the same issue on Huawei Browser (aswell Vivaldi Browser), but instead of the op, all I got was a White page or a broken UI while loading any private Spaces, now, I found hopefully by experiencing some settings that the resolution is easy.

It is not a problem of standard Cookies, it’s an issue related to the Third-party Cookies, so, when you are on a Private Browsing mode in a tab loading a PRIVATE Space, then, just let enabled the Third-party cookies (not the tracking cookies, there is no need to enabled tracking cookies!).

Hope this will helps someone 😉

---

<div class="post-metadata">

**Author:** ![jsid97](https://avatars.discourse-cdn.com/v4/letter/j/3e96dc/32.png) [@jsid97](https://discuss.huggingface.co/u/jsid97)\
**Post date:** [July 19, 2026, 11:39am UTC](https://discuss.huggingface.co/t/error-accessing-private-space-on-ios/54291/3 "2026-07-19T11:39:10Z")

</div>

Found solution - use direct `.hf.space` link for your application.

its usually as - `https://<username>-<appname>.hf.space`

if you are logged in to [huggingface.co](http://huggingface.co) in the same browser, it will automatically use the same credentials. Works for me on safari without having to turn off the “Prevent cross-site tracking” setting globally.
