Following up on this after having another look at what is happening. It's even stranger... and I still don't think it's anything to do with UI3 unless there is some workaround using BroadcastChannel or similar. Posting for curiosity and interest!Thank you very much! I understand my use case here with running ui3 within an iFrame is not general practice
Strangely, cookies are enabled and I don't receive the toast error when logging into ui3 directly, only when running through an iFrame.
I will test the update the and post back here.
I have tested using three methods; Safari.app, Safari WebClips via Profiles and Kiosker.app (A fullscreen iOS app). Webclips and Kiosker.app both allow full screen. Safari.app does not.
If the page with UI3 is displayed within an iFrame using the default Safari.app, everything works as expected. Session Cookies and LocalStorage are retained.
If the page with UI3 is displayed within an iFrame using WebClips or Kiosker.app, Session Cookies and LocalStorage are not retained.
If I load UI3 WITHOUT being within an iFrame, Session Cookies and LocalStorage are retained using all three methods...
I've been attempting to find information as to why this would be the case, but I haven't found ANY discussion on the topic. I don't understand how it can work in Safari.app but as soon as you use safari through a WebClip or similar full-screen app, it doesn't work.
As you can tell this is frying my brain. I don't see why Apple have to make this so difficult! I may just have to chuck the iPad's in the bin and be done with it