@maccesar/titools 4.4.0 → 4.5.0

package/skills/ti-api/references/api-modules-map.md

@@ -110,21 +110,15 @@
 > Extends Ti.Proxy
 > Platforms: both
 
-The `Annotation` object gives you low-level control over annotations that can be added to
-[map view](Modules.Map.View). An annotation must have its `latitude` and `longitude`
-properties set to appear on a map.
+The `Annotation` object gives you low-level control over annotations that can be added to [map view](Modules.Map.View). An annotation must have its `latitude` and `longitude` properties set to appear on a map.
 
-Use the <Modules.Map.createAnnotation> method to create an annotation.  Starting with Alloy
-1.4.0, use the **`<Annotation>`** Alloy element to define one in XML markup.
+Use the <Modules.Map.createAnnotation> method to create an annotation.  Starting with Alloy 1.4.0, use the **`<Annotation>`** Alloy element to define one in XML markup.
 
-An annotation can also have a title, a subtitle, and two inset buttons or views on the left
-and right side of the title. All of these items are optional.
+An annotation can also have a title, a subtitle, and two inset buttons or views on the left and right side of the title. All of these items are optional.
 
-The controls on the left and right side of the annotation can be specified in one of two
-ways:
+The controls on the left and right side of the annotation can be specified in one of two ways:
 
-* To display an image, set the [leftButton](Titanium.Map.Annotation.leftButton) or
-  [rightButton](Titanium.Map.Annotation.rightButton) property to an image URL. (On
+* To display an image, set the [leftButton](Titanium.Map.Annotation.leftButton) or [rightButton](Titanium.Map.Annotation.rightButton) property to an image URL. (On
 
 *(See full overview in titanium-docs)*
 
@@ -188,18 +182,13 @@ ways:
 > Extends Ti.Proxy
 > Platforms: both
 
-Applying a camera to a map has the effect of giving the map a 3D-like appearance.
-You can use a camera to rotate the map so that it is oriented to match the user's
-heading or to apply a pitch angle to tilt the plane of the map.
+Applying a camera to a map has the effect of giving the map a 3D-like appearance. You can use a camera to rotate the map so that it is oriented to match the user's heading or to apply a pitch angle to tilt the plane of the map.
 
-If the app is run on pre iOS 7, camera functionality will not be available.
-After creating a `Camera` object, it can be applied to the map by setting the `camera` property of the
-[map view](Modules.Map.View).
+If the app is run on pre iOS 7, camera functionality will not be available. After creating a `Camera` object, it can be applied to the map by setting the `camera` property of the [map view](Modules.Map.View).
 
 Use the <Modules.Map.createCamera> method to create a camera.
 
-If `altitude`, `eyeCoordinate`, and `centerCoordinate` are passed in on creation, a camera will be
-returned using the specified viewing angle information.
+If `altitude`, `eyeCoordinate`, and `centerCoordinate` are passed in on creation, a camera will be returned using the specified viewing angle information.
 
 ### Example:
 
@@ -234,8 +223,7 @@ returned using the specified viewing angle information.
 > Extends Ti.Proxy
 > Platforms: both
 
-The `Circle` object gives you low-level control over circles that can be added to a
-[map view](Modules.Map.View). A circle must have a `center` property and a `radius` set to appear on a map.
+The `Circle` object gives you low-level control over circles that can be added to a [map view](Modules.Map.View). A circle must have a `center` property and a `radius` set to appear on a map.
 
 Use the <Modules.Map.createCircle> method to create a circle.
 
@@ -272,9 +260,7 @@ Use the <Modules.Map.createCircle> method to create a circle.
 > Extends Ti.Proxy
 > Platforms: both
 
-The `ImageOverlay` object gives you low-level control over image overlays that can be added to a
-[map view](Modules.Map.View). An image overlay must have a `boundsCoordinate` property and a `image` 
-set to appear on a map.
+The `ImageOverlay` object gives you low-level control over image overlays that can be added to a [map view](Modules.Map.View). An image overlay must have a `boundsCoordinate` property and a `image` set to appear on a map.
 
 Use the <Modules.Map.createImageOverlay> method to create an image overlay.
 
@@ -304,8 +290,7 @@ Use the <Modules.Map.createImageOverlay> method to create an image overlay.
 > Extends Ti.Proxy
 > Platforms: both
 
-The `Polygon` object gives you low-level control over polygons that can be added to a
-[map view](Modules.Map.View). A polygon must have its `points` property set to appear on a map.
+The `Polygon` object gives you low-level control over polygons that can be added to a [map view](Modules.Map.View). A polygon must have its `points` property set to appear on a map.
 
 Use the <Modules.Map.createPolygon> method to create a polygon.
 
@@ -347,8 +332,7 @@ Use the <Modules.Map.createPolygon> method to create a polygon.
 > Extends Ti.Proxy
 > Platforms: both
 
-The `Polyline` object gives you low-level control over polylines that can be added to a
-[map view](Modules.Map.View). A polyline must have its `points` property set to appear on a map.
+The `Polyline` object gives you low-level control over polylines that can be added to a [map view](Modules.Map.View). A polyline must have its `points` property set to appear on a map.
 
 Use the <Modules.Map.createPolyline> method to create a polyline.
 
@@ -387,8 +371,7 @@ const polyline = Map.createPolyline({
 > Extends Ti.Proxy
 > Platforms: both
 
-The `Route` object gives you low-level control over routes that can be added to a
-[map view](Modules.Map.View). A route must have its `points` property set to appear on a map.
+The `Route` object gives you low-level control over routes that can be added to a [map view](Modules.Map.View). A route must have its `points` property set to appear on a map.
 
 Use the <Modules.Map.createRoute> method to create a route.
 
@@ -397,8 +380,7 @@ Use the <Modules.Map.createRoute> method to create a route.
 The `addRoute` method no longer accepts a dictionary as a parameter. Pass a <Modules.Map.Route> object instead.
 
 ### Android Platform Notes
-The parameter `points` accepts additional the route in format `encoded polyline`.  
-https://developers.google.com/maps/documentation/utilities/polylinealgorithm
+The parameter `points` accepts additional the route in format `encoded polyline`. https://developers.google.com/maps/documentation/utilities/polylinealgorithm
 
 ### Properties (unique: 4/7)
 | Property | Type | Default | Platform | Description |
@@ -484,9 +466,7 @@ const Snapshotter = MapModule.createSnapshotter({
 > Extends Ti.UI.View
 > Platforms: android
 
-Each street view panorama is an image, or set of images, that provides a full 360-degree view from
-a single location. It provides a viewer that renders the panorama as a sphere with a camera at its center.
-A window can only contain one street view.
+Each street view panorama is an image, or set of images, that provides a full 360-degree view from a single location. It provides a viewer that renders the panorama as a sphere with a camera at its center. A window can only contain one street view.
 
 ### Properties (unique: 5/66)
 | Property | Type | Default | Platform | Description |
@@ -517,14 +497,11 @@ A window can only contain one street view.
 > Extends Ti.UI.View
 > Platforms: both
 
-With native maps, you can control the mapping location, the type of map, the zoom level
-and you can add custom annotations and routes directly to the map. Once the map view is
-displayed, the user can pan, zoom and tilt the map using the native control gestures.
+With native maps, you can control the mapping location, the type of map, the zoom level and you can add custom annotations and routes directly to the map. Once the map view is displayed, the user can pan, zoom and tilt the map using the native control gestures.
 
 Use the <Modules.Map.createView> method to create a map view.
 
-In Alloy, use the **`<Module>`** element with the `module` attribute set to `ti.map`
-and `method` attribute set to `createView` to create a map view in XML markup:
+In Alloy, use the **`<Module>`** element with the `module` attribute set to `ti.map` and `method` attribute set to `createView` to create a map view in XML markup:
 
 
 ### Properties (unique: 29/101)
@@ -620,32 +597,42 @@ and `method` attribute set to `createView` to create a map view in XML markup:
 #### CameraAnimationParams
 > Simple object used to control camera animations.
 
-| Property | Type | Description |
-|----------|------|-------------|
-| camera | Modules.Map.Annotation | <Modules.Map.Camera> to be animated to. |
-| duration | Number | The amount of time (in milliseconds) that the animation will last. |
-| curve | Number | Animation curve or easing function to apply to the animation. |
+| Property | Type | Platform | Description |
+|----------|------|----------|-------------|
+| camera | Modules.Map.Annotation | both | <Modules.Map.Camera> to be animated to. |
+| duration | Number | both | The amount of time (in milliseconds) that the animation will last. |
+| curve | Number | both | Animation curve or easing function to apply to the animation. |
 
 #### ClusterAnnotationParams
 > Simple object used to create cluster annotation view.
 
-| Property | Type | Description |
-|----------|------|-------------|
-| memberAnnotations | Array<Modules.Map.Annotation> | Array of Modules.Map.Annotation, which is recieved in event 'clusteringstarted'… |
-| annotation | Modules.Map.Annotation | <Modules.Map.Annotation> instance, which you want to show as clustered annotati… |
+| Property | Type | Platform | Description |
+|----------|------|----------|-------------|
+| memberAnnotations | Array<Modules.Map.Annotation> | ios | Array of Modules.Map.Annotation, which is received in event 'clusteringstarted'… |
+| annotation | Modules.Map.Annotation | ios | <Modules.Map.Annotation> instance, which you want to show as clustered annotati… |
 
 #### MapLocationTypeV2
 > Simple object used as an argument to [setLocation](Modules.Map.View.setLocation).
 
-| Property | Type | Description |
-|----------|------|-------------|
-| longitude | Number | Longitude value for the center point of the map, in decimal degrees. |
-| latitude | Number | Latitude value for the center point of the map, in decimal degrees. |
-| longitudeDelta | Number | The amount of east-to-west distance displayed on the map, measured in decimal d… |
-| latitudeDelta | Number | The amount of north-to-south distance displayed on the map, measured in decimal… |
-| animate | Boolean | Set to `true` to animate the move to the new location. |
-
-*Plus 3 more types: MapViewPadding*
+| Property | Type | Platform | Description |
+|----------|------|----------|-------------|
+| longitude | Number | both | Longitude value for the center point of the map, in decimal degrees. |
+| latitude | Number | both | Latitude value for the center point of the map, in decimal degrees. |
+| longitudeDelta | Number | both | The amount of east-to-west distance displayed on the map, measured in decimal d… |
+| latitudeDelta | Number | both | The amount of north-to-south distance displayed on the map, measured in decimal… |
+| animate | Boolean | both | Set to `true` to animate the move to the new location. |
+
+#### MapViewPadding
+> The padding applied to the map view using <Modules.Map.View.padding>.
+
+| Property | Type | Platform | Description |
+|----------|------|----------|-------------|
+| top | Number | both | Top padding of the map view. |
+| left | Number | both | Left padding of the map view. |
+| bottom | Number | both | Bottom padding of the map view. |
+| right | Number | both | Right padding of the map view. |
+
+Also referenced by this API, documented elsewhere: [MapPointType](#mappointtype), [MapRegionTypev2](#mapregiontypev2).
 
 ---
 

package/skills/ti-api/references/api-modules-nfc.md

@@ -40,9 +40,7 @@
 > Platforms: both
 > Type: module
 
-This module provides access to Near Field Communication (NFC) functionality, 
-allowing applications to read and write (Android-only) NFC tags. 
-A "tag" may actually be another device that appears as a tag.
+This module provides access to Near Field Communication (NFC) functionality, allowing applications to read and write (Android-only) NFC tags. A "tag" may actually be another device that appears as a tag.
 
 ### NFC Resources
 
@@ -133,9 +131,7 @@ A "tag" may actually be another device that appears as a tag.
 > Extends Modules.Nfc.NativeTagTechnology
 > Platforms: ios
 
-Use the <Modules.Nfc.createTagTechnologyMifareUltralight> method to create this tag technology.
-See also:
-[Mifare Ultralight](https://developer.apple.com/documentation/corenfc/nfcmifaretag?language=objc)
+Use the <Modules.Nfc.createTagTechnologyMifareUltralight> method to create this tag technology. See also: [Mifare Ultralight](https://developer.apple.com/documentation/corenfc/nfcmifaretag?language=objc)
 
 
 ### Methods (5)
@@ -174,8 +170,7 @@ Common methods get called for all the native tags so that we can save the redund
 
 Use the <Modules.Nfc.createNdefMessage> method to create an NDEF message.
 
-See also:
-[NdefMessage](http://developer.android.com/reference/android/nfc/NdefMessage.html)
+See also: [NdefMessage](http://developer.android.com/reference/android/nfc/NdefMessage.html)
 
 ### Properties (unique: 1/3)
 | Property | Type | Default | Platform | Description |
@@ -196,10 +191,7 @@ See also:
 > Extends Ti.Proxy
 > Platforms: both
 
-**Android**:
-The NDEF record is the base type for more type-specific NDEF records. You will generally
-work with the type-specific NDEF records (e.g. NdefRecordText, NdefRecordUri, etc.) which have
-more applicable properties for each type of record.
+**Android**: The NDEF record is the base type for more type-specific NDEF records. You will generally work with the type-specific NDEF records (e.g. NdefRecordText, NdefRecordUri, etc.) which have more applicable properties for each type of record.
 
 Use one of the <Modules.Nfc.createNdefRecordApplication>, <Modules.Nfc.createNdefRecordEmpty>,
 
@@ -233,8 +225,7 @@ Use one of the <Modules.Nfc.createNdefRecordApplication>, <Modules.Nfc.createNde
 
 This record type was introduced in Android 4.0 (API level 14).
 
-See also:
-[createApplicationRecord](http://developer.android.com/reference/android/nfc/NdefRecord.html#createApplicationRecord(java.lang.String))
+See also: [createApplicationRecord](http://developer.android.com/reference/android/nfc/NdefRecord.html#createApplicationRecord(java.lang.String))
 
 ### Properties (unique: 1/9)
 | Property | Type | Default | Platform | Description |
@@ -261,8 +252,7 @@ See also:
 > Extends Modules.Nfc.NdefRecord
 > Platforms: android
 
-See also:
-[createExternal](http://developer.android.com/reference/android/nfc/NdefRecord.html#createExternal(java.lang.String,%20java.lang.String,%20byte[]))
+See also: [createExternal](http://developer.android.com/reference/android/nfc/NdefRecord.html#createExternal(java.lang.String,%20java.lang.String,%20byte[]))
 
 ### Properties (unique: 2/10)
 | Property | Type | Default | Platform | Description |
@@ -280,8 +270,7 @@ See also:
 > Extends Modules.Nfc.NdefRecord
 > Platforms: android
 
-See also:
-[createMime](http://developer.android.com/reference/android/nfc/NdefRecord.html#createMime(java.lang.String,%20byte[]))
+See also: [createMime](http://developer.android.com/reference/android/nfc/NdefRecord.html#createMime(java.lang.String,%20byte[]))
 
 ### Properties (unique: 1/9)
 | Property | Type | Default | Platform | Description |
@@ -343,8 +332,7 @@ See also:
 > Extends Modules.Nfc.NdefRecord
 > Platforms: android
 
-See also:
-[createUri](http://developer.android.com/reference/android/nfc/NdefRecord.html#createUri(java.lang.String))
+See also: [createUri](http://developer.android.com/reference/android/nfc/NdefRecord.html#createUri(java.lang.String))
 
 ### Properties (unique: 1/9)
 | Property | Type | Default | Platform | Description |
@@ -361,15 +349,11 @@ See also:
 > Extends Ti.Proxy
 > Platforms: both
 
-The NFC adapter gives you access to the features of the NFC device. The NFC adapter proxy is always
-associated with the activity that was the current activity when it was created. The NFC Adapter must
-be created after the activity has been opened. You can use the window `open` event to know when the
-activity has been opened.
+The NFC adapter gives you access to the features of the NFC device. The NFC adapter proxy is always associated with the activity that was the current activity when it was created. The NFC Adapter must be created after the activity has been opened. You can use the window `open` event to know when the activity has been opened.
 
 Use the <Modules.Nfc.createNfcAdapter> method to create an NFC adapter.
 
-See also:
-[NfcAdapter](http://developer.android.com/reference/android/nfc/NfcAdapter.html)
+See also: [NfcAdapter](http://developer.android.com/reference/android/nfc/NfcAdapter.html)
 
 ### Properties (unique: 8/11)
 | Property | Type | Default | Platform | Description |
@@ -407,15 +391,11 @@ See also:
 > Extends Ti.Proxy
 > Platforms: android
 
-The <Modules.Nfc.NfcAdapter.enableForegroundDispatch> method is used to give priority to the foreground activity when dispatching
-a discovered tag to an application. This proxy is used to specify the intent, intent filters, and technology
-lists used to filter the dispatched intents. This proxy automatically creates the required pending intent and
-will create an intent for the current activity if one is not provided.
+The <Modules.Nfc.NfcAdapter.enableForegroundDispatch> method is used to give priority to the foreground activity when dispatching a discovered tag to an application. This proxy is used to specify the intent, intent filters, and technology lists used to filter the dispatched intents. This proxy automatically creates the required pending intent and will create an intent for the current activity if one is not provided.
 
 Use the <Modules.Nfc.createNfcForegroundDispatchFilter> method to create a foreground dispatch filter.
 
-See also:
-[enableForegroundDispatch](http://developer.android.com/reference/android/nfc/NfcAdapter.html#enableForegroundDispatch(android.app.Activity,%20android.app.PendingIntent,%20android.content.IntentFilter[],%20java.lang.String[][]))
+See also: [enableForegroundDispatch](http://developer.android.com/reference/android/nfc/NfcAdapter.html#enableForegroundDispatch(android.app.Activity,%20android.app.PendingIntent,%20android.content.IntentFilter[],%20java.lang.String[][]))
 
 ### Properties (unique: 3/5)
 | Property | Type | Default | Platform | Description |
@@ -478,8 +458,7 @@ Use the <Modules.Nfc.createTagTechNdef> method to create this NDEF tag technolog
 > Extends Ti.Proxy
 > Platforms: both
 
-See also:
-[Tag](http://developer.android.com/reference/android/nfc/Tag.html)
+See also: [Tag](http://developer.android.com/reference/android/nfc/Tag.html)
 
 ### Properties (unique: 2/5)
 | Property | Type | Default | Platform | Description |
@@ -503,10 +482,7 @@ See also:
 > Extends Ti.Proxy
 > Platforms: android
 
-NFC tags are based on a number of independently developed technologies and offer a wide range of
-capabilities. The TagTechnology proxies provide access to these different technologies and capabilities.
-The TagTechnology proxy is the base type for more type-specific tag technologies. You will
-work with the type-specific tag technology proxies which provide capabilities for each tag technology.
+NFC tags are based on a number of independently developed technologies and offer a wide range of capabilities. The TagTechnology proxies provide access to these different technologies and capabilities. The TagTechnology proxy is the base type for more type-specific tag technologies. You will work with the type-specific tag technology proxies which provide capabilities for each tag technology.
 
 Use one of the <Modules.Nfc.createTagTechnologyIsoDep>, <Modules.Nfc.createTagTechnologyMifareClassic>,
 
@@ -534,8 +510,7 @@ Use one of the <Modules.Nfc.createTagTechnologyIsoDep>, <Modules.Nfc.createTagTe
 
 Use the <Modules.Nfc.createTagTechnologyIsoDep> method to create this tag technology.
 
-See also:
-[IsoDep](http://developer.android.com/reference/android/nfc/tech/IsoDep.html)
+See also: [IsoDep](http://developer.android.com/reference/android/nfc/tech/IsoDep.html)
 
 
 ### Methods (7)
@@ -559,8 +534,7 @@ See also:
 
 Use the <Modules.Nfc.createTagTechnologyMifareClassic> method to create this tag technology.
 
-See also:
-[MifareClassic](http://developer.android.com/reference/android/nfc/tech/MifareClassic.html)
+See also: [MifareClassic](http://developer.android.com/reference/android/nfc/tech/MifareClassic.html)
 
 ### Constants (3)
 - **KEY_\***: KEY_DEFAULT
@@ -601,8 +575,7 @@ See also:
 
 Use the <Modules.Nfc.createTagTechnologyMifareUltralight> method to create this tag technology.
 
-See also:
-[MifareUltralight](http://developer.android.com/reference/android/nfc/tech/MifareUltralight.html)
+See also: [MifareUltralight](http://developer.android.com/reference/android/nfc/tech/MifareUltralight.html)
 
 
 ### Methods (7)
@@ -626,8 +599,7 @@ See also:
 
 Use the <Modules.Nfc.createTagTechnologyNdef> method to create this tag technology.
 
-See also:
-[Ndef](http://developer.android.com/reference/android/nfc/tech/Ndef.html)
+See also: [Ndef](http://developer.android.com/reference/android/nfc/tech/Ndef.html)
 
 
 ### Methods (8)
@@ -652,8 +624,7 @@ See also:
 
 Use the <Modules.Nfc.createTagTechnologyNdefFormatable> method to create this tag technology.
 
-See also:
-[NdefFormatable](http://developer.android.com/reference/android/nfc/tech/NdefFormatable.html)
+See also: [NdefFormatable](http://developer.android.com/reference/android/nfc/tech/NdefFormatable.html)
 
 
 ### Methods (2)
@@ -672,8 +643,7 @@ See also:
 
 Use the <Modules.Nfc.createTagTechnologyNfcA> method to create this tag technology.
 
-See also:
-[NfcA](http://developer.android.com/reference/android/nfc/tech/NfcA.html)
+See also: [NfcA](http://developer.android.com/reference/android/nfc/tech/NfcA.html)
 
 
 ### Methods (6)
@@ -696,8 +666,7 @@ See also:
 
 Use the <Modules.Nfc.createTagTechnologyNfcB> method to create this tag technology.
 
-See also:
-[NfcB](http://developer.android.com/reference/android/nfc/tech/NfcB.html)
+See also: [NfcB](http://developer.android.com/reference/android/nfc/tech/NfcB.html)
 
 
 ### Methods (4)
@@ -718,8 +687,7 @@ See also:
 
 Use the <Modules.Nfc.createTagTechnologyNfcF> method to create this tag technology.
 
-See also:
-[NfcF](http://developer.android.com/reference/android/nfc/tech/NfcF.html)
+See also: [NfcF](http://developer.android.com/reference/android/nfc/tech/NfcF.html)
 
 
 ### Methods (6)
@@ -742,8 +710,7 @@ See also:
 
 Use the <Modules.Nfc.createTagTechnologyNfcV> method to create this tag technology.
 
-See also:
-[NfcV](http://developer.android.com/reference/android/nfc/tech/NfcV.html)
+See also: [NfcV](http://developer.android.com/reference/android/nfc/tech/NfcV.html)
 
 
 ### Methods (4)

package/skills/ti-api/references/api-modules-social-misc.md

@@ -206,17 +206,20 @@
 > Platforms: both
 > Type: module
 
-### Properties (unique: 10/50)
+### Properties (unique: 14/50)
 | Property | Type | Platform | Description |
 |----------|------|----------|-------------|
 | accessToken | String | both | OAuth token set after a successful `authorize`. |
 | accessTokenExpired | Boolean | both | Returns whether the <Modules.Facebook.accessToken… |
 | accessTokenActive | Boolean | both | Returns `true` if the <Modules.Facebook.accessTok… |
+| advertiserTrackingEnabled | Boolean | ios | Gets or sets the SDK's advertiser-tracking flag. |
 | appID | String | both | If not explicitly set, the default will be read f… |
+| authenticationToken | String | android | Returns the raw Authentication Token (JWT) from the most recent Limited Login, … |
 | canPresentOpenGraphActionDialog | Boolean | android | Checks if the device can support the use of the F… |
 | expirationDate | Date | both | Time at which the `accessToken` expires. |
 | loggedIn | Boolean | both | Indicates if the user is logged in. |
-| loginTracking | Number | ios | Gets or sets the desired tracking preference to u… |
+| loginTracking | Number | both | Gets or sets the desired tracking preference to use for login attempts. |
+| nonce | String | android | Optional nonce used by Limited Login (`LOGIN_TRACKING_LIMITED`) to bind the iss… |
 | permissions | Array<String> | both | Array of permissions to request for your app. |
 | uid | String | both | Unique user ID returned from Facebook. |
 
@@ -272,13 +275,30 @@
 ### Events (6)
 | Event | Platform | Description |
 |-------|----------|-------------|
-| login | both | Fired at session login. |
+| login | both | Fired at session login. Payload: `success`, `cancelled`, `error`, `code`, `uid`, `data`, `authenticationToken`. |
 | logout | both | Fired at session logout. |
 | requestDialogCompleted | both | Fired when the Send Request dialog is closed. |
 | shareCompleted | both | Fired when the Share dialog or Web Share dialog is closed. |
 | inviteCompleted | both | Fired when the Invite dialog is closed. |
 | tokenUpdated | both | Fired when [refreshPermissionsFromServer](Modules.Facebook.refreshPermissionsFr… |
 
+### Login Tracking and Limited Login
+
+`loginTracking` and the `LOGIN_TRACKING_ENABLED` (default) / `LOGIN_TRACKING_LIMITED` constants are supported on **both** platforms. With `LOGIN_TRACKING_LIMITED`, `authorize()` (or `requestNewReadPermissions()`) starts Facebook's OIDC-based Limited Login flow: the SDK returns an Authentication Token (a JWT) instead of a classic Graph access token, delivered as `event.authenticationToken.tokenString` on the `login` event. Verify that JWT's signature server-side against Facebook's JWKS.
+
+> **Warning:** `Modules.Facebook.LoginButton` honors `loginTracking` on iOS only. The Android FB SDK's button exposes no Limited Login configuration, so on Android you must trigger Limited Login through `Modules.Facebook.authorize()` rather than through the button.
+
+### Related Types
+
+#### LimitedLoginAuthenticationToken
+> Shape of `event.authenticationToken` on the [login](Modules.Facebook.login) event when Limited Login (`LOGIN_TRACKING_LIMITED`) is used.
+
+| Property | Type | Platform | Description |
+|----------|------|----------|-------------|
+| tokenString | String | both | The signed JWT (header.payload.signature) issued by Facebook. Verify on your ba… |
+| nonce | String | both | The nonce echoed back by Facebook. Matches the [nonce](Modules.Facebook.nonce) … |
+| graphDomain | String | both | Optional graph domain hint returned by the iOS SDK (e.g. `gaming`). `undefined`… |
+
 ---
 
 ## Modules.Facebook.LoginButton

package/skills/ti-api/references/api-ui-android.md

@@ -138,8 +138,7 @@ Use a CardView to layout content that:
   * Supports variable length content or displays more than three lines of text
   * Contains rich content or interactive elements, such as comments or a favorite button
 
-If you are displaying a collection of the same type in a uniform layout without many actions,
-use a [ListView](Titanium.UI.ListView) or [TableView](Titanium.UI.TableView) instead.
+If you are displaying a collection of the same type in a uniform layout without many actions, use a [ListView](Titanium.UI.ListView) or [TableView](Titanium.UI.TableView) instead.
 
 For design guidelines, see
 
@@ -174,8 +173,7 @@ For design guidelines, see
 | ------- |
 | ![Android](./collpasetoolbar_android.jpg) |
 
-CollapseToolbar acts as a top-level container for window content that allows to set a parallax image and title
-in the toolbar. The main content goes into `centerView` and will automatically be scrollable.
+CollapseToolbar acts as a top-level container for window content that allows to set a parallax image and title in the toolbar. The main content goes into `centerView` and will automatically be scrollable.
 
 ### Properties (unique: 11/18)
 | Property | Type | Default | Platform | Description |
@@ -206,15 +204,11 @@ in the toolbar. The main content goes into `centerView` and will automatically b
 | ------- |
 | ![Android](./drawerlayout_android.png) |
 
-DrawerLayout acts as a top-level container for window content that allows for interactive "drawer"
-views to be pulled out from one or both vertical edges of the window.
+DrawerLayout acts as a top-level container for window content that allows for interactive "drawer" views to be pulled out from one or both vertical edges of the window.
 
-As per the Android Design guide, any drawers positioned to the left/start should always contain
-content for navigating around the application, whereas any drawers positioned to the right/end
-should always contain actions to take on the current content.
+As per the Android Design guide, any drawers positioned to the left/start should always contain content for navigating around the application, whereas any drawers positioned to the right/end should always contain actions to take on the current content.
 
-For design guidelines, see
-[Google Design Guidelines: DrawerLayout](https://developer.android.com/training/implementing-navigation/nav-drawer.html)
+For design guidelines, see [Google Design Guidelines: DrawerLayout](https://developer.android.com/training/implementing-navigation/nav-drawer.html)
 
 ### Properties (unique: 15/80)
 | Property | Type | Default | Platform | Description |
@@ -266,8 +260,7 @@ For design guidelines, see
 > Extends Ti.UI.View
 > Platforms: android
 
-For design guidelines, see
-[Material design: Snackbars](https://material.io/components/buttons-floating-action-button)
+For design guidelines, see [Material design: Snackbars](https://material.io/components/buttons-floating-action-button)
 
 ### Properties (unique: 4/30)
 | Property | Type | Default | Platform | Description |
@@ -295,15 +288,11 @@ For design guidelines, see
 | ------- |
 | ![Android](./progressindicator_android.png) |
 
-A progress indicator can be used to show the progress of an operation in the UI to let the
-user know that some action is taking place. It is used to indicate an ongoing activity of
-determinate or indeterminate length.
+A progress indicator can be used to show the progress of an operation in the UI to let the user know that some action is taking place. It is used to indicate an ongoing activity of determinate or indeterminate length.
 
-Use the <Titanium.UI.Android.createProgressIndicator> method or **`<ProgressIndicator>`** Alloy
-element to create a progress indicator.
+Use the <Titanium.UI.Android.createProgressIndicator> method or **`<ProgressIndicator>`** Alloy element to create a progress indicator.
 
-A progress indicator can be either a progress dialog or a horizontal progress bar in the title
-of the window. The progress dialog is a modal dialog that blocks the UI. See also:
+A progress indicator can be either a progress dialog or a horizontal progress bar in the title of the window. The progress dialog is a modal dialog that blocks the UI. See also:
 
 ### Properties (unique: 8/29)
 | Property | Type | Default | Platform | Description |
@@ -351,12 +340,9 @@ of the window. The progress dialog is a modal dialog that blocks the UI. See als
 
 `SearchView` provides a user interface to enter a search query and submit a request to a search provider.
 
-Search views are most commonly used for filtering the rows in a [TableView](Titanium.UI.TableView).
-Similar to [SearchBar](Titanium.UI.SearchBar), you can add a search view to a table view by setting the table view's
-[search](Titanium.UI.TableView.search) property. A search view can be used without a `TableView`.
+Search views are most commonly used for filtering the rows in a [TableView](Titanium.UI.TableView). Similar to [SearchBar](Titanium.UI.SearchBar), you can add a search view to a table view by setting the table view's [search](Titanium.UI.TableView.search) property. A search view can be used without a `TableView`.
 
-You can also use a `SearchView` object as the <Titanium.UI.ListView.searchView>
-property of a [ListView](Titanium.UI.ListView) object.
+You can also use a `SearchView` object as the <Titanium.UI.ListView.searchView> property of a [ListView](Titanium.UI.ListView) object.
 
 You can also add `SearchView` to an `ActionBar` as a view (see example below).
 
@@ -401,8 +387,7 @@ You can also add `SearchView` to an `ActionBar` as a view (see example below).
 | ------- |
 | ![Android](./snackbar_android.png) |
 
-For design guidelines, see
-[Material design: Snackbars](https://material.io/components/snackbars)
+For design guidelines, see [Material design: Snackbars](https://material.io/components/snackbars)
 
 ### Properties (unique: 3/27)
 | Property | Type | Default | Platform | Description |
@@ -443,14 +428,9 @@ For design guidelines, see
 
 A popover is created using the <Titanium.UI.iPad.createPopover> method or **`<Popover>`** Alloy element.
 
-Popovers are used to present information temporarily, but in a way that does not take over
-the entire screen in the way that a modal view does. The popover content is layered on top of
-the existing content in a special type of window. The popover remains visible until the user
-taps outside of the popover window or it is explicitly dismissed.
+Popovers are used to present information temporarily, but in a way that does not take over the entire screen in the way that a modal view does. The popover content is layered on top of the existing content in a special type of window. The popover remains visible until the user taps outside of the popover window or it is explicitly dismissed.
 
-Do not add top-level view containers, such as a `SplitWindow` or `TabGroup`, to a popover.
-Adding top-level view containers may have unintended side effects. See the [contentView](Titanium.UI.iPad.Popover.contentView)
-property for more information.
+Do not add top-level view containers, such as a `SplitWindow` or `TabGroup`, to a popover. Adding top-level view containers may have unintended side effects. See the [contentView](Titanium.UI.iPad.Popover.contentView) property for more information.
 
 ### Properties (unique: 4/13)
 | Property | Type | Default | Platform | Description |
@@ -498,10 +478,9 @@ property for more information.
 > Platforms: ios
 > Type: module
 
-All properties, methods and events in this namespace will only work on the Apple iPad devices. 
+All properties, methods and events in this namespace will only work on the Apple iPad devices.
 
-For iOS UI programming guidelines, review the
-[iOS Human Interface Guidelines](https://developer.apple.com/ios/human-interface-guidelines/overview/themes/).
+For iOS UI programming guidelines, review the [iOS Human Interface Guidelines](https://developer.apple.com/ios/human-interface-guidelines/overview/themes/).
 
 ### Constants (6)
 - **POPOVER_ARROW_DIRECTION_\***: POPOVER_ARROW_DIRECTION_ANY, POPOVER_ARROW_DIRECTION_DOWN, POPOVER_ARROW_DIRECTION_LEFT, POPOVER_ARROW_DIRECTION_RIGHT, POPOVER_ARROW_DIRECTION_UNKNOWN, POPOVER_ARROW_DIRECTION_UP