App crash after logging in #85
Comments
|
@PaterB that error is usually due to, either the merchant account not having PayPal Here enabled, or not having the right scopes assigned during the permissions portion of the onboarding. Please ensure that your onboarding flow utilizes the following scopes at minimum: You'll also need to ensure that your App that you created under your developer.paypal.com account has the PayPal HERE option selected as well as all of the address options selected (they are underneath the Log In With PayPal section). |
|
I have my sandbox account setup with paypal here enabled. |
|
Please let me know the merchant ID of your sandbox account so I can take a look at how it's set up. |
|
How do I find merchant ID? |
|
If you login to your account at sandbox.paypal.com, you would see it, otherwise you can just let me know the email address (since it's Sandbox) if that's easier. |
|
KKSFRHD45Y7GW, here's my merchant account id |
|
Thanks @PaterB. That account is a Singapore account which is not eligible for PayPal Here. You'll want to create a US Business account with the first name of 'Ryan' to use in the Onboarding. The onboarding is explained in the Merchant Onboarding document that's in the docs folder of this repo. The TakePayment app assumes that the account is already set up for PayPal Here, which won't be the case for a brand new sandbox account. You'll need to run it through the initial signup flow that's explained in the Merchant Onboarding guide. Let me know if you run into any more questions. |
|
I have created an account and now I'm able to login. |
|
The EMV reader is only able to be tested in Production, but the older triangle dongles can be used in the Sandbox. Also, you can modify the TakePayment App for keyed entry to test in the Sandbox as well. You can purchase readers here or you can request one if you sign up for PayPal HERE through the PPH App itself from the App/Play Store. |
|
I tried using key mode, now I receive this error.
|
|
@PaterB it appears that you didn't create your sandbox merchant account through developer.paypal.com so there were some things that weren't verified on the account. I've manually changed those things so the account should be able to be used now. |
|
Hi I still receive the same error. |
|
Can you provide the correlation ID of the error? Also, can you confirm that you're logging in and providing permissions to the TakePayment App so that it's able to get the information that it needs from your account? |
|
When I first login, I did allow the permission.
|
|
My apologies for the delay. Please try using the following sandbox login and see if it works. I really think that there's an issue with the account you created. |
|
Thanks so much for your help. It works now. |
|
Are you referring to the reader displaying the Tap, Swipe, Insert options? This would be due to calling |
|
The code. |
|
Where are you putting your code and what code are you using so that I can try to reproduce and help you out? |
|
Hi, all the codes are untouched, it's from the sample app. |
|
Where are you putting your code for the key entry and then how are you submitting it after typing the amount? In order to assist you with what you're seeing, I need to be able to reproduce it so I can adjust things and let you know what to do differently. Please let me know code samples and where in the app exactly these code samples are placed. |
|
Hi sorry for that. |
|
Thanks. I'll take a look and get back to you. |
|
@PaterB I see what you're seeing now. One issue is that you are not populating card data for the manual entry. Manual entry is not yet available on the EMV reader so you have to capture that data yourself and assign it to |
|
Hi, |
|
I have another issue here. Our app is integrated with payanywhere and seems like some of the library is clashing. What can we do to avoid this? |
|
@PaterB it looks like you're clashing with the Magtek libraries. We do offer the NOHW version of our SDK in this repo if you want to remove those libraries from our SDK. Keep in mind, however, then you'll be responsible for handling all communications with the Magtek reader in your App as it won't be handled through our SDK. |
|
Sorry, could you provide me a detailed way of downloading the NOHW version? |
|
For your BN code request, you'll need to reach out to the email address that's at the bottom of the ReadME next to the MFi program information. |
|
Hi we manage to build custom framework and it is able to compile now. Hopefully it doesn't affect the core functionality.
However after that, the app crashes. I'm not too sure if this is caused by lacking a partnerid. Thanks.
|
|
@PaterB this usually has to do with the account setup and/or the options selected on the REST Application. It would have nothing to do with the Partner ID. I need to get some account information from you to make sure that everything is set up correctly. Can you please send me the email address of the accounts that you are using via the email address above? Just put attn: Cory in the email and I will be able to pick it up. I'll need the email address of the production account you are using to login at developer.paypal.com so that I can see the REST Apps that you created for this. |
|
I've send the email to pph-sdk@paypal.com |
|
Yes, I see it. I'll take a look, thank you. |
|
@PaterB I modified your REST App for sandbox to include the right information. The relevant scopes weren't selected in the REST App. Aside from the PPH option, you'll also need to ensure that you have email, phone, and the address fields selected. Those are found under the Log In With PayPal section once it and the Address Information sections are expanded. I've configured your sandbox app for you, however, you'll need to make sure that you do the same for your Live app when you're ready. |
|
Hi, thanks. |
|
Everything is set on your Sandbox application. Did you go through the onboarding again with the merchant account so that the appropriate permissions can be granted? You'll need to to through the flow again so that a new auth code can be generated and then subsequent refresh token. If you didn't do this, then the tokens associated with that account will not have the correct permissions for what we're asking for when setting up the merchant in the SDK. |
|
Hi, https://www.sandbox.paypal.com/webapps/auth/protocol/openidconnect/v1/authorize? Can you explain to me what should I put in the scope? I'm leaving it as https://uri.paypal.com/services/paypalhere |
|
You need to use all those scopes. Essentially it's 4 different scopes all separated by a space... All those scopes are needed as that's the information that's grabbed from the merchant account by the SDK. Since you are not using those scopes, the SDK can't grab the information, and therefore you get the crash. Your |
|
Hi, seems to be good now. Finally. |
|
Take a look at our older sample app here for more information on that. Since you're not using the reader, you'll just have to manually call |
|
Finally! thanks, i'll play around with it. |
|
Hi, how do we modify the page whereby it shows 'Payment Complete, would you like a receipt? |
|
You won't be able to modify the receipt screen as it's implemented to appease EMV certification requirements. |
|
But we need to remove the test alert option. |
|
What test alert option are you speaking of? |
|
Ah, I think you're referring to the Sample Alert option. This option is not shown by default. It's only present in the sample app to simply show that it's something that can be done. |
|
I'm doing the integration by copying codes from the sample app, so am I doing it wrong? |
|
If you don't want the sample alert option to be there, then you'd just not copy that portion from the sample app. The code within |
|
Got it, thanks. |
|
Hmm.. I'm not aware of a way to make it expire early but you could simply use a bad value for the access token to trigger an invalid token error if that's what you're looking for. There's no way to modify the expiry value of the token itself. |
|
Alright, let me describe the issue with refreshing token. I'm using this as refresh token. and this is what I got back. and it seems like the access token is always the same. |
|
That sounds accurate. Since the token isn't actually expired yet, it's re-used. Can you modify that token string to be invalid and trigger the invalid token error that way? What is the issue you're seeing with the refreshing anyway? Perhaps I can help with that... |
|
The token is already invalid, but by requesting it's returning me the same. |
|
The only time that the access token will return the same value from the call to retrieve it, is if it's still within it's 8 hour expiry window. Your composite token that you posted above has the following (with some masking)... The first value that starts with I just did a call to the |
|
Yes, I think only after the 8 hours, i will get a different token, if not I will get the same.
|
|
Hmm... that's strange as it seems the token expired early. I just created a new one based on the refresh token and that initialized just fine. If this new token, which you can get by running the call again, fails after 3 hrs, then please send the account through the onboarding again to generate a new auth_code and turn that into a new refresh token to store. I'm wondering if there was just a sandbox anomaly with the first generation of that refresh token. |
|
I got the EMV chip reader already, however i fail to upgrade the software. I read from another thread saying that we need to point it to production account. |
|
Yes, you won't be able to upgrade the reader in the sandbox environment. You'll need to use a Production account for any testing with the EMV reader. I will reach out to you via email to see how we can help getting you set up with a Production account. |
I just downloaded the paypal here SDK.
Running the TakePayment SDK, upon login with my business account, it crashes.
Please look at the crash log below. Thanks.
The text was updated successfully, but these errors were encountered: