# Titanium.Network

On iOS, the cookie will override an existing cookie with the same name, domain and path, if any. The cookie's expiryDate property must be a date later than the creating date, otherwise the cookie will not persist in the cookie storage. On Android, any existing cookie with the same domain and name will be replaced with the new cookie. This is a bug in BasicCookieStore because based on RFC6265, an existing cookie can be evicted and replaced only when it has the same cookie-name, domain-value and path-value with the new cookie.

On Android, Titanium.UI.WebView uses the system cookie store. Any existing cookie with the same domain, path and name will be replaced with the new cookie.

Properties are supplied as a dictionary. Each key-value pair in the object is applied to the proxy such that myproxy[key] = value.

On iOS, this also escapes the following characters, which are allowed in a URL but may not be allowed or desirable inside a path component:

!*'();:@+$,/?%#[]=&

The domain matching and path matching follow RFC6265. If name is null, return all the cookies with the domain and path matched.

The domain matching follows RFC6265.

On Android, Titanium.UI.WebView uses the system cookie store. The domain matching and path matching follow RFC6265. If name is null, return all the cookies with the domain and path matched. The returned cookies only have their name and value properties returned.

Call this method to allow remote push notifications. It should usually be called on application start.

iOS Notes: Before calling this method, the application needs to call the registerUserNotificationSettings method and pass it the notification types to use. Setting the notification types with this method will have no effect and throws a warning.

Android Notes: Make sure to also add the <uses-permission android:name="android.permission.POST_NOTIFICATIONS"/> permission in the <manifest> tag of your tiapp.xml. Example:

const win = Ti.UI.createWindow();
win.addEventListener("open", function() {
  console.log("Is enabled", Ti.Network.remoteNotificationsEnabled);

  Ti.Network.registerForPushNotifications({
    success: (e) => {
      console.log("success", e);
    },
    error: (e) => {
       console.log("error", e);
    }
  });
});
win.open();

The permission request will only be shown twice. After that it won't show up again and the user has to go to the app permissions to enable it.

On Android, Titanium.UI.WebView uses the system cookie store.

Multiple listeners can be registered for the same event, so the callback parameter is used to determine which listener to remove.

When adding a listener, you must save a reference to the callback function in order to remove the listener later:

var listener = function() { Ti.API.info("Event listener called."); }
window.addEventListener('click', listener);

To remove the listener, pass in a reference to the callback function:

window.removeEventListener('click', listener);

The domain matching follows RFC6265.

On Android, Titanium.UI.WebView uses the system cookie store.

Per Apple's documentation, it is rarely necessary to call this method. See: unregisterForRemoteNotifications in the UIApplication Class Reference

For example, calling this method would be required if a new version of your application no longer supports push notifications.