Closed hiteshchalise closed 1 year ago
@hiteshchalise You are correct in that we don't require a returnUrl to be passed in in the latest version as of today - 0.8.7
.
However, we've noticed a few issues with removing the custom return url. So, while I cannot tell you exactly when, the return url is going to be added back.
Thank you for the response, and as a followup question, what is the intermediate solution until the return of the 'returnUrl'? Should we remove both RedirectUriReceiverActivity
and PYPLInitiateCheckoutActivity
declaration from our manifest? or should we only remove RedirectUriReceiverActivity
?, because that activity is not currently present, but PYPLInitiateCheckoutActivity
is.
What would be the best path moving forward? Because we must use 0.8.7
due to policy violation.
We define the intent-filters in our manifest, so it shouldn't be necessary for you to declare it again. I believe the reason why these were asked to be declared was to handle few edge cases where app developers had non-standard characters in their application ID and that was causing issues. You should be able to remove them without problem.
The intent filters are used to return from web authentication back into the application. If you want to test it for yourself on sandbox, authenticate on web and check if you are being taken back into the native application.
In the developer.paypal.com site, in 'customize return url' section it is mentioned that, there should be two activity declarations with our custom return URL. Since, the use of return url is removed in newer versions of checkout SDK, does this mean the activity declaration with our custom return url is now obsolete?
I have this error, after upgrading from
0.6.2
to0.8.7
The activity declaration in our manifest:
I couldn't find the info in this particular issue anywhere. It seems removing these declarations has no effect in our sandbox testing, can anyone please confirm this. Thank you.