Tutorial: Storing cookies - Maintaining user login on Android/iOS

Mobile Apps
6

@Evaldas Hello!

The problem about third party cookies (You can see the discuss here: Third party cookie will be blocked) is the next one:
What google is going to cut are the cookies that are sended from domain1.com to domain2.com where in this particulary case it is domain1.com to localhost which has the same logic.

But you can set the host on the app:

// Server object contains port and url configurations
  "server": {
    // You can make the app to load an external url (i.e. to live reload)
    "url": "http://192.168.1.33:8100",
    // You can configure the local hostname, but it's recommended to keep localhost
    // as it allows to run web APIs that require a secure context such as
    // navigator.geolocation and MediaDevices.getUserMedia.

So if your backend is on domain.com then this:

    "server": {
    "androidScheme": "https",
    "hostname": "domain.com"
  }

Will work, or at least, the error disappears.
This workaround is what many people are using, so I guess it’s okay.

It’s still not clear, I can’t see a certain topic about this anywhere.
Will try another search tomorrow.

2 Likes