Using this post by echapeta:
https://www.b4x.com/android/forum/t...-referral-from-google-play.66355/#post-451082
I have managed to pass "referrer" strings from a webpage href to an app as it is launched for the first time via the Google Play Store OPEN button.
Testing this has revealed a curious little quirk: if the OPEN button is pressed too quickly after it first appears (i.e. immediately after the app is installed) the app can miss getting the "referrer" string. If the app is closed and OPEN pressed again it generally works properly - but this is definitely NOT a good user experience.
Doing some googling about this issue (which seems to be a quite well known problem) I came across this article:
https://android-developers.googleblog.com/2017/11/google-play-referrer-api-track-and.html
which is all of 3 days old - hot off the press!
In it a Google engineer describes a new API for accessing the "referrer" string which presumably is a lot more robust than the current mechanism.
It is all above my pay-grade however, so 3 questions:
1. Does this need to be wrapped or can it be accessed via a bit of reflection skullduggery.
2. If the answer to (1) is a bit of skullduggery - can anyone tell me how.
3. If the answer to (1) is wrapping - is there a guru out there who is willing to do it?
Thanks in anticipation...
https://www.b4x.com/android/forum/t...-referral-from-google-play.66355/#post-451082
I have managed to pass "referrer" strings from a webpage href to an app as it is launched for the first time via the Google Play Store OPEN button.
Testing this has revealed a curious little quirk: if the OPEN button is pressed too quickly after it first appears (i.e. immediately after the app is installed) the app can miss getting the "referrer" string. If the app is closed and OPEN pressed again it generally works properly - but this is definitely NOT a good user experience.
Doing some googling about this issue (which seems to be a quite well known problem) I came across this article:
https://android-developers.googleblog.com/2017/11/google-play-referrer-api-track-and.html
which is all of 3 days old - hot off the press!
In it a Google engineer describes a new API for accessing the "referrer" string which presumably is a lot more robust than the current mechanism.
It is all above my pay-grade however, so 3 questions:
1. Does this need to be wrapped or can it be accessed via a bit of reflection skullduggery.
2. If the answer to (1) is a bit of skullduggery - can anyone tell me how.
3. If the answer to (1) is wrapping - is there a guru out there who is willing to do it?
Thanks in anticipation...