ig_push_token_registration -- the push token registration's status, as the
token analytics module writes it at the app's start-up (token_requested
beside the initiated fetch, token_result_received beside the token the
provider returned, registration_initiated beside the registration into the
push transport, registration_result_received at its answer). The
trigger names the launch (app_startup) in the recordings that carry the
field at all; a caller whose recording names no trigger omits it.
device_sub_type is the phase's own fact, as every recording carries it
(issue #944): the token request reports "1", and the three events that
report the FBNS token and its registration report "2" — the sub type the
process's own push/register request sends for the in-app FBNS service
(device_sub_type=2, is_main_push_channel=true). The sub type is never a
caller input: it derives from the phase, so the event carries no value the
recordings do not.
ig_push_token_registration -- the push token registration's status, as the token analytics module writes it at the app's start-up (
token_requestedbeside the initiated fetch,token_result_receivedbeside the token the provider returned,registration_initiatedbeside the registration into the push transport,registration_result_receivedat its answer). Thetriggernames the launch (app_startup) in the recordings that carry the field at all; a caller whose recording names no trigger omits it.device_sub_typeis the phase's own fact, as every recording carries it (issue #944): the token request reports "1", and the three events that report the FBNS token and its registration report "2" — the sub type the process's ownpush/registerrequest sends for the in-app FBNS service (device_sub_type=2,is_main_push_channel=true). The sub type is never a caller input: it derives from the phase, so the event carries no value the recordings do not.