-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not fetching Details When Clicked On Truecaller Button #12
Comments
Once you swipe down, do you get the option to "Open in App"? Also please try the following: |
Hi,
When we swipe down there was no option to open in app. Also there is no
problem in setting up the sdk with iOS project since it worked on some
devices.
Truecaller version we will update u , adding navneet for the same.
Thanks.
…On Feb 24, 2018 4:59 AM, "bi1zi1" ***@***.***> wrote:
Once you swipe down, do you get the option to "Open in App"?
What is the version of the Truecaller app?
Also please try the following:
Open the Truecaller app and then try your flow again.
When you open Truecaller you can check the device logs to see if there is
an issue with retrieving the apple-app-site-association file for it. See
link: https://stackoverflow.com/a/40382040
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#12 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AjDxRHgKQsU2OqV4lbeaoX0-qItr1ldqks5tX0nqgaJpZM4SQuVZ>
.
|
Both Truecaller and the app containing the sdk need to be validated by iOS. This is per device (just like your case) and this is a "side-effect" of universal links. |
HI, I am facing the same issue. @abhinayVrm were you able to solve it? |
Facing the same issue, Please suggest a solution |
any solution ? |
Hi There, Hope you are doing great! The issue that you mention is due to an OS level restriction. In some cases the AASA file doesn't get's downloaded leading to this behaviour. I would request you to update our IOS SDK to it's latest version as we have gracefully handled this scenario now. Please feel free to reach out to us via our support channel for a faster and dedicated response. Regards, |
Things integrated in project -:
i) Info.plist -> LSApplicationQuesriesSchemes have key value set as truesdk.
ii) In Capabilities -> Associated Domains -> setted domain without https . used applinks:.........
iii) In app Delegate -> TCTrueSDK.sharedManager().setup(withAppKey: "mykey", appLink: "mylink")
iv) In app Delegate ->
func application(_ application: UIApplication, continue userActivity: NSUserActivity, restorationHandler: @escaping ([Any]?) -> Void) -> Bool {
TCTrueSDK.sharedManager().application(application, continue : userActivity, restorationHandler: restorationHandler)
}
v) I have integrated TCProfileRequestButton and func didReceive(_ profile: TCTrueProfile) , didFailToReceiveTrueProfileWithError and willRequestProfile delegate functions in the controller with TCTrueSDKDelegate confirmed in the controller.
PS -: a) It was working for us before pushing it to app-store.
b) I'm getting a call in willRequestProfile on clicking of that button after which it takes me to a blank safari screen attaching the same.
No call came in didFailToReceiveTrueProfileWithError and didReceive after willRequestProfile.
Kindly let us know what is the issue.
Thanks.
The text was updated successfully, but these errors were encountered: