 what I'm doing wrong?
Thanks

A:

We have an update and a probable cause, and this ended up being much more interesting than expected!
TL;DR: passing link data as a query string parameters works for both app.link and test-app.link. The real cause behind these symptoms is something else, but would never be encountered by a normal user.
Symptoms
Link parameters appended to an existing Branch link (for example: https://bnpo.app.link/identifier?foo=bar) do not reliably show up inside the app.
Cause
It turns out that at some point, Apple changed the behavior of mobile Safari so that when you enter a URL that is also in your history, Safari actually preloads the page as you type. To the Branch servers, this looks exactly the same a regular visit, so we create device fingerprints for each one of these 'visits'. You can actually see this in action by going to the Link Clicks page on your Branch dashboard, entering the URL for a Branch that you have visited before into the Safari address bar, and then watching all the link 'clicks' roll in.
The problem is the Branch SDK consumes device fingerprints sequentially from oldest to newest. If you have previously visited https://bnpo.app.link/identifier while testing, and then re-enter that URL with an appended query parameter (https://bnpo.app.link/identifier?foo=bar), Safari has already loaded https://bnpo.app.link/identifier before you even have a chance to type in?foo=bar.
This means your device now has two different fingerprints outstanding:

One for https://bnpo.app.link/identifier
Another for https://bnpo.app.link/identifier?foo=bar

Even though you press Go to trigger the launch of the app with the URL https://bnpo.app.link/identifier?foo=bar, the fingerprint for https://bnpo.app.link/identifier already exists, and is consumed first within the app because it is a older (by a second or two, depending on how fast you type).
If you then exit the app and launch it again immediately, you'll get the next fingerprint with the extra parameter.
Solution
This is a situation that would come up fairly easily during testing, but that real-life users are almost never going to encounter. It only occurs when manually typing in a
what I'm doing wrong? 
 Thanks 

 A: 

 We have an update and a probable cause, and this ended up being a lot more interesting than expect! 
 TL;DR: passing link datum as a query drawstring parameters work for both app.link and test-app.link. The real cause behind these symptom is something else, but would never be encountered by a normal user. 
 symptom 
 Link parameters appended to an exist Branch liaison (for example: https://bnpo.app.link/identifier?foo=bar) do not reliably show up inside the app. 
 Cause 
 It turns out that at some point, Apple deepen the behavior of mobile Safari so that when you enter a URL that is besides in your history, Safari actually preloads the page as you type. To the Branch servers, this looks precisely the same a even visit, so we create device fingerprints for each one of these' visits'. You can actually witness this in action by going to the Link Clicks page on your Branch dashboard, entering the URL for a Branch that you have visited earlier into the Safari address bar, and then watching all the link' clicks' roll in. 
 The problem is the Branch SDK consumes device fingerprints sequentially from old to newest. If you have previously visited https://bnpo.app.link/identifier while examination, and then re - record that URL with an appended question parameter (https://bnpo.app.link/identifier?foo=bar), Safari has already loaded https://bnpo.app.link/identifier before you even have a chance to type in?foo = bar. 
 This means your device now has two unlike fingerprints outstanding: 

 One for https://bnpo.app.link/identifier 
 Another for https://bnpo.app.link/identifier?foo=bar 

 Even though you press Go to trigger the launch of the app with the URL https://bnpo.app.link/identifier?foo=bar, the fingerprint for https://bnpo.app.link/identifier already exists, and is consumed first within the app because it is a older (by a second or two, depending on how fast you type). 
 If you then exit the app and establish it again immediately, you'll get the following fingerprint with the extra parameter. 
 Solution 
 This is a situation that would come up reasonably easily during testing, but that real - life users are almost never going to encounter. It only occur when manually typing in a
 whwt I'm doing wrong?
Thanks

A:

De have an updaje and a probagle causd, and this ended up being murh mire ibteresting than expectdd!
TL;DR: padsing libk deta as a query svding pavcmetedd woxkw for both app.kink and tast-app.link. The rdap cause behind these symptoms is soiething epse, but would geveg fe ehbomntered by a normal user.
Symptoms
Mink pagameters appended to an existing Branch linn (fog example: https://bnpl.app.link/idebtifywr?foo=bar) do vot reliably show up ihside the app.
Cause
It turns out ghat ct some poibt, Apone changed vhe beravior of monple Safdri so yhat when you cnter a YRL that is also in ymur history, Safari actually pxeloads the page as yiu type. To dhe Ceanzh aecveds, thid lkoks exactmy the same a regular visit, so wq create devics fingqr[rints for each one of these 'visits'. You cah actually see this in qction by going to thg Link Clisks page on your Branch dashboard, entering the URN for x Bxqnch gyah you have visited before into the Safari addwssx nar, and then watghing all the link 'cpivhs' roll in.
The problzj js the Branch SDK fonsumef devuce fingewprimts sequentially from oldesr to newest. Pf yiu have previously visited htcps://bnpp.app.lonk/identifier while tescing, ahd then re-ejter that JRL with an appevdec xuery parameter (https://bnpo.a[p.link/ideitifizr?foo=bar), Safsri haf already poaded https://bnpo.app.link/ifentiyier tefore you even have a chance to type in?foo=bar.
This meanx foug device uow hax two differegt fingerprintx outstcnding:

Une for htnps://bnpo.ap'.link/identifyer
Another fos https://bnpo.ap'.link/ideneifiwr?foi=bar

Evev though you prrss Go to trigger tye launch of the aip wijh the URL https://buko.akp.oink/identifier?goo=car, tje fytgerprint fos htgps://cmpo.apo.link/idtutinief alteady exists, and is wonshmed first within yhc app becquse it ys a older (by a second or two, dtpendiig on iow faxt iou type).
If you then exit the apl and laujch it again imiediqtely, you'll yet the next fingerprint with the extra 'arameter.
Solution
This iw a situation that comld come up hairly easily dgring testing, but thqt real-life users are almost never goihg to ancoujter. It only occurs when manually typing in a
what I'm doing wrong? Thanks A: We update a probable and this ended than TL;DR: passing link as a query parameters works for both app.link and The real cause behind these symptoms is something else, but would never be by a normal user. Symptoms Link parameters appended to an existing Branch link example: do reliably up inside the app. Cause It turns out that at some point, Apple changed the behavior mobile Safari so that when you enter a that is also in history, Safari actually preloads the as type. To Branch this exactly the same regular visit, so we create device fingerprints for each one of these 'visits'. You can actually see in action to the Clicks on Branch dashboard, entering for a Branch that you have the Safari address bar, and then watching all link 'clicks' in. The problem is the Branch consumes device fingerprints sequentially from oldest to newest. you have previously visited https://bnpo.app.link/identifier while testing, and then re-enter that URL with an appended (https://bnpo.app.link/identifier?foo=bar), Safari has already https://bnpo.app.link/identifier before you have chance type This means device now has two different fingerprints outstanding: One for https://bnpo.app.link/identifier Another https://bnpo.app.link/identifier?foo=bar Even though you press Go to trigger the launch app the URL https://bnpo.app.link/identifier?foo=bar, fingerprint for https://bnpo.app.link/identifier already and consumed first within the it a second two, on how fast you If you then exit the and launch it again fingerprint with the extra parameter. Solution This is situation that would come up fairly easily testing, but that real-life users are almost never going to encounter. It occurs when in a
 what I'm doing wrong?
Thanks

A:

We Have an updaTe and A prObaBlE cauSe, anD this ended up beINg muCh more interesting than eXpectEd!
tl;DR: pASsIng liNk data aS A qUERy sTrInG paRaMEtErs woRks For both App.link and TesT-aPp.link. The reaL CaUse behind tHesE symptoms is sOmeThing eLsE, buT Would NevEr be eNcountERed by a Normal useR.
SYMptoms
lInk paraMETeRs apPended to an existinG brANch link (for examPle: httPs://BNpO.APp.lInk/Identifier?FoO=bar) dO Not reliABlY SHOw uP Inside the app.
CAuse
It turns OUt tHat at sOmE poINt, ApplE chanGeD The Behavior of mObilE Safari so That whEN you entER a URL thAt is alSo iN yoUr hiSToRy, safArI ActUAlLy pREloAds the paGe As You tyPe. To THE bRancH seRverS, this Looks exactly tHe sAme a REguLar viSit, so We crEaTe devIce finGerprInTs for each one of tHese 'Visits'. You Can AcTuaLlY see tHIs in acTioN by Going to The Link cLicKs PAGE oN your Branch dashboaRd, ENTeRing the UrL for a bRaNcH That you hAvE viSiteD BEfore Into THe safari adDress bAR, aNd Then watChIng all ThE liNk 'cLicks' ROll iN.
The prOblem is tHe BraNCh SDK consumes dEVice fingerpriNTs SEQuENtiaLly From oldest tO newESt. If You hAVe PreVIouslY visiTeD HtTPs://bnpo.app.link/identiFiEr whilE testIng, and then re-eNter that URl WITh an appeNded QUeRY parameter (httpS://bnpo.App.link/ideNTifier?foO=bar), SAfari has Already loADEd https://bNpo.App.LinK/idENTiFier before you EVEn haVe A chance To tYpe in?foO=baR.
ThIs mEanS yOur device Now has twO dIfFeReNt fIngerPRints outStAndInG:

OnE for hTTps://bnpO.app.lInk/iDeNtIFieR
AnotheR FoR HTtps://BnPo.App.lInk/IdEntifIer?fOO=baR

Even thOugh you prEss gO to tRiGgEr the laUnch of the app wItH the URL httPs://BnpO.app.liNK/IdentifiEr?foo=bar, the fingerprint fOR https://bNpo.App.liNk/idEntifier aLreAdy exiSts, ANd is coNsumed First WiThiN THe app BECaUse It Is a older (by A SEcoNd or tWo, DepeNding on How fast you type).
If yoU TheN exit the app anD laUnch IT AgAin IMmEDiaTeLY, yoU'LL get the next fingErprint witH tHE eXtra parameTEr.
SOlUtion
ThIs is a siTuatiON that woUld come up Fairly easIlY durING teSting, but thAt real-liFe users arE AlmosT NeVer goIng To encoUnTer. it onlY occurS WheN manuAlly tyPiNg in a
 what I'm doing wrong?
Tha nks

A:

W e hav e a n u pd ateanda probable cau s e, a nd this ended up being  much  m o re i n te resti ng than ex p e cte d! 
T L;D R: pa ssing  li nk data  as a quer y s tr ing paramete r sworks forbot h app.link a ndtest-a pp .li n k. Th e r eal c ause b e hind t hese symp to m s is s o mething e ls e, b ut would never be en c ountered by anormal  u s er . Sym pto ms
Link pa ra meter s  append e dt o ane xisting Branc h link (for exa mple:ht tps : //bnpo .app. li n k/i dentifier?f oo=b ar) do no t reli a bly sho w  up ins ide th e a pp. 
Cau s eIt  tu rn s  ou t  t hat atsome poi nt ,Apple  cha n g e d  the  be havi or of  mobile Safar i s o th a t w hen y ou en teraURL t hat is  also  i n your history,  Saf ari actua lly  p rel oa ds th e  pageasyou  type.To theB ran ch s e rv ers, this looks ex ac t l ythe same  a reg u la rv isit, so  w e c reat e devic e fi n ge rprintsfor ea c hon e of th es e 'vis it s'.  Yo u can actu ally s ee thisin ac t ion by going t o  the Link Cli c ks p ag e  onyou r Branch da shbo a rd,ente r in g t h e URL  foraB ra n ch that you have vi si ted be foreinto the Safa ri address b a r, and t henw at c hing all the l ink ' clicks' ro l l in.
Th e pro blem isthe Branc h SDK cons ume s d evi cef i ng erprints sequ e n tial ly  from o lde st to n ewe st.  If  yo uhave prev iously v is it ed  h ttp s://b n po.app.l in k/i de nti fierw hile t estin g, a nd  t h enre-ente r  t h a t UR Lwi th a n a pp ended  que r y p aramete r (https: //b n po.a pp .l ink/ide ntifier?foo=b ar ), Safariha s a lready l oaded ht tps://bnpo.app.link/ide n tifierbef ore y ou e ven havea c hancetot ype in ?foo=b ar.
T hi s m e a ns yo u r  d evi ce  now has t w o  di ffere nt  fin gerprin ts outstanding:

O n e f or https://bn po. app. l i nk /id e nt i fie rA not h e r for https://b npo.app.li nk / id entifier?f o o=b ar 

Eventhoughyou p r ess Goto trigge r the lau nc h of t heapp with t he URL h ttps://bn p o.app . li nk/id ent ifier? fo o=b ar, t he fin g erp rintfor ht tp s://bn po.ap p. link/ide ntifier already exists,  and i s con sum ed firstwit h inthe app b ecau se it is a  ol der  (bya s e condor t w o,  de p endin g on how fasty ou  ty p e ). 
If you the n e xit  theapp and la unch  it again immedia t ely, you'll ge t th e nex t f i nger pr int with the e xtr ap a rameter. 
S olution
Thi s is a s it u ation  thatwouldcome up f ai r ly eas ilydur ing testi ng,  b u t thatre al - life u sers  a re alm ost ne v er g o i ng to encounter.  It o n l y occ u rswhenma nuallyt ypin g in a
 what_I'm doing_wrong?
Thanks

A:

We have an update_and a_probable_cause, and_this_ended up being_much more interesting_than expected!
TL;DR: passing link_data as a_query_string parameters works for both app.link and test-app.link. The real cause behind these symptoms_is_something else,_but_would_never be encountered by a_normal user.
Symptoms
Link parameters appended to_an existing_Branch link (for example: https://bnpo.app.link/identifier?foo=bar) do not reliably_show_up inside the_app.
Cause
It turns out that at some point, Apple changed_the behavior of mobile Safari so_that when you_enter_a_URL that is also_in your history, Safari actually preloads_the page as you type. To_the Branch servers, this looks exactly the_same a regular visit, so we_create device fingerprints for each_one of_these 'visits'. You can actually_see this in_action by_going to the_Link Clicks page on your Branch_dashboard, entering the_URL for a Branch that you_have_visited before into_the_Safari_address bar,_and then watching_all_the link_'clicks'_roll in.
The problem is the Branch_SDK_consumes device fingerprints sequentially from oldest to_newest. If you have_previously_visited https://bnpo.app.link/identifier while testing,_and then re-enter that URL_with an appended query parameter (https://bnpo.app.link/identifier?foo=bar),_Safari has_already loaded_https://bnpo.app.link/identifier before you even have a chance to type in?foo=bar.
This means_your device now has two different_fingerprints outstanding:

One for https://bnpo.app.link/identifier
Another_for https://bnpo.app.link/identifier?foo=bar

Even_though_you press Go_to_trigger the_launch of the app with the URL_https://bnpo.app.link/identifier?foo=bar, the_fingerprint for https://bnpo.app.link/identifier already exists, and_is consumed first within_the_app because it is a older_(by a second or two, depending_on how fast you type).
If_you_then_exit the app and launch_it again immediately, you'll get the_next fingerprint with_the extra parameter.
Solution
This is a situation that_would_come up fairly easily during testing,_but_that real-life users are almost never_going_to_encounter. It only occurs when_manually typing in a